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.13.0 - February 9, 2022

What's New

To keep a check on the performance due to the accumulation of unwanted tasks, the Time to live (TTL) can be enforced on Closed and Invalid tasks. By default, the TTL is set to one year. Starting from March 02, 2022, TTL would be enabled for all tenants, by default. All closed and invalid tasks older than a year would be removed from the Inbox. You will not be able to search or filter for such tasks. For more information, see Time To Live (TTL) for Workflow Tasks.

Fixes

Console

For Google Pub/Sub queues, we have removed the extra validation in the Tenant Management application. This ensures validation errors are displayed only if required.

Reltio Insights

We simplified queries used in entity and relation views. Complex queries were sometimes resulting in the Resources Exceeded error.

Reltio Platform

We have enhanced the processing of the select parameter in the Get Hops API (/entities/{entity object URI}/_hops). For more information, see Get Hops.

Workflow

We have modified the pod change mechanism. Now, when the data loader jobs change from one pod to another, the interrupted records are listed and reloaded without causing any jobs to fail.

Release notes for Fix Release 2021.3.12.1 - February 4, 2022

Hub

Now, when you hover over a crosswalk in the Sources perspective, the Delete option is displayed as expected.

Release notes for Weekly Release 2021.3.12.0 - February 2, 2022

What's New

Hub

We have enhanced the user experience for selecting the year from the calendar. You can now select the year directly, instead of using arrows to browse through the months.

Match

  • For Relevance based match rules, we have removed the irrelevant attribute level match property from the Verify Matches API's response.

  • We have enhanced the Verify Matches API's response to display the OV strategy and ignore in token values through the useOVOnly and ignoreInToken fields. For more information, see Verifying Matches.

Fixes

Data Loader

When the number of columns didn't match between a data loader job's excel file and mapped columns, the CSV files were not generated correctly. Now, Data Loader generates the CSV files based on the maximum number of columns in the excel files.

Security

  • Due to an error in GBQ logging, incorrect user names and customer ID combinations were being displayed in some scenarios. This is fixed by ensuring that the Customer ID value is always considered in the logs.
  • We fixed an issue where the Auth Log API was throwing an exception related to the clusterName field in GBQ.

Workflow

  • Some additional security checks were causing a few Data Loader jobs to fail. These checks have been removed and the jobs complete successfully.
  • Invalid configuration did not allow the connection to be terminated and a few Data Change Requests (DCRs) could not be assigned. The implementation to configure the time outs for closing the unused connection is modified to resolve the issue.

Release notes for Fix Release 2021.3.11.1 - January 27, 2022

Connectors

Salesforce to Reltio synchronization of data failed because of a regression issue in the sync retry mechanism. The issue has been fixed and new quality checks are in place to avoid such issues in future.

Release notes for Weekly Release 2021.3.11.0 - January 26, 2022

Data Insights

We have optimized Reltio Data Science jobs to overcome potential connection limits while running Reltio extract.

Hub

In the main Profile page, you can now use the vertical scroll bars effortlessly even on touch screen devices.

Reltio Analytics

Support for merge on the fly is now enabled by default for new users. Existing users must contact support to get it enabled and then run sync jobs to update secondary storage with existing merge on the fly records.

Reltio Insights

  • We have modified the internal logic for joining data to prevent DQ jobs from failing. Restart DQ jobs that failed earlier.
  • We have modified the ovOnly parameter to ensure that when it is set to true, the crosswalk includes the Uniform Resource Identifier (URI) of only the attribute for which the Operational Value (OV) is set to true. And only when the ovOnly parameter is set to false, the crosswalk includes URIs of all attributes.

Release notes for Fix Release 2021.3.10.1 - January 20, 2022

Data Loader

Data Loader jobs that use Amazon Simple Storage Service (Amazon S3) to load data now consider the AWS region while downloading the source file from Amazon S3. This ensures that the data load jobs complete successfully.

Release notes for Weekly Release 2021.3.10.0 - January 19, 2022

