• In the Hub, we added an option to restore the default layout for the Dashboard and the Profile view. Your personalized settings for these UI pages will be reverted to the default layout configured in the UI Modeler. After the default layout is restored, you will still have the option to revert back to your personalized settings for a few minutes. For more information, see topics Refresh facets and restore default layout for Dashboard and Restore default layout for Profile view.
• We introduced a new UI configuration that initiates a background check, in the view and edit modes, for any updates or data enrichment to a profile. This ensures the most recent and updated version of the profile is always available to the users. While configuring, you can specify the entity types for whose profiles this check must be initiated. You can also opt to have the details refreshed automatically, or display a message asking the user to refresh the page manually. For more information, see topic Adding a Profile.

We introduced a maximum size limit for the authentication object. If a user has too many roles or permissions when creating a token, they will get this error message:

"Authentication object size exceeds the limit. This might be because of very large set of permissions assigned to the user. Please contact the Reltio support team to resolve the problem."

Previously, time-series charts in the Data Quality (DQ) dashboard displayed an error in some cases of localization. Localization was used where it should not have been used, due to which the error was displayed. We fixed the way localization is done in these cases, and localization now no longer affects the time-series charts in the DQ dashboard. For more information, see topic Analyze DQ dashboard charts.

• In the Frequency analysis chart, the Advanced Search page used the string data type for the Search filter. This led to incorrect search results. To ensure relevant search results, we enhanced the filter to use the boolean data type when you use the Advanced Search page. For more information, see topic Frequency analysis.

• In the Value distribution chart, the Advanced Search page used the After and Before search filters. This led to incorrect search results. To ensure relevant search results, we replaced the filters with the Within filter in the Advanced Search page. For more information, see topic Value distribution.

• You can now control whether you ignore an entity's updated attribute value in the Profile UI or not using the forceOvForUiUpdates parameter in your entity configuration. By default, the parameter is set to true, so the updated value in the Profile UI is ignored. Set the parameter to false if you don't want the updated attribute values to be ignored. For more information, see topic Add an entity type.

• We enhanced the Sources perspective to quickly identify nested and simple attributes values for focused crosswalks. Now, all attributes of focused crosswalks are colored and all attributes of non-focused crosswalks are grayed out. For more information, see topic Sources Legend.

We upgraded our queue monitoring infrastructure to a newer technology. As part of that change, you'll have data going back to April 18, 2023. You will no longer have access to historical data prior to that date. For more information, see topic Monitoring Queues.

• In the Profile page, you couldn’t resize the right panel due to its fixed width, to view more details in the main page. This was also the case in the Sources, Graph, and Potential Matches views. We enhanced these views, so you can now resize the right panel to a width that suits your requirement. Hover over the border of the right panel, and drag it to the required width. For more information, see topics Profile Tabs, Get started with the Potential Matches perspective, and Sources Legend.
• In the Legend tab in Sources view, you can now unmerge sources from the Crosswalk swim lane chart also. The existing option to umerge is available for each entity in the lower section of the Legend tab, but you now have the additional option to unmerge from the Crosswalk swim lane tree chart. For more information, see topic Unmerge Sources.
• In the Workflow tab in the Profile view, you can now submit comments and complete the action for the workflow task in one click of a button. Enter your comments and click the corresponding action button, which results in your comment being submitted and the action being executed. Of course, you can do these two actions individually too, but this is one click less in your task. For more information, see topic Add a Workflow Task.

We have updated processing, so if any one of the objects: parent entity, child entity, or reference attributes, encounters an error, the entire profile won't load.

• In the Profile view History tab, we now compare the historical slice that you select from the tab with the current view by default. The details in the selected slice are compared to the current view and the changes are displayed in the Profile view. You also can compare it with the previous historical slice. For more information, see topic History tab.

• In the Profile view, when you added a date attribute for a new or existing profile, a completely different date was sometimes displayed. The local date was calculated incorrectly, which led to this issue. We now ensure that the local date is calculated correctly, so the profile displays the date as you you added it.

• We changed the default behavior of the existing transitive matches filter in the new UI's Potential Matches view to hide the transitive matches for an entity. Select the Show transitive matches filter to display the transitive matches for the entity. For more information, see topic Select the potential matches for a profile.
• In the Hub, when you created or edited a profile and added attributes using the option, you couldn't immediately determine where the attribute was added. You had to scroll through the Profile page to find the newly added attribute and then add values to it. We enhanced this logic, so now you are immediately taken to the new attribute as soon as you add it using the +MORE ATTRIBUTES option. For more information, see topic Adding a Profile.

• In the Profile statistic dashboard in the Hub, you could see wrong data in some of the map charts configured for the tenant. Country names referenced on the map were incorrect and the Advanced search displayed details for an entirely different country when selected on the map. We updated the data in the topography JSON file and now the correct data is displayed in the map charts. For more information, see topics Profile Statistic Dashboard and Configuring Dashboards.
• In the Profile view, you could save a customer entity without providing mandatory information. The appropriate error message was not displayed on saving the profile. We fixed the error handling process, and now you can save a new customer entity only after providing the mandatory information. For more information, see topic Editing profiles.

We provided additional information in the banner notification that displayed in the Profile view to provide additional information on Data Validation Function (DVF) error functions. Use this information to troubleshoot the cause of the error or warning. For more information, see topic Data validation function.

• When you merged profiles after searching and navigating to the Potential Matches view, you couldn't view the link in the Profile band. We changed the way we handle merge events in the Profile band navigation, so now you can use the Search results link in the Profile band to browse through profiles. For more information, see topic Merge potential matches.
• In the Profile view, when you created a Data Change Request (DCR) after making suggestions for the profile, you couldn’t see the descriptions or the ? icon next to the attribute until after the profile was approved. We now display these descriptions even while the Profile is pending approval. For more information, see topics Profile Attribute Facets, Workflow tab and Editing profiles.