1. Metric Insights containers/pods can now be run with with non-root (least privileged) system users.
2. Major re-architecture of our Remote Data Processor.
3. AWS Graviton (Beta) support is introduced in this version, allowing MI on Arm64 .
4. RedHat 9 is supported.
5. Multiple API improvements, intended to support more feature-rich custom Portal Pages.
6. Chatbot has been improved for better performance and usability.
7. Tableau Plugin can collect metadata about whether a Dashboard has been optimized for mobile.
8. Plugin Config (for advanced plugin configuration) includes multiple new Parameters to control SSL validation and connection security for such Plugins as QlikView, Power BI Report Server, TIBCO WebFOCUS, SAP Business Objects, SAP Analytics Cloud, Microsoft Purview, and MI Portal Pages.

The primary Docker images used for standard deployments are:

1. web – docker.metricinsights.com/metric-insights/release_6_4/21
2. dataprocessor – docker.metricinsights.com/dataprocessor/release_6_4/26967
3. seed – docker.metricinsights.com/seed/release_6_4/39949
4. data-analyzer – docker.metricinsights.com/data-analyzer/release_6_4/13
5. monitoring – docker.metricinsights.com/monitoring/release_6_4/999

Additional images:

1. logger (needed for simple deployments) – docker.metricinsights.com/logger/release_6_4/29
2. mysql (used for simple deployments with mysql running locally) – docker.metricinsights.com/mysql/release_6_4/32

AWS Graviton (Beta) has been introduced. Graviton provides significant cost and performance efficiency improvements through the use of Arm64 CPUs.

1. element_info API allows for modification of Name, Description, and Publishing Workflow.
2. If a User does not have access to an Element, element_info API will return either the Element-level Access Denied message or the Category-level message.
3. metric_data API has been enabled for Regular and Power Users.
4. search_history API endpoint has been updated with a POST method, which allows adding new items.
5. Search API has been updated with two new parameters: sort and content_type.
6. logs/level endpoint has a new parameter level that can accept one of the following values: INFO, DEBUG, TRACE, WARNING, ERROR. 
7. Added /api/token endpoint for MI token validation.

1. Previously, when running the !tags command, a chatbot was showing a User all Tags available in the system. Now, it shows only Tags that are applied to content to which the user has access.
2. Chatbot logs can be downloaded from the Status Monitor "Errors & Logs" tab by clicking Get Logs.

1. Port 32250 on the Dataprocessor container has to be opened for incoming connections in order for RDP to function.
2. Dataprocessor is now working on JDK 17.
3. We have modified error messages for SQL and Plugin Data Sources to be more clear and understandable. 

We have updated/removed some of the library dependencies to mitigate CVE-2019-8331 and CVE-2022-39261 in this version.

1. We have updated the Data Analyzer libraries, Ixml and Axios, for improved security. Additionally, multiple changes to optimize Search speed and performance have been introduced. 
2. The new System Variable, GLOBAL_SEARCH_DATA_ANALYZER_INDEX_SKIP_CLICKS, can now control whether or not you want to include user clicks to indexation. User clicks are used for sorting results in search and require longer indexation times when included. 

1. Restoring a Sub-folder is now possible even if the name of its parent Folder has been changed. This was not possible in the previous release. 
2. Metric Insights provides an opportunity to download the Migration Tool logs. The zip archive will be downloaded as a part of the main error and logs archive from the Status Monitor Page. 
3. External Report and External Content Type are now included in migration of Elements as dependent objects in case these Types do not already exist on a target system.
4. Portal Pages are migrated with their sharing relationship to Groups.

1. ENABLE_PUBLISHING_WORKFLOW_AUTOMATION_RULES now defaults to “Y”.
2. The ability to see and use the Share Now functionality in the Element Viewers and Preview Pages is now controlled by the DISABLE_SHARE_NOW System Variable.

