After over a year of development and iteration, with a front-end implemented as an App (formerly called Portal Pages), Concierge is now fully integrated into the core Metric Insights platform UI. It now has a dedicated setup page under Admin > System, with all the existing and new settings such as using Concierge for Global Search, determining how many results Concierge displays when Tiles are returned, when to reset the current chat, etc. 

Content search in Concierge is now tied directly with Global Search and many Global Search improvements have been introduced to support Concierge. We have improved search accuracy with multi-pass searching and intention mapping, extended capabilities to include lineage columns and content, implemented new re-indexing through the UI and API, and enhanced formula readability for LaTeX content.

The Search results page now has a different look and feel. The sidebar includes more Filters and can be collapsed. The main results section looks more dense while each individual result is more informative when expanded. For Datasets to include in Search, we have implemented Group-level security at the Dataset level.

With Analytics Marketplace, we've taken discovery and search capabilities across multiple data catalog platforms to the next level. Your analyst community can now leverage tools like Atlan, Alation, Collibra, Databricks Unity Catalog, and more — all from a single pane of glass, without ever leaving the Metric Insights UI.

Integration with Atlan has been enhanced to include Glossary Terms, Dataset Columns, and Lineage information. The Global Search UI has been completely revamped to deliver more relevant results and offer advanced filtering options.

These improvements were specifically designed to support and elevate the Analytics Marketplace use case.

1. In Catalog List View, you can toggle the display of the “Expired” label for Elements on and off. Additionally, you can select the label's color. 
2. We have introduced new customization options for the Catalog, main header, left navigation, drop-downs, and Tiles, including the ability to set background colors or use images for that purpose, as well as to adjust the Tile appearance. 
3. The Menu tab has been renamed to Navigation & Menus, providing greater flexibility for customizing the Catalog tabs, start page, left navigation design, and the New menu display. 
4. You can also choose whether to display the Element border in Element viewers. This setting is found under the Elements tab.
5. The “No Tile” message on Homepage can now be customized as well. The supported parameters include [SearchQuery] and [SupportAdmin]. The latter will show the contact set through the MI_SUPPORT_CONTACT_EMAIL System Variable. 
6. On the Themes Menu tab, Content Menu and Custom Links:How-To Guide default to "PUs & Admins only.”
7. In multi-column List View, you can choose to display Element thumbnails or disable them. This behavior is controlled by the Display Thumbnail setting under Catalog List of Themes Editor. 
8. The default embed URL for multi-column List View follows this format: https://<HOSTNAME>/home?hide_filter_panel=Y&hide_hierarchy=Y&hide_announcements=Y. Check boxes provide the ability to enable/disable certain features.

See more in Use Themes to Customize Metric Insights.

A powerful new set of features is available for Bursts. PDF Report Packs enable the distribution of large PDF files (think hundreds of pages of reports), which are useful for some enterprise reporting use cases that are otherwise very cumbersome to implement in reporting tools or require manual creation or scripting for full implementation.

We've also introduced parameters for Bursts. The functionality allows you to dynamically populate data from a Dataset into the email subject line and custom header/footer text fields for a Burst.

Portal Pages are now Apps, and App Builder Alpha marks the beginning of a new era in MI App development. It is designed to streamline app creation for every member of your team — even those with only basic experience in programming or design. This simple yet powerful tool offers a component-based approach with an intuitive drag-and-drop interface. It offers:

• Component library including menus, embedded Elements, and list components—limited for now, but will be dramatically expanded in the future;
• Support for file uploads and asset management;
• Customizable styling and theming options;
• Variable storage for app settings and configurations;
• Visibility controls for components and containers.

Other App Improvements

1. External Reports shared with our sharing API can now be linked back to an App (instead of going directly into the External Report Viewer within the core application). This was a final missing piece to the "keeping users in a custom experience (App)" puzzle.
2. When creating a new App or Template, while auto-generating the "name used in URL", we now use dashes (-) instead of underscores(_), e.g. name-used-in-url.
3. Disabled Apps and Templates now appear grayed out on the App/Template list page. 
4. The Apps list page includes four new columns for a better understanding of their usage with no need to access the App itself: 
   • Navbar: specifies if the App is visible in the main application navbar;
   • Mobile: specifies if the App is optimized for mobile devices;
   • Shared: displays the count of users the App is shared with;
   • Last Modified: displays the date of the latest modifications.
5. The Layout and Available for Content columns are hidden.
6. The "Execute additional JavaScript at runtime" setting has been removed for all App Variable Types.

