Skip to main content

HyperIntelligence and its Architecture

HyperIntelligence and its Architecture

When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy.

This feature is similar to what we see in web pages particularly stock related web sites. 
MicroStrategy introduced HyperCards, a new object that is built, managed, and deployed using MicroStrategy Workstation(Not by using Developer or Desktop as far as I know). Cards can be consumed in a web browser via the MicroStrategy HyperIntelligence Chrome extension and on iOS devices via the MicroStrategy HyperMobile app. This feature can help the users to inject Zero-Click Intelligence (as it requires the users to hover only and no need to click!) about customers, products, people, and more directly onto words within websites or web application or emails. This feature can display the content through the mobile devices to bring answers through relevant, context-based analytics.
HyperIntelligence assists the users to find a report without logging into the environment and then allows to locate relevant information. It brings answers directly to you through contextualized text analytics that is as simple as hovering over a highlighted word.
HyperIntelligence can be an interesting and exciting feature for all levels of report/analytics users as they can see the reports as they type on in emails as below:

Salient features of HyperIntelligence:
  • Enables the text analytics that is as simple as hovering over a highlighted word in your email or web browser.
  • HyperIntelligence automatically scans every web page and underlines relevant keywords. Hover over a highlighted word to see insights in real-time.
  • Each card can seamlessly combine information from multiple enterprise assets and applications.
  • The extension supports multiple cards for different use cases. Each card can point to a different keyword. Simply click the extension icon to see the list of available cards or toggle individual cards on or off.
  • By default, the extension will work with any web-based content, however it is possible to blacklist individual websites - disabling the extension's functionality.
Microstrategy 2019 enhances the HypeIntelligence features further by introducing vision voice screen etc with the the new features like Hypevoice, Hyperscreen and Hypervision.

Hypervoice:

This feature allows the users to ask questions to get instant answers through voice commands in a similar fashion as you interact with Alexa. MicroStrategy integration with Amazon Alexa or Google Home (Not sure about Apple Homepod integration) to turn analytics applications into a voice-enabled personal coach. Which could boost productivity by blending insights into existing workflows. Developers can leverage MSTR APIs to integrate with voice-controlled applications like Amazon Alexa and Google Home. With MSTR-developed NLG and voice recognition mechanisms, it could be easy to get answers to the business questions on the way to the next meeting. By integrating with voice technology or chatbots, it’s easy to deliver the right data, fast.
No alt text provided for this image

Hyperscreen:

Hyperscreen enables the personalized insights on every wall(screen) you walk through. It can turn a screen into a dynamic, intelligent display that presents a personalized view of information based on who is standing nearby. It uses the new feature called Digital Identity to transform offices and facilities into spaces that inspire data-driven collaboration and action.

Hypervision:

Here, the magic comes by embedding analytics with virtual reality. Hold up your device for an augmented reality experience that overlays insights on objects and surroundings. Use image recognition to scan products and check inventory, or use GPS location to get an instant customer brief as you walk into your meeting.

Architecture 

The above workflow can be described as:


  • HypeIntelligence extension from Google Chrome browser submits a REST API request to MicroStrategy cubes by requesting topic(attributes!) and metrics.Data received from MSTR cubes to the browser is cached.
  • When the user open the browser and opens a web page or types text in emails or open emails. 
  • The extension finds matches and highlights those matching keywords.
  • Users hovers the highlighted keyword.
  • Extension displays the hypercard as designed.
  • Once the extension gets the data it caches the data and display the data in Hypercards whenever a user hovers on the key word highlighted.
 Deliver Zero-Click Intelligence
 Combine Information from Multiple Systems
 Support Multiple Cards
 Blacklist Individual Websites

The architecture for HyperIntelligence is similar to MicroStrategy Library. MicroStrategy Library is a client application running on a desktop browser or a mobile device, whereas HyperIntelligence is currently only available as a Chrome browser extension
If we compare this architecture with the old Microstratgey architecture we see the additional component of MicroStrategy Library which makes all the magic of HyperIntelligence.
 Single node architecture

Multi Node Architecture:

Comparison between Single node i-server and multi node i-server:

HyperIntelligence Workflow 

Hover effects won’t work on mobile devices because there’s no mouse cursor. To overcome this MSTR has handled mobile links with high color and shape contrast on them so that user will know where to tap. So that it displays the cards.
I have not yet explored this feature when the email goes to external users and the data level security(security filters) work as we are not passing any security filters.Handling of row level security on the cards is still a mystery!

