Reltio Connected Data Platform: 2021.3 Weekly Releases

This page lists enhancements and fixes applied as part of our Weekly Releases in Reltio Connected Data Platform: 2021.3.

Release notes for Weekly Release 2021.3.6.0 - December 1, 2021

Fixes

Hub

You can save a profile only after adding the mandatory information, irrespective of the match rules associated with the profile.

Nested Attributes

Set the new flag, doNotTakeRequiredFromSubnested, to true in the tenant configuration to resolve any nested attribute errors generated when the validateRequiredAttributes flag is set to true.

If the sub-nested attribute has the required flag set to true and the nested attribute has the required flag set to false, then the request will not contain the nested attribute, and an error message saying that the nested attributes are required is not displayed. But, if the nested attribute has the required flag set to true, then an error message saying that the sub-nested attributes are required is displayed.

Before the doNotTakeRequiredFromSubnested flag was added to the tenant configuration, the error message saying that the nested attributes are required was always displayed when the sub-nested attribute has the required flag set to true and the nested attribute has the required flag set to false. To modify the doNotTakeRequiredFromSubnested flag, create a Support ticket.

Partial Override

Setting the enableNestedPartialOverride parameter to true changes the default tenant behavior for a partial attribute update in the case of nested attributes. For more information, see enableNestedPartialOverride Option.

Search

In the Activity Log, filtering based on metadata permissions is added for entity, activities, and export-related APIs, since earlier the activities for entities were not filtered based on the metadata permissions.

Survivorship

The primary attribute Uri is handled in accordance with the OtherAtrributeWinnerCrosswalk survivorship strategy when the attribute sorting is done during the Operational Value (OV) calculation, and the strategy is used in a fallback strategy at the third nested level or deeper. For more information, see Survivorship Rules.

Release notes for Weekly Release 2021.3.5.0 - November 18, 2021

Fixes

Cleanse

  • The Reltio Cleanser is updated. Now, the phone and email attributes are not considered for the Cleanse process after these are removed from the Reltio Cleanser crosswalk.
  • The Address Cleanser is fixed to calculate the correct values for response fields. The cleanser displayed incorrect values during pre-processing, when Coding Accuracy Support System (CASS) cleanse process was used to cleanse addresses.

Hub

On opening a profile and immediately navigating to another profile, Hub displayed the details of the earlier profile in the facets. The data of the latest selected profile was displayed after a delay. Now, the facet displays the details of the latest selected profile correctly.

Release notes for Fix Release 2021.3.4.1 - November 16, 2021

Partial Override

The partial override operation logic is modified to remove only the unmodified sub-attributes of a nested attribute from the entity when a partial override request and delete request are sent simultaneously. Also, the repeatAllOperationsOnConflict optional parameter is added to the tenant configuration to resolve any conflicts that arise due to multiple requests sent for the same attribute. For more information, see Simultaneous Update Requests.

Release notes for Weekly Release 2021.3.4.0 - November 10, 2021

Fixes

Connectors

The Salesforce connector uses a service user while replicating data from Salesforce to Reltio. The synchronization of data fails when the delete privileges for the Reltio_Sync service object are not granted to the service user for the Reltio Synchronization Service. The connector code has been fixed and the new privileges are granted to the service user to enable the synchronization process to restart.

Hub

  • In the Profile view, some attribute details were not visible. This was due to using non-wrappable container for tags in the Read mode, which made the Attributes View wider. This issue is fixed, and in the Profile view, the attribute details are displayed correctly.
  • In Activity log Perspective (Early Access), in the Date filter, clicking the CLEAR ALL button did not clear the specified search criteria. This issue is fixed, and clicking the CLEAR ALL button clears the specified search criteria. For more information, see Activity Log Perspective (Early Access).
  • On opening a profile and immediately navigating to another profile, Hub displayed the details of the earlier profile. This issue is fixed and the correct details of the latest selected profile are displayed.

Workflow

In the list of Workflow tasks assigned to a user, approved Data Change Requests (DCRs) were displayed. The Retrieve History Tasks API had inconsistent default values for the state filter resulting in this behavior. The default value is updated and the issue is fixed.

Release notes for Weekly Release 2021.3.3.0 - November 3, 2021

Fixes

Partial Override

A crosswalk was deleted and the same crosswalk was added to the entity subsequently due to the entity created date being later than the entity updated date. When two updates for the same object were sent simultaneously, the update that was sent first was applied last, hence this behavior. The behavior is fixed only when the operation is repeated in case there is a conflict.

Cleanse

Redundancies in attribute values were observed after nested attributes were cleansed. Running the Remove Attribute Duplicates task after the last cleanse removes redundant entries. For more information, see Remove Attribute Duplicates Task.

Reltio Platform

An incorrect count of events (false positives) was displayed in the Dead Letter Queue (DLQ) due to the event processing configuration on the UI cluster. A secondary Amazon Web Services (AWS) queue was used to process the events. To prevent the false positive count of events, the DLQ functionality is disabled for event processing on the UI cluster.

Workflow

The default state of Partial update was set incorrectly. The default state of Partial update is updated and functions correctly.

Release notes for Weekly Release 2021.3.2.0 - October 27, 2021

Fixes

Hub

  • In Hub, the profile icon was not displayed for the profiles. The inline images converter code was enhanced to display the profile icons.
  • In Advanced Search, when one of the conditions was deleted, the operator for the last condition automatically changed in Search. This issue is resolved and the operator does not change when one of the conditions is deleted.

Workflow

  • Using Data Loader, when a Data Change Request (DCR) was initiated, the Relation start and end objects information was not used. This resulted in the missing information about the start and end objects of the DCR. The DCR creation process is updated to link the start and end objects with the change request, and the issue is resolved.
  • Using the Inbox, users were unable to work with the Workflow tasks. The Inbox displayed an empty list since it was unable to process Data Change Requests (DCRs) that had conflicts due to the missing entity type in L3 configuration. This issue is fixed and the Inbox skips the DCRs that have conflicts. Thus, an empty list is not displayed and users can work with the Workflow tasks in the Inbox.

Release notes for Weekly Release 2021.3.1.0 - October 20, 2021

Fixes

Entity Processing

During the batch processing of a list of entities using the UpdateAttributesTask counter (POST api_uri/tenant/entities/_update API), if one of the batches was incompletely processed in the first attempt, and was successfully reprocessed during the next attempt, the entities in the reprocessed batch were not considered by the UpdateAttributesTask counter. Hence, the number of processed objects in the task result (numberOfProcessedObjects counter value) was less than the actual number of processed objects. This behavior is modified to display the correct number of processed objects in the task result.

Reference Data Management

In the Get Tree API, the hierarchy facets displayed the Reference Data Management (RDM) code instead of the values for all entities, except the root entity. Attribute values were transcoded only for the root entity. Hence, the labels displayed the code for all other entities. For the API result, transcoding of attribute values was added to lookups of all entities, and the issue is fixed.

Reltio Insights

Numerous partitions created for Resilient Distributed Datasets (RDDs) caused the Entity export to fail with an error message, Job aborted due to stage failure. This issue is fixed.

Search

Incorrect configuration of Index Lifecycle Management (ILM) caused slowing of performance and issues with search capabilities in the tenant. It also resulted in overloading of Elastic Search and delayed processing of the Simple Queue Service (SQS). The configuration was changed and the issue is fixed. ILM was also optimized to reduce simultaneous updates and prevent delays in the future. For more information, see Manage the index lifecycle.