Reltio Connected Data Platform: 2021.2 Weekly Releases

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

Release notes for Weekly Release 2021.2.14.0 - September 22, 2021

What's New

Search

The safety of the file-based search is improved by implementing a new and secure process for uploading and using the search file. For more information, see Uploading a File for File-based Search.

Fixes

Connectors

During the merge operation, the winner and losers are determined based on the Salesforce ID in the crosswalk. In certain cases, this determination failed. The issue has now been fixed and the connector determines winner and loser from Salesforce account IDs alphabetically. This ensures, that the lowest value is the winner and all other values are losers. For more information, see Merging and Unmerging Records.

Hub

Using the Bulk Update, when the address status for profiles was updated an error was displayed indicating the process failed due to an unexpected error. The inSameAttribute operator was modified to ensure that the Bulk Update does not display the error.

Survivorship

The fallbackUsingCriteria parameter was defined for a survivorship rule configuration without defining a fallback strategy, which led to a validation exception warning. To prevent a recurrence of the warning, thefallbackUsingCriteria parameter must be defined in the configuration only when a fallback strategy is used in the survivorship rule configuration. For more information, see Survivorship Rules.

Workflow

For all the tabs of the Inbox application, Workflow users experienced a slow performance of getting tasks API. The performance issue was caused by a significant increase in the size of the database (DB) while adding duplicate rows. The size of the DB became a problem for a latency of SQL queries that led to overall performance degradation for getting tasks APIs. This issue is fixed and duplicate rows are not added.

Release notes for Weekly Release 2021.2.13.0 - September 15, 2021

What's New

Search

The file-based search functionality is now extended to support the Comma Separated Values (CSV) format. For more information, see Filtering Entities and Relations Filtering.

Fixes

Console

While defining the conditions for a Data Validation Function, a reference attribute was available even though Data Validation Function does not support reference and relation attributes. We have updated our code to fix this issue.

Hub
  • While editing some profiles, the page became unresponsive and the changes were not saved. The process of saving profile changes is modified so that validation is ignored for warning cases, and the other changes are saved.
  • Changes to default rulesets, or, ruleset details like label or description, affect all users. Hub now displays a warning message to confirm before allowing you to make such changes.

Workflow

Tasks with empty data change requests did not show up for non-admin users. Access roles cache is modified to ensure non-admin users are able to search for closed tasks with empty DCRs.

Release notes for Weekly Release 2021.2.12.0 - September 8, 2021

What's New

Hub

Graph Search is enhanced, and a new operator named, Missing is added to enable searching of entities that do not include records for the selected relationship type. For more information, see Adding a Relation.

Fixes

Connectors

While synchronizing data between Reltio and Salesforce, some of the tasks were failing as a result of an API timeout in the Reltio Platform. To handle such scenarios, a retry mechanism has been added so that tasks can execute successfully if a subsequent retry is successful. In addition, when the defined number of retry attempts fail, the status of the task changes to failed. For more information, see Synchronization Process.

Console

In the Tenant Management, while editing queues and on selecting the Type Filter, the ENTITIES_MERGED option was not displayed. This issue is fixed. Match events are supported along with CRUD events and the ENTITIES_MERGED option is displayed. For more information, see Managing External Queues.

Hub

In the Potential Matches screen, the list of attribute values for the main profile was not collapsible. This is fixed and the attribute values list is collapsible.

Reference Data Management

The full-text search is modified and enables searching for any lookup code or value in the RDM UI without any limitations on the request Uniform Resource Locator (URL).

Reltio Analytics

  • The Export V2 JSON had incorrect values because OV strategies were lost after the EntityTO conversion process. Reltio Analytics is modified and uses standard platform serialization to resolve this issue.
  • A few objects were missing from the Export V2 output JSON, and the structure was unlike the Export V1 output. The S3 compaction process is updated to handle the persistRelationEdgeType=true flag correctly to resolve this issue.

Reltio Platform

When the Uniform Resource Indicator (URI) from a deleted crosswalk source is used in a Data Change Request, the Reltio Platform is updated to provide error messages, such as OBJECT_TYPE_NOT_FOUND, instead of a NullPointerException.

Release notes for Fix Release 2021.2.11.1 - September 7, 2021

Search

The Fuzzy search displayed redundant results. The search query optimizer logic, which determines the number of words that match the fuzzy filter, was corrected to ensure that the search result is precise, and displayed as expected.