1. The “Required” option has been added for Glossary Terms. When checked, a user must set at least one Glossary Term before moving an Element from the Stage.
2. The new setting, “Only allow updates from Assignee,” restricts the ability of other users rather than the current assignee to move or re-assign Elements in the Publishing Board. 
3. The “Add Group to manage content in this Stage” has been improved to include three options: 
   • Can edit this Stage;
   • Can assign to this Stage;
   • Can edit and assign to this Stage.

2. We have introduced API tokens with built-in security. A new token has 128 characters and is visible only once, upon creation. Make sure to save it in a safe location. A few rules apply to tokens:
   • Power users can add a new token only for themselves.
   • Admins can add a new token for themselves and for other non-admin users.
   • Admins can't add a new token for another Admin.
3. Two new Publishing Workflow API endpoints have become available in this release:
   • /api/publishing_workflow
   • /api/publishing_workflow_element
4. api/category  allows Admins or Power Users with the Create Categories and Subcategories Privilege to create a Category. Users with the Edit Access can edit or delete a Category.
5. The new App Template API has been implemented to be able to download/upload Template Assets:
   • GET /api/page_template/id/{portalPageTemplateId}/asset/download
   • PUT /api/page_template/id/{portalPageTemplateId}/asset/upload
6. The abilities of /api/page have been expanded to upload and download App Assets for an App.

1. The Rule setting on the Visibility tab allows you to add rules to conditionally display a Custom Field. For example, Custom Field 2 displays if the value = X in Custom Field 1, Custom Field 3 displays if the value = Z in Custom Field 2, etc. Custom Fields can conditionally display for:
   • Elements;
   • Glossary Terms; 
   • Publishing Workflows.
2. On the Custom Field list page, there’s now a “Group” filter that displays Custom Fields to which the selected Group has access. The new “Visibility” column displays a value depending on the “Visible to” setting.
3. When creating a new Custom Field, "Tile Hover Information" is checked by default.

We've refined the UI for Metadata Propagation Rules. The editor now includes options to search, add, duplicate, and delete rules. The success message is now more informative and interactive.

You can now choose to add or replace existing Tags, Glossary Terms, and Multi-Select Custom Fields. Element matching has been extended to support External GUIDs, in addition to Report Names and IDs.

Similar to Glossary Autoimport, you can now email error reports to specified recipients.

A new option — “Reports found in Dataset that map to MI External Reports” — allows changes to be applied only to External Reports, instead of all Elements.

1. In some Editors, for better convenience, users will be automatically taken to fill out the field that appears based on the selection for the previous one. 
2. The RDP icon has been redesigned to better represent the functionality and avoid ambiguity.
3. We have implemented multi-select and delete options for Announcements. 
4. The Tile’s right-click menu provides an option to copy the URL to the clipboard.
5. The standard Edit gear control has been reimplemented for Triggers in Bulk Add External Reports/Content.
6. Fixed columns on Grids have a center alignment.
7. The "Update" button on the Element Bulk Change popup has been renamed to "Next: Review" to avoid confusion. 
8. We continue to reimplement multi-select in v7 in all critical Editors.
9. "sourced" and "hiding" have been removed from the Show Columns list on the Objects grid of the Source Object tab in Plugin Data Sources Editors.
10. Metric stoplight labels have been updated for more accuracy.
11. In Element Editors, we have renamed "Report Image Trigger" to "Image Collection Trigger".
12. Based on a Data Source selected, the User/Group access grid names change dynamically.
13. From now on, users will see an alert when trying to upload unsupported favicon archives.
14. Metric Insights now shows the full Folder hierarchy in User and Group Editors.
15. On the Dataset Run History popup, the Data Collection Trigger run and data fetch duration (in seconds) are now displayed in the Duration and the Fetch Time columns respectively.
16. There is a new note about thumbnail image collection for External Reports created from Data Sources with OAuth enabled. When Image type is set to “Collect with user's credentials (1 image per user, per view)” and Generic Image is set to “Collect via Data Source”, users will see the following message: "The service account must have access to this report to collect a thumbnail image (the thumbnail is not collected per user, rather it is a generic image visible to all users with Tile access).

1. The new “Create Documents” Privilege enables Regular Users to create/use/delete Documents.
2. The "Create Announcements" Privilege now requires only View access to Elements.

1. The new System Variable, LOGIN_USER_HELP_URL, allows you to override the default link to Metric Insights Help documentation with your own custom document/URL.
2. AUTO_INCREMENT_WARNING_PERCENT defines the percentage threshold for monitoring AUTO_INCREMENT usage in MySQL tables. If the used range of an AUTO_INCREMENT column exceeds the assigned value, the table will be flagged as approaching its limit. 
3. When ENGAGEMENT_HIDE_PII is set to Y, the Engagement Distribution By User (Last month Only) section will be hidden from the Engagement tab of Content Center. Additionally, the user’s name won’t appear on both the Content and Behavior tabs.

