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

Allow a Visualization to Update the Data in Another Visualization in Dossier

Allow a Visualization to Update the Data in Another Visualization After adding multiple visualizations to a dossier, you can select values in one visualization (that is, the source) to automatically update data in another visualization (that is, the target). This is done by creating a filter on a visualization that targets other visualizations. To Add a Target Visualization to Your Dossier: Open the dossier with the visualization. Click  Insert Visualization   . A blank visualization appears in the dossier. From the Visualizations panel, select  Grid   . Drag an attribute from the Datasets panel to the  Rows  area of the Editor panel to add attributes to the rows. Drag an attribute from the Datasets panel to the  Columns  area of the Editor panel to add attributes to the columns. Drag a metric from the Datasets panel to the  Metrics  area of the Editor panel, to add a metric to the grid. The Metric Names attribute automatically appears i...

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Fact tables levels tables in Microstrategy explained

Fact tables levels in Microstrategy: Fact tables are used to store fact data. Fact tables should contain attribute Id's and fact values which are measurable. All the descriptive information about the fact tables should stored in Dimension tables either in Star Schema fashion or Snow Flake Schema fashion which is best suited to your reporting solution. Since attributes provide context for fact values, both fact columns and attribute ID columns are included in fact tables. Facts help to link indirectly related attributes using these attribute ID columns. The attribute ID columns included in a fact table represent the level at which the facts in that table are stored. So the level of a fact table in the Fact_Item_Day_Customer can be the attribute Id's which is at Day, Item & Customer Id level. For example, fact tables containing sales and inventory data look like the tables shown in the following diagram: Base fact columns ver...

Microstrategy Dossiers explained

Microstrategy  Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has  evolved dashboards to the point that they are more than dashboards - they are  interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so  the've  renamed VI dashboards to  ‘ dossiers ’.  Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers   With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...

Microstrategy Document Editor Sections Important Notes:

Microstrategy Document Editor Sections Important Notes: The Layout area is in the center of the Document Editor interface and provides the framework for precisely controlling where controls (such as text fields, grid and graph reports, images, and widgets) are displayed when the document is viewed in different display modes, printed, exported, emailed, and so on. To add data to the document, drag objects from the  Dataset Objects  panel and drop them into the  Layout  area. Controls are rendered differently depending on what section they are placed in, as described below:   Page Header : The control is displayed at the top of each page in the document. By default, if a document contains multiple layouts, the same Page Header is displayed for all layouts in the document. You can change this setting so that each layout has a separate Page Header. Document Header : The control is displayed once at the beginning of the document, immediately below the Page Header sec...

Apply or Pass-through functions in Microstrategy

Ap ply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various RDBMS systems.. Syntax common to Apply functions Apply Function Name   ("expression with placeholders", Arg1, Arg2, Arg3, …ArgN) where: Apply Function Name  – is a generic name used for the predefined pass-through functions described above expression with placeholders  – is the string describing the actual expression or syntax that the engine uses while generating the SQL and which is sent to the RDBMS. The placeholders are represented by #0, #1, and so on. "#" is a reserved character for MicroStrategy. Arg  – is an argument that replaces the parameter markers in the pattern. Arg1 replaces #0, Arg2 replaces #1, and so on. There are   five  pre-defined Apply functions to replace regular, predefined functions of the same type. For more details, cli...

"Table structure cannot read or update" in the warehouse catalog error while updating a table structure in Microstrategy

"Table structure cannot read or update"  in the warehouse catalog error while updating a table structure while using Warehouse Catalog in MicroStrategy Developer  This issue could be due to the incorrect prefix.  To fix the issue. 1. Open the Warehouse Catalog. 2. Select the table and assign the correct Prefix update the structure. 3. Save and close the warehouse catalog.

User request is completed. (Ran out of memory)

Unable to Run/Edit particular MicroStrategy reports ue to the following error: User request is completed. (Ran out of memory) User request is completed. (Ran out of memory) The above issue appeared in MSTR Web Universal version 10.5 We tried the below options without any luck: 1. i-server restart 2. Web server restart 3. clear document cache/dataset cache 4. Web server cache clear as below: The correct option is to increase the contract memory settings: Using the Memory Contract Manager The  MCM settings are in the Intelligence Server Configuration Editor, in the  Governing Rules: Default: Memory Settings  category. The  Enable single memory allocation governing  option lets you specify how much memory can be reserved for a single Intelligence Server operation at a time. When this option is enabled, each memory request is compared to the  Maximum single allocation size (MBytes)  setting. If the request ...

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...

Star Schemas issue fixes in Modelling of Microstartegy

Star Schemas issue fixes in Modelling of Microstartegy Explanation This schema is characterized by one lookup table per dimension, with base tables at the lowest level. This is the fastest way to set up a data warehouse: This type of schemas is supported but has restrictions such as when adding aggregate tables: Problem Double counting. According to the diagram above, a report that contains month and the a metric SUM(SALES_AMT) will go to the aggregate table and join to the column to retrieve the description from the table. Since the column is not unique in its lookup table, the results will appear duplicated. Recommendation MicroStrategy engine is optimized to work with snowflake schemas, where each attribute level has a distinct lookup table. Star schemas are supported with restrictions, as long as fact tables are not at a higher level than the dimension tables to which they are joined. Consult the following MicroStrategy Knowledgebase document for further information....