The biggest change in v7 is invisible: our new architecture, built on the wildly popular React JavaScript library and the robust Laravel PHP framework. We've simplified our codebase, prepared the entire UI for localization (please request languages as they come up—to start, over the coming months, we'll be gradually supporting the same languages we did in v6), and done a ton more behind the scenes improvements.

For the serious techies: we've replaced PhantomJS with a combination of NodeJS (server), Chromium (headless browser) and Puppeteer (API / control plane), a set of tools that make generating images , taking screenshots of reports, and running Custom Scripts easier, faster and more flexible. All of these functions are now done via new service, the image-generator.

Finally, all libraries utilized within Metric Insights v7 are on recent versions and will be kept up to date.

To summarize the major points:

1. Our new front-end architecture is now production-ready, introducing an updated UI and numerous usability improvements.
2. MI Console is a new environment administration tool that allows Administrators with special rights to complete most configuration tasks via the UI.
3. Themes can be created and modified directly in the product. Theme Editor incorporates functionality for quick color, font, and style changes.
4. Custom Fields can now be assigned to and displayed on Glossary Terms.
5. Two new Plugins, Atlan and Alation, have been added to the product.

We've introduced a brand new way of administering the Metric Insights platform via a UI. From 7.0.1 onward, we will invest heavily in ensuring that all administration can be done with the help of MI Console, in addition to the command line tools that are already available. In 7.0.1, the majority of configuration, including patching, is possible through the UI with LDAP/AD User Sync configuration arriving in v7.0.2.

This release introduces the possibility of creating your own Theme to customize the look and feel of Metric Insights according to your needs and preferences. Available under Admin>System>Themes, the Editor includes a wide range of settings, allowing Admins to:

• Adjust the colors, sizes, and shapes of UI elements;
• Upload custom fonts;
• Hide/Unhide Content menu;
• Customize Content Viewers. 

The Editor is intuitive and easy to use. Most of the changes can be seen in real time on the example UI elements. Once ready, the Theme must be applied via the desired Brand page, which also means that you can customize the UI based on User Groups.

1. We have implemented smarted API caching. When a POST or PUT occurs against a specific endpoint, only the related table is updated instead of the entire cache.
2. /api/embed generates an embed URL for a BI tool object that is not an Element in Metric Insights.
3. /api/page_variables surfaces Portal Page Variables. 
4. /api/glossary_term provides Glossary access for Regular and Power Users.
5. /api/metric_alert allows Regular and Power Users to get all Metric Alerts available to them without specifying Metric Alert IDs.
6. /api/publishing_workflow and /api/publishing_workflow_element allow for manipulating Workflow Stages and Statuses, updating Assignees, and managing Comments.
7. /api/data_source_external_report gets metadata about an External Report reference via a set of new parameters.
8. We have also implemented several new Data Source metadata endpoints:
   1. /api/data_source_external_rollup
   2. /api/data_source_external_connection
   3. /api/data_source_external_dataset
   4. /api/data_source_external_dataset_column
   5. /api/data_source_external_dataset_linkage
   6. /api/data_source_plugin

1. The ENABLE_BI_CONCIERGE System Variable has been renamed to ENABLE_CONCIERGE. Those upgrading from 6.4.5 will need to enable this new Variable to use Concierge.
2. The Concierge Portal Page now uses Brand Theme colors.
3. The Welcome icon, Title, Description, and bot icon can be customized.
4. We have implemented integrating an external resource to include an Azure Index in search.
5. Concierge considers the User type when answering how-to questions. 
6. Concierge has been added to MS Teams chatbot.
7. The “Default out of Scope” message can now be set for when the Concierge is unable to find a high-quality answer through the provided content or documentation. 

Custom Fields can be assigned to Glossary Terms. Custom Field Descriptions support Markdown, which is especially helpful for inserting links.

• Upgrading from versions 6+ requires additional configuration to enable the legacy Portal Page code as a short-term solution.
• A new version of JQuery and new internal APIs are now supported.

Available at <hostname>/admin/owner, there is now a new Editor that allows for some basic manipulations with Owners, such as disabling Owners, relabeling them, and disabling their display on Elements and Glossary Terms.

1. Search aliases and hierarchies can be set up in the Search Aliases table.
2. Global Search can be enabled/disabled on the Search Setup Page instead of configuring the System Variable.
3. Category Search uses full Category paths. If there is the same Category under different parent Categories, they will all be searched.
4. Glossary terms are broken out from Tags in the results list.
5. "Created on" date is included in the results list.

1. Brands can now be migrated. 
2. When Custom Fields are migrated, you can choose to update the existing ones in the target.
3. Custom Fields have been added as a dependency for the Glossary Term migration.  

1. Tiles, Tile Previews, Element Viewers, and the Glossary Terms popup have an updated UI. They are cleaner, more functional and helpful. All existing features from v6 remain.
2. Element Editors now allow folder selection via their Info tab.
3. Multi-select is more broadly available when granting access to objects or groups/users (with more areas covered in 7.0.2). Where you once had to single-select via dropdowns, you can now check-check-check via checkboxes in lists. This will save you time when granting object access or setting up security.
4. External Report Type Editor has been revamped to provide informative settings’ explanations for better user experience. A new setting for Microsoft Power BI Personal Bookmarks has been added.
5. There is now an option to set the maximum height for an Announcement. Once set, “Show More”/“Show Less” options will be available to expand/collapse the displayed message if the announcement extends beyond the maximum pixel height set.
    

A re-architecture is always a great opportunity to re-evaluate features and retire those that are not seeing widespread usage in order to stay focused on the functionality the matters. Here's a high level summary of what was retired, and what's still to come.

Retired:

1. Alert Inbox
2. Alert Workflows (often referred to as Managed Alerts)
3. Global Alerts (alerts available to all users with access to Metrics)
4. Stats Models for Datasets
5. KPI Visualization
6. Slideshows
7. Folder sidebar in Element Viewer
8. Multi-metrics (use Metrics with overlays instead)
9. Formula-based Metrics
10. Legacy Reports
11. XML requests

Coming in future releases:

• Admin page (arriving in 7.0.2)
• Pipeline page
• Target Type Editor
• Public Viewers for:
  • External Report
  • External Content
  • Reports
  • Metric
• Homepage/product tour for new users
• Quick Editor for Viewers

1. Currently, there is no Drill To link in Pie Chart Editors for Reports. 
2. On the Regular User Editor’s Elements tab, grids include columns that specify if a User can edit the assigned objects. 
3. Apache Pinot JDBC Driver does not support BIG_DECIMAL and TIME_STAMP data types.
4. When content at the Complete Stage of Publishing Workflow is modified, it is moved to New Content, without being decertified or made invisible.
5. Custom JavaScript Charts can’t be embedded into Reports in this version.
6. There is no way to validate the uploaded Custom Favicon file (in the Brand Editor)
7. While using API Toolkit, refrain from using XML requests as they won’t be executed. The common approach is to use JSON.
8. External Reports from file-based Plugins (like SharePoint) cannot generate images for any file type. Our recommendation is to use External Content instead.
9. Power Users with directly assigned Edit access to an External Report may not be able to access its Editor until they are also explicitly granted access to the the Data Source.
10. mi-app-restore may fail in the --dry-run mode.