1. The Large Tables card of Status Monitor lists DB tables that are close to the limit to be maxed out.
2. Category Names can be up to 50 characters long.
3. Upon Burst import, a new Notification Schedule will be created if it does not already exist on the target. The existing Notification Schedule will not be updated on the target but mapped by name. 
4. Being a part of deprecated functionality, Assigned Datasets have been removed from Digest Template Editors.  
5. When running Content Sync and picking up the “Manually uploaded” setting from the External Report Template, you can try collecting preview images for newly created Elements regardless of the Template by enabling the corresponding setting. 
6. In the External Report Editor, it is now specified if the Plugin collects native PDFs or PDFs are generated using collected PNG images.
7. "Send emails now" triggers emails to be sent immediately without any delays. 
8. The Auto Expiration parameter is now available for Element Bulk change.
9. You can configure to get email and Slack notifications when key MI services go down. 
10. Different Plugins can have non-unique Data Source Names. 
11. The Glossary Autoimport’s “Import Now” logic is now disconnected from the associated Dataset update.
12. We have implemented the CONCAT function for MIQL.

1. Backup history can be filtered by the Backup type.
2. MI Console displays detailed SSL Certificate information under Configuration > SSL certificates.
3. Alerts for service downtime can be configured to email and Slack.
4. Changing the Metric Insights application timezone will also change the Chatbot timezone.

1. Metric Insights is now fully compliant with Docker hardening requirements by enforcing a read-only root filesystem for all containers. The Docker image was reconfigured to create a volume for the /opt/mi directory, allowing writable operations only within this directory, which is backed by a mounted volume.
2. Metric Insights is now shipped with a Vagrant configuration file for local application deployment, supporting both x86_64 (VirtualBox) and ARM64 (VMWare) architectures.
3. The CPU and memory usage for each service can be regulated by the new installer options for Simple Install: --default-memory-limit, --default-cpu-limit, --cpu-limit, --memory-limit. The default value for the memory limit is 80%. For Kubernetes and Docker Swarm, edit the service manifest files to regulate the resources.
4. A new parameter system-info of the mi-support tool displays system information for MI services. During the start of containers, the information on the available RAM and disk space is displayed.
5. Application keys are regenerated when Metric Insights application is restored to a different hostname.
6. The latest Terraform version 1.10.4 is supported.
7. The New Relic client has been removed.
8. NodeJS was updated to version 22.
9. Oracle Linux 7 is no longer supported by the Metric Insights installer.
10. Data Processor no longer requires opening the port TCP 32550, it connects to RDP via the main application URL using the standard HTTPS protocol.
11. Directories /tmp and /opt/mi/backup/.tmp/ are cleaned up during every upgrade.
12. Chromium was updated to version 135.
13. PHP was updated to version 8.4.
14. Data Processor is now shipped as is, eliminating the unzipping process to prevent potential errors and speed up startup.

1. A discrepancy in our session logging that skewed engagement metrics displayed on Engagement pages within Content Center and impacted custom SQL queries related to engagement has been addressed in v7.1.0. All previous versions of v7 need to be patched. Contact [email protected] if you have any questions.
2. On the Vocabulary grid, filter selections are maintained for the user, even upon page refresh or navigation away and back to this page. 
3. Glossary Sections are now ordered alphabetically in all Editors and Viewers as well as on Tiles.
4. In Element Viewers, Regular Users can no longer share Elements, leave comments, or provide expert analysis. 
5. Workflows with a large number of Elements used to take longer for Publishing Boards to load for Regular Users. This behavior has been fixed by reducing the number of required permissions to check against.
6. From now on, the Java Virtual Machine will be automatically allocated 80% of the data processor container, which will help avoid container crashes. 
7. An issue with authorization that occurred after modifying saml.php via MI Console has been resolved.
8. Keyword search on Homepage works correctly, and returns matches on Tags. 
9. All new Elements created from Content Sync with the Discoverability setting enabled are blurred for users without access.
10. Failing to access Owner Field Setup with the "Not Found" error has been resolved. The issue was related to the non-standard autoincrement setup.
11. Before the fix, External Reports embedded in Apps included extra margins at the bottom.
12. Getting Filter Values was failing for specific Tableau Workbooks due to an NPE error which has been fixed in this release. 
13. We have fixed a bug with the processing of the installer.options file (saved installer options).
14. Issues with some Trigger runs taking longer times for data collection has been resolved by setting data-processor.dc-worker.count-simultaneous-tasks in application.yaml inside dataprocessor container to "20".
15. At some point, Global Search stopped returning newly created Elements because one of the Data Analyzer tables reached the limit of the primary key value. We have updated the primary keys to use the BIGINT data type.