Release notes for Weekly Release 2021.2.11.0 - September 2, 2021

Fixes

Connectors

  • After a Reltio entity is deleted, the Salesforce Connector deletes the Salesforce object only when the entity is not filtered.
  • Salesforce supports the mapping of a single reference attribute with multiple salesforce objects. Therefore, a reference attribute can have multiple crosswalks. To prevent unexpected deletion of related objects, identification of the winner and loser entities is modified.

Hub

The synchronization issue of stored user preferences and updates to the User Interface configuration is resolved, and the Search page is correctly displayed.

Match

In some cases, there were inconsistencies in Reltio Analytics and Search due to a pair of entities having two different statuses (Potential_match and Not-A-Match) in matching at the same time. This issue is fixed and only one state is allowed for a pair of entities in matching.

Reference Data Management (RDM)

The RDM Client is enabled to retry sending requests to the RDM API, if the requests failed with the HTTP status code 502. For more information, see API Error Codes.

Reltio Platform

The rulesets for a survivorship group of an entity type could not be configured, because the survivorship group was not retrieved due to the incorrect Uniform Resource Indicator (URI) comparison values. The Reltio Platform is updated to retrieve the correct survivorship group of an entity and configure the rulesets for it. For more information, see Ruleset Configuration.

Workflow

Data load was failing due to concurrent updates on the same entity. To minimize data load failures, exponential back-off delays were added.

Release notes for Weekly Release 2021.2.10.0 - August 25, 2021

What's New

Hub

In the Potential Matches Perspective (Early Access), the Potential Matches tab now enables you to either merge or mark potential matches as not a match using Match Score. For more information, see Potential Matches Perspective (Early Access).

Match

The Verify Matches API is enhanced to include a reason field, which provides an explanation or the reason for matching or not matching a given pair of records using the Match IQ match method. For more information, see Verifying Matches.

Fixes

Reltio Platform

  • For entities with relations that were missing the start or end object crosswalks, Reltio Platform did not allow the reference attribute to be pinned or ignored. Such entities are handled by processing the reference attribute appropriately and the pin or ignore flags are set successfully. For more information, see Sources and Crosswalks.
  • The Reltio Support Log In password could not be reset due to invalid reCAPTCHA keys error. The CAPTCHA keys are updated, and the error is resolved.

Match

To avoid errors during the validation of matching, the Verify Matches API is updated to process match rules with missing relevance values. For more information, see Verifying Matches.

Release notes for Weekly Release 2021.2.9.0 - August 18, 2021

Fixes

Cleanse

Updating an entity resulted in the recreation of all the attribute values associated with the ReltioCleanser crosswalk, due to which the pin or ignore status of the simple and nested attributes was lost. This issue has been resolved. Updating an entity does not result in losing the pin or ignore status of the simple and nested attributes.

Reltio Analytics

In Reltio Analytics, after Batch Export, the datasets did not include all the views and tables, because the descriptions of some attributes exceeded the character limit of 1024 characters. This issue is fixed, and the descriptions of all attributes are trimmed to not exceed 1024 characters. For more information, see Understanding the Structure of Data in Reltio Analytics.

Reltio Platform

When the incoming JSON requests include crosswalk values that are null, detailed error messages are displayed, instead of the null pointer exceptions. When the request body is missing in the request, the CROSSWALK_VALUE_SHOULD_BE_SPECIFIED error is displayed. In the request body, if a crosswalk value is not specified, CROSSWALK_VALUE_MISSED error is displayed.

Search

For nested attributes, the query builder was modified, to ensure the relevant search results are displayed on searching entities using the containsWordStartingWith filter. For more information, see Filtering Entities.

Release notes for Fix Release 2021.2.8.1 - August 12, 2021

Reltio Platform

For entities with a large number of reference attributes (over 10000), the Connections API request was timing out. Now, the performance of the connections algorithm is optimized. An additional parameter - returnLabels, is introduced. When the parameter is set to false it does not retrieve the entity or relationship labels, and thereby enhances the performance of the API request. For more information, see Requesting Multiple Entity Connections with a Request.

Release notes for Weekly Release 2021.2.8.0 - August 11, 2021

Fixes

Match

The Verify Matches API is enhanced to include additional information about strict constraints in its responses. For more information, see Verifying Matches.