Fixes

Console

In Data Modeler, for the entity type - Name attribute, only letters, numbers and underscores were allowed. Now, special characters are also allowed for this attribute.

Crosswalks

Searching for an entity with an empty crosswalk no longer results in an error.

Hierarchy Management

The improved Hierarchy Management facet now displays all referenced attributes configured for an entity in the secondary label pattern.

Hub

  • The new Sources Perspective view displays all values of a nested attribute, instead of only the operational values.
  • In the Search Results page, overlay issues in the table view are fixed and the profile details are correctly displayed.
  • The new Sources Perspective view displays only the relevant sources for the period specified using the History tab. For more information, see Tabs.
Reltio Platform

During the POST API request, you will now receive an error message when a batch contains large objects that exceed object size quotas and limits. On finding a large object in a batch, only the identified entry fails, not the entire batch. You may see one or more of the following error messages:

  • ENTRY_HAS_LARGE_OBJECT(921) – Displays when an object exceeds size when sending a POST/entities or POST/relations request.
  • ENTRY_HAS_OBJECT_USED_IN_FAILED_ENTRY(922) – Displays when an object that is referenced by a failed object exceeds size when sending a POST/entities or POST/relations request.
For more information, see, Object Size Limits.

Reference Data Management

When the parent attribute of an entity is empty, and the dependent attribute has a value, the platform does not perform RDM transcode now. Therefore, no transcode error is associated with this attribute, and, such an entity is not displayed in the list of entities with RDM transcode errors.

Workflow
  • If the crosswalks of an entity have different Data Provider and Data Contributor Provider options they are not merged.
  • The retrieval of mapping details is improved and now the tenant IDs are used for validating access to tenants.

Release notes for Fix Release 2021.3.9.2 - January 14, 2022

Reltio Insights

Restart the export jobs that were failing after they were refreshed.

Release notes for Weekly Release 2021.3.9.0 - December 29, 2021

What's New

Match

  • We have added the documentsWithOmittedTokens inspection to identify match rules generating a high number of match tokens. For more information, see Inspections for Tokens.
  • We have updated the Inspection for Overcollisioned Tokens to use the results of overcollisionedMatchToken calculator instead of the mostFrequent calculator. For more information, see Inspections for Overcollisioned Tokens.

Fixes

Cleanse

We have improved the design of the attribute re-cleanse mechanism. Now, if the attribute value doesn't change during cleansing, the attribute URI remains the same.

Reltio Platform

While using an LCA hook with the useOnlyOvValuesInReferencedEntities parameter set to true, updating an entity does not create extra events regarding removal of non-operational values anymore.

Release notes for Fix Release 2021.3.8.3 - December 23, 2021

Fixes

Connectors

In the Salesforce connector, we have updated the Compare function to ensure that the multiple comparison behavior is the same, irrespective of the position of the Compare function in the mapping.

Release notes for Weekly Release 2021.3.8.0 - December 15, 2021

Fixes

Nested Attributes

Before cleansing, the nested attributes of an entity are checked and recleansed only if the attributes have changed.

Reference Attributes

The ENTITY_CHANGED event is not created when an entity's attributes are not changed. For more information, see Events API.

Hub

In the Simple and Advanced search pages, the Search results display only the selected Boolean value - Yes or No for attributes, instead of True or False.

Release notes for Weekly Release 2021.3.7.0 - December 8, 2021

What's New

Reltio Platform Status Page

The Reltio Platform Status Page is now available at status.reltio.com. For more information, see Reltio Platform Status Page.

Fixes

Bulk Update

During a bulk update, emails are now only sent for completed tasks, unlike earlier when emails were also sent for paused tasks.

Export

In Export, selecting and deselecting attributes to define an Export job does not disable the Continue button now, unlike earlier.

Hub

When a task is restarted during a bulk update, we first save the accumulated number of processed objects in the database and then restore them. This prevents you from receiving an incorrect number of processed objects when the task is stopped and restarted.

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 (new view).
  • 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.