1. The mi_ldap_usersync_run_log table has been added to Dashboard DB to record start and end times for LDAP Usersync processing.
2. The system can now cache users during LDAP Usersync to save time for querying the same user against LDAP when the user exists in multiple groups. In general, the process of retrieving users with LDAP Usersync has been optimized by decreasing the number of requests to LDAP.

1. Services inside containers are now run by one unprivileged user. For orchestrated environments the ownership for the network shared volume must be manually set to www-data, uid: 33 before updating to 6.4.1.
2. We have implemented support for RedHat 9.
3. Custom authority certificates with extensions cer, crt, pems can now be added to the web container by copying into the /opt/mi/ssl/ca-certificates/web directory of the web container and restarting it. 
4. Only one installer instance can run on a server at once. 
5. The approximate remaining time to finish the installation is now displayed in logs.  
6. Metric Insights application is now automatically using the latest Chromium version.
7. We have adapted Kubernetes deployment manifest to work with ingress controllers nginx and traefik with versions 1.20 and newer. The latest Kubernetes version is used by default and can be controlled by the new version parameter.
8. Istio Ingress Controller is now supported.

1. Patcher has been added to chatbot and mi-nlu services.
2. Elements can be made visible/invisible in a mobile application. This is controlled via the Visible “in Mobile App” setting in all Element Viewers.

1. mi-crypt works correctly with passwords starting with any of the supported special symbols.
2. The "Undefined Index" error appearing in Errors & Logs that was related to the empty Category column in Search Setup Datasets has been addressed. 
3. search_history API is not returning null for deleted Elements. If an Element is deleted, information about this Element is deleted too.
4. Previously, Manage Index was failing to create lengthy custom indexes for Datasets. The issue has been fixed in this release. 
5. LDAP Usersync was adding Users and assigning/removing them to/from groups, but these changes were not reflected in Search. A new option, --enable-search-index-update, has been added to be able to trigger Search Index updates after applying changes to Groups. 
6. A property “name” for a Dataset has been included in the search API response.
7. The Engagement Tab in Element Editors is now reflecting correct information, without skipping particular dates.
8. Some of the grids on Tabs in External Report Editors were taking longer times to load. This has been fixed by distributing requests to avoid sending too many of them at the same time. 
9. The Sub-Categories URL is no longer throwing the Access denied message and works correctly for authorized Users. 
10. A part of the LDAP group Distinguished Name could be cut off when the group was created in Metric Insights. The issue occurred because the name included a comma (,), but this has been fixed.
11. GET custom_field_value and custom_field weren’t working correctly after the introduction of Custom Field Sections. We have addressed this issue in this release. Additionally, a new method, PUT, has been implemented for custom_field_value. 
12. Uploading of ZIP with files that are whitelisted for Portal Page Assets was failing due to exceeding memory limits. The problem no longer occurs in the system.
13. Increasing/Decreasing Popularity grids on the Content Center’s Content tab are not showing duplicate entries and incorrect values for Power Users.
14. Engagement for External Content with manually sourced URLs now properly displays in Content Center for Power Users.
15. The assigned Tags are no longer migrated with their original IDs to a target system, but are replaced by identical Tags with their unique IDs that exist on a target instance.
16. The "mi-crypt:cannot decode string: error reading input file" error thrown when testing connection and collecting images for Power BI Cloud is not appearing in Status Monitor.
17. The embedded Power BI External Reports were taking a slightly longer time to load in the application. We have shortened the server response waiting time, which allowed us to achieve better results. 

1. In case you are using RH9, Docker cannot be installed out-of-box. Reach out to our support for assistance.
2. The Elements tab does not display the correct Engagement count. Refer to Content Center for the actual number. 
3. For Microsoft SQL Data Sources with invalid certificates, it is required to upend “;trustServerCertificate=true” to the JDBC connection string to establish connectivity.
4. OBIEE Plugin is still included in the Plugins list; however, the Plugin is no longer fully functional and will be removed from the system in 6.4.2.