Reltio Platform

When bulk operations were done on an entity's sub-attributes, the updates were reflected in the User Interface (UI), but the email notifications were not generated. The Platform is now enhanced to ensure that the email notifications are generated. For more information, see Bulk Operations.

Search

  • When multiple filter conditions with the same entity URI were specified as the value for a search query, Search used only one of those filter conditions. Search has been enhanced to use all specified filter conditions.
  • The behavior of Fuzzy Search is enhanced to ensure that its search result is based on the word length, and the percentage of the difference between the attribute values being matched.

Release notes for Fix Release 2021.2.7.1 - August 6, 2021

Workflow

The Workflow service is modified to ensure that the workflow tasks can be approved or rejected from the Inbox without any issues.

Release notes for Weekly Release 2021.2.7.0 - August 4, 2021

What's New

Export

Export API exports all types of attributes that include hidden attributes. These attributes are not shown in the UI, but available as part of the entity or relationship data model. While exporting entities or relationships, you had to list individual hidden attributes.

A new Export API property sendHidden has been introduced now. This property controls if hidden attributes will be included into the exported results. By default, it is set to true. So all the attributes are exported if this new property is not used. But now users can set this property to false, which will exclude all the hidden attributes from the exported result. This property can be used to export only non-hidden attributes without the need to list them gradually. For more information, see Export Entities or Export Relations.

Fixes

Reltio Analytics

In Reltio Analytics, delay in synchronization impeded the display of Events. Based on the tenant's location, datasets are moved to the European Union (EU) servers to overcome the delay.

Reltio Platform

  • The value of a specific field was not chosen as the operational value if the value belonged to a crosswalk from the winner entity. With the existing set of Operational Value strategies and auto-generators, this behavior could not be configured. The new configured behavior uses a new strategy for Operational Values - WinnerEntityCrosswalk, which has been implemented to choose the winner values from the winner entity. For more information, see Survivorship Rules .
  • When an entity was updated, all values using the ReltioCleanser crosswalk were recreated, and the entity pin value was overwritten. Now, the functionality is enhanced, and the pin or ignored value is retained.

Release notes for Weekly Release 2021.2.6.0 - July 28, 2021

Fixes

Cleanse

Earlier, the cleansed operational value could not be merged with an operational value that was not generated by a cleanser as it was not transcoded properly. Now, this issue is resolved. Additional transcoding for lookups has been added, which allows nested attributes to merge as expected.

Hub

  • Earlier, when a search query with multiple conditions was saved, the correct count of search results was not displayed in the Saved Search Dashboard. Now, this issue is resolved. When a search query with multiple conditions is saved, the correct count of search results is displayed in the Saved Search Dashboard.
  • Earlier, for an entity, multiple values of an attribute could not be deleted at an instance. Now, this issue is resolved. For an entity, multiple values of an attribute can be deleted in an instance.
  • Earlier, while creating an entity and including special characters in the entity name, disabled the Save button resulting in data loss. This happened due to the incorrect validation configuration. To resolve this issue, the user was guided to configure the validation correctly via Data Validation Function.

Match and Merge

Earlier, GBQ displayed invalid IDs in the Match column because incorrect IDs were sent using the /entities/{id}/_notMatch endpoint. Now, we have added a validation to check all incoming IDs and display the Object not found error for incorrect IDs.

Security

Earlier, relations of entities could not be created or updated even when the RDM attribute values met the filter conditions. Now, this issue is fixed. Relations of entities can be created and updated successfully.

Release notes for Fix Release 2021.2.5.1 - July 27th, 2021

Reltio Platform

While loading data, some parts of the events were failing due to the incorrect status, offline reported by some processors in the internal events queue. This resulted in the rapid increase of the queue size and the waiting time for messages in the queue. This behavior is fixed and the correct status is reported by the processors.

Release notes for Weekly Release 2021.2.5.0 - July 21, 2021

What's New

Reltio Data Science

Now, using the withDeleteEvents flag, you can delete interactions. When the withDeleteEvents flag is set to true, it creates the DataDeleteJob event, which sends the interactions deletion requests to the MDM server.

Fixes

Hub

Earlier, in Hub, the Profile Statistics section did not include the count of deleted profiles - an outcome of periodic scheduled tasks. Now, this issue is resolved. In Hub, the Profile Statistics section includes the count of deleted profiles - an outcome of the periodic scheduled tasks.

