Overview of Apps (Portal Pages)

1. The traditional Homepage in Metric Insights appears as Catalog.
2. Apps appear as tabs. Any of these Apps can be selected as a User's default Homepage upon entry into the system. You can control which Apps appear as tabs for specific Users or Groups, and you can set an App as a start page.
   • See Share the App for details.

Access Content > Apps

1. [+New Page]
2. Use App Builder: Specify whether to use the App Builder (if enabled).
3. Name: Enter an App name.
4. Name used in URL: Enter a name to be used in the App URL.
   • Note: Letters, numbers, dashes and underscores are the only supported characters for Apps' URL names.
5. Template: If you want the App to be populated from a Template, choose one.
   • See App Templates for details.
6. [Save]

1. Can be used as External Report: Activate the checkbox when an App needs to be available as a tile in the Catalog or sent via a Burst.
   • If enabled, the Image Capture for External Reports section appears on the Advanced tab.
     • See Advanced Settings for details.
2. Optimized for Mobile: Activate this checkbox if the App is optimized for mobile devices. Only Apps that have this checkbox activated will be displayed in the mobile application.
   • NOTE: App must be developed for mobile devices; otherwise, “Optimized for Mobile” won't work.
3. Sync with Git: Toggle on to enable the App for Git synchronization.
   • If on, the Code tab switches to Git Sync where you can configure syncing for uploading App assets as an alternative to a manual upload.
4. Display without Metric Insights navigation bar: Activate the checkbox to display the App without the MI navigation bar at the top of the page
   • If checked, specify the following:
     • Embed URL: A way to access the page and use it for embedding.
     • Layout: A way to establish navigation on the page.
5. Allow linking to specific elements within this App: Enable this option to allow redirecting to elements contained in the App from Burst.
   • If this option is enabled, provide URL Pattern that matches the routing implemented in your App.
6. Optionally, exclude the page from Homepage navigation bar and search.
7. Version Identifier displays a unique hash of each App, which is used to identify the App version and track changes. Click on its value to see the version history.
8. Proceed to the Code tab to add additional information; e.g., HTML, CSS, and JavaScript, embed objects.
   • Code files can also be uploaded and managed from the Assets tab.

Use the Code tab to add or manage the App's code (HTML/CSS/JavaScript) and to embed Metric Insights content.

Use the Sharing tab to control who can view the App, whether it appears in User's navigation bar, and whether access is restricted by default. You can also copy or inherit access rules from another App to apply the same sharing settings consistently.

• See Share App with Users and Groups for details.

Use the Assets tab to supply your App with JS, CSS, images, and other files.

• See Understanding App (Portal Page) Assets and Upload/Download App (Portal Page) Assets for details.

Use the Entities tab to configure managed integration points (Entities) that connect your App to Metric Insights objects.

1. Toggle on to enable receiving POST requests from sites other than the current MI instance
   • See How to use the 'Enable POST request navigation from other sites' option? for details
2. Support v6 App Code: Enable this option if your App contains v6 code and you want to make it compatible with v7
   • See Legacy Scripts for Portal Pages Compatibility in v7.0.1+ for details
3. Asset Browser Cache Setup: Set up cache lifetime for Assets
   • See Portal Page Asset Caching for Improved Performance for details
4. Custom Domain: Enter a Custom Domain for the App
   • See Configuring a Custom Domain for an App for details on Custom Domain configuration

For image collection, you can decide when the system should take a screenshot of App or how much time an App can take to load before the system takes a screenshot of that Page:

5. Timeout: Specify a time interval after which a screenshot is taken once the App is opened
6. Screenshot on: Select a condition of taking a screenshot. Note that a screenshot will be taken when the selected condition is met or after the time interval specified in the Timeout field has elapsed
   • Only on Timeout: A screenshot is taken after time interval specified in the Timeout field
   • Element Removed from Page: This condition is appropriate if you want a screenshot to be taken after some element disappears from an App. The element can be set in the CSS Selector field; e.g., if you want a screenshot not to be taken until the App is fully loaded, enter .loading to the CSS Selector field
   • Element Added to Page: Select this condition if you want a screenshot to be taken when some element appears on an App. The element can be set in the CSS Selector field
7. [Save]

Use the Access tab to grant edit access to Power Users for this App.

• See Granting User Access to a Portal Page for details.

Use the History tab to view the log of App changes. To see the code changes:

1. [More]
2. [Code History]