Comments

Post a Comment

Popular posts from this blog

Microstrategy Release Types Platform release Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, and regular hotfix cadence addresses critical defects. Feature Release Interval:  Quarterly every three (3) months Who:  Customers with specific feature requirements. What:  New functionality developed in close collaboration with customers and customer council. Expectation:  Customer has chosen feature path, will consume further feature releases. Support:  Six (6) months patch support for approved P1 defects and (eighteen) 18 months troubleshooting. Customers upgrade to next feature release for roll-up f...

Microstrategy Document Autotext macros:

Autotext  code/macros in  Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add  document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard:  AUTOTEXT DESCRIPTION   {&PAGE}  Display the current page.  {&NPAGES}  Display the total number of pages.  {&DATETIME}  Display the current date and time.  {&USER}  Display the user name that is executing the Report Services Document.  {&DOCUMENT}  Display the document name.  {&DOCUMENTID}  Display the document ID.  {&DESCRIPTION}  Display the document description.  {&PROJECT}  Display the project name.  {&EXECUTIONTIME}  Dis...

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...

RunningSum calculation only on the metric subtotal in MicroStrategy

RunningSum calculation only on the metric subtotal in MicroStrategy Here are the series of steps to setup report objects in which metrics and subtotals so only the  subtotal field  will contain the  RunningSum  and the  regular metric values  will be  standard sum values . 1) Create Metric 1 which is the sum of the fact that is to be in the columns. 2) Create Metric2 as the RunningSum of Metric1.  NOTE:  The  sortby  parameter for the RunningSum should be set to whichever attribute you want the report sorted by. 3) Create Metric3 as Metric1 + (Metric2 x 0) 4) Create a new subtotal called "Max" which is defined as Max() 5) On the Subtotals/Aggregation tab for Metric 3, set the Total subtotal function to be "Max" and select the check box for "Allow Smart Metric" 6) Create the desired report and place the 3 metrics on the report.  NOTE:  Only Metric3 is required on the gri...

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...

Microstrategy "Error type: Odbc error. Odbc operation attempted

 "Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’.  Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy FiscalWeek Returns the numeric position of a week within a fiscal year, for a given  input date. This function is useful in financial reporting when the start of the fiscal year is different than the start of the calendar year. Syntax FiscalWeek< firstWeekDay ,  firstMonth >( Date / Time ) Where: • Date / Time  is the input date or timestamp. • firstWeekDay  (default value is 1) is a parameter that determines which day of the week is considered as the first day of the week. You can type an integer value from 1 to 7, with 1 representing Sunday, 2 representing Monday, and so on until 7 representing Saturday. • firstMonth  (default value is 1) is a parameter that determines which month is considered as the start of the fiscal year. You can type an integer value from 1 to 12, with 1 representing January, 2 representing February, and so on until ...

Evaluation Ordering

Evaluation Ordering Evaluation Ordering is an advanced property that is hidden by default. For information on how to display this property, see  Viewing and changing advanced VLDB properties . An evaluation order is the order in which the MicroStrategy Analytical Engine performs different kinds of calculations during the data population stage. The Evaluation Ordering property determines the order in which calculations are resolved. MicroStrategy objects that are included in the evaluation order include consolidations, compound smart metrics, report limits, subtotals, derived metrics, and derived elements. Some result data can differ depending on the evaluation order of these objects. • 6.x order - Calculate derived metric/smart compound metric before derived elements/consolidation and all subtotals as smart : This option is used primarily to support backward compatibility. It is recommended in most scenarios to update your project to use the 9.x evaluation order described below. • ...

Customers Who Live in the Same City as Call Centers

Customers Who Live in the Same City as Call Centers Your new utility company has call centers located throughout the country, and your recent surveys indicate that customers who live in the same city as a call center are particularly satisfied with service due to extremely rapid repairs during power outages. To begin your new advertising campaign, you want to generate a list of Call Centers that coincide with Customer Cities. The following steps create an attribute-to-attribute qualification filter that generates the list of desired cities. To Create an Attribute-To-Attribute Qualification that Compares the Call Center and Customer City Attributes In MicroStrategy Web, log in to a project. Open any folder page (for example, click Shared Folders on the home page). Click the  Create Filter  icon  . From the Object browser on the left, select the  Customer City  attribute from the Customers hierarchy and drag it to the filter pane on the right. Change  Qualify...