Reltio Data Science

Earlier, in the Match Source table, match rules were not stored for events, when the potential match was removed. Now, in the Match Source table, match rules are stored for events, when the potential matches are removed.

Reltio Platform

  • Earlier, the API endpoint for deleting interactions was unable to process IDs that include slashes. Now, this issue is resolved. The API endpoint for deleting interactions has been enhanced and IDs that include slashes are processed without any issues.
  • Earlier, during an entity partial override request on using a null value for a reference attribute, the relation mentioned in the request was deleted if a match was found for the relation. Now, the issue is resolved. Using a null value for a reference attribute during an entity partial override request results in removing only the incoming crosswalk from the match found for the relation, instead of deleting the relation.

Search

Earlier, using the Qubole script to delete interactions, removed all the interactions from the primary storage, without synchronizing with the secondary storage leading to inconsistencies. Now, this issue is resolved. The Qubole script has been enhanced to use the Platform Batch Delete API, which deletes interactions without causing any of the earlier inconsistencies.

Security

Earlier, the client authentication logs could not be filtered and viewed. Now, this issue is resolved. On filtering the Log API using a client ID, the corresponding authentication logs for the client are displayed.

Release notes for Weekly Release 2021.2.4.0 - July 14, 2021

Fixes

Connectors

  • Earlier, the data models had to comply with the Account 360 data model for mapping verification. Now, for the D&B self-service mapping APIs, the mapping verifications are enhanced to accommodate customer-specific data models.
  • Earlier, on updating the mapping, the Reltio-SFDC connector did not restart the profile when the worker process hung. Now, this issue is resolved, and the connector kills the hung worker process within 10 minutes, and a new profile is restarted on all the worker processes.

Match and Merge

Earlier, creating the cleanse dictionary using UTF-8 encoding caused issues due to the Byte Order Mark (BOM) signature in the file. Now, this issue is resolved. The BOM signatures have been removed to fix this issue.

Reltio Analytics

Earlier, the potential matches displayed in the UI and GBQ were not consistent because the match events were not processed as expected. Now, this issue is resolved. The processing of match events is enhanced and enabled. We are introducing a new reducing mechanism to find the correct record. Also, two events have been added.

The following limitations still exist:

  • For a pair of entities having more than one potential match, and if one of the matches is removed the entity is skipped in GBQ. For example: when a rule is updated or removed.
  • For a pair of entities having a manual match and a potential match, only the manual match is returned in GBQ. In the UI, the count is not affected because a manual match is displayed as manual rule within the potential match record.
  • For a pair of entities having more than one potential match, only the latest are returned in GBQ. It does not affect the count. For example: when a rule is updated or duplicated.
  • Transitive matches are not supported in Reltio Data Science.

Reltio Platform

  • Earlier, when the singleAttributeUpdateDate value was lesser than the crosswalk updateDate value, the responses for the entity’s POST and GET requests were inconsistent. After the POST request was sent, the GET response did not include the singleAttributeUpdateDate attribute. Now, this issue is resolved. When the singleAttributeUpdateDate value is lesser than the crosswalk updateDate value, the responses for the entity’s POST and GET requests are consistent, and the singleAttributeUpdateDate attribute is not displayed in both the responses.
  • Earlier, while retrieving an entity version for the specified Time parameter, the survivorshipAdvancedBehavior setting was not considered. Now, this issue is resolved. While retrieving an entity version for the specified Time parameter, the survivorshipAdvancedBehavior setting is considered.
  • Earlier, loading entity data including cross-references resulted in an error. Now, this issue is resolved. Loading entity data including cross-references do not cause any error.

Security

Earlier, system roles with restricted privileges could not be duplicated. Now, this issue is resolved. On duplicating the system roles, new customer-specific roles are created excluding these privileges. To get these privileges for the new roles, contact Customer Support.

Release notes for Weekly Release 2021.2.3.0 - July 7, 2021

What's New

Match and Merge

We have enhanced relevance based matching to support constraints in the tokenization and the relevance score calculation. We have also added the ability to configure weights for the constraints to be included in the relevance score calculation. For more information, see Relevance-Based Matching - Detailed Explanation.

Reltio Data Science

The GBQ view for objects has been enhanced to update the insertedTime field, even if the object is from a GBQ Batch process. All records that were inserted in the past during the streaming will also be synced into the GBQ, during the GBQ Batch process and their corresponding fields of insertedTime will also be updated.

Fixes

Cleanse

Earlier, after Cleansing, leading and/or trailing spaces were appearing in the strings. Now, the String Function Cleanser processes have been organized, and this issue is resolved. The leading and/or trailing spaces do not appear in the strings.

Console

Earlier, the Data Loader failed to read the source file, when its path had a leading or trailing / character. Now, this issue is resolved. We have enhanced the Data Loader to ignore the / character in the source file path.

Core

Earlier, every time a source type for an entity or relation had a non-text value, a Null Pointer Exception message was displayed. This message did not explain the issue as expected. Now, this message has been replaced with an error message: Error #2502 - UNSUPPORTED_VALUE.

Export

  • Earlier, in case of Spark-based export, by default, S3N protocol was used. This resulted in issues with V4 signatures. Now, in case of Spark-based export, by default, S3A protocol is used, and this issue is resolved.
  • Earlier, the merge data extract operation was a bit slow. Now, this issue is resolved. The merge data extract operation works as expected.

Hub

  • Earlier, on scrolling through the Data Change Request (DCR) dialog box in Hub, the scroll bar disappeared and the DCR listed only the assignee's name in the DCR dialog box. Now, this issue is resolved. On scrolling through the DCR dialog box, the scroll bar does not disappear and lists all the user names in the dialog box.
  • Earlier, on creating a Data Change Request (DCR) for a new entity, additional entities were getting created. Now, this issue is resolved. On creating a DCR for a new entity, only entities associated with the DCR are getting mapped in the workflow.

Search

Earlier, For Relations API, in the search filtering criteria, listEquals did not work as expected. Now, the issue is resolved, and listEquals works as expected.

Release notes for Weekly Release 2021.2.2.0 - June 30, 2021

Fixes

Console

Earlier, the console had issues in the creation of an Azure SB external queue with hyphens in the namespace. Now, this issue is resolved.

Hub

  • Earlier, logging into a tenant displayed a blank screen due to the incorrect configuration of the Status attribute. Now, the functionality is enhanced and logging into the tenant does not display a blank screen and there are no issues.
  • Earlier, when the profiles were selected for Bulk Update and an action had to be selected from the drop-down list, the drop-down list was empty and did not display any actions. Now, this issue is resolved. Now, when you select profiles for Bulk Update and want to select an action from the drop-down list, the available actions are displayed in the drop-down list.

Match and Merge

Earlier, the External Match API failed sometimes when the relevance scores were null. Now, the relevance score is calculated correctly and this issue has been resolved.

Reference Data Management

Earlier, there were Remote RDM service invocation errors while exporting due to unstable network connectivity. An RDM lookup error message was displayed in the exported JSON file. Now, this issue is resolved.

Reltio Data Science

Earlier, the GBQ dataset was not in sync with the Reltio Database, due to the higher volume of entities and relation types exported. Now, we have changed the settings, and a higher volume of entities and relation types can be exported.

Reltio Platform

Earlier, operational values for MinValue or MaxValue strategies were incorrectly calculated, if the values of an attribute were not converted to the type of the attribute. Now, this issue is resolved.

Release notes for Weekly Release 2021.2.1.0 - June 23, 2021

What's New

Match and Merge

Earlier, while creating Match IQ model, a trained model was reviewed before it could be approved and published for matching. Now, the Match IQ model can be reviewed using a set of user uploaded records, and matched with the tenant using the trained model. Also, you can generate a random set of match pairs for the review process to effectively validate the accuracy and completeness of the Match IQ.

Reltio Plaform

Earlier, while submitting Data Change Requests (DCR) to update addresses on an entity with multiple address nests, only one address was updated. Now, this issue is resolved, and the cumulative-update flag is checked during cleansing to ensure it does not collapse with partial data and the addresses are successfully updated on the entity.

Fixes

Hub

Updating an entity in the hierarchy node resulted in multiple requests to the server, causing a delay in the response. Now, this issue is resolved, and the entity details are updated in the hierarchy, as expected.

Workflow

When multiple jobs were executed at the same time, data loader jobs were stuck as the disk size was exhausted. Now, this issue is resolved and the data loader is configured to use Network File System (NFS) to provide additional temporary storage. So, when multiple jobs are executed at the same time the data loader jobs run successfully.