Reltio Connected Data Platform: 2021.1 Weekly Releases

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

Release notes for Weekly Release 2021.1.16.0 - June 9, 2021

What's New

Security

Now, in the Reltio User Management system, SSO users can be deactivated. Deactivation of SSO users revokes all active user sessions. After deactivation, SSO users cannot access any of the Reltio services. For more information, see Deactivating Single Sign On Users.

Fixes

Hub

In the new Potential Matches Perspective page, adding a relationship is not possible without specifying the Start and End Dates. The old Potential Matches Perspective page enabled adding a relationship without specifying the Start and End Dates. Now, in the new Potential Matches Perspective page, we are providing a similar experience, and a relationship can be added without specifying the Start and End Dates.

Security

Reltio Authentication logs were not capturing all the login scenarios of Single Sign-On (SSO) users. Now, the log records details of all SSO users who log in to the system.

Release notes for Weekly Release 2021.1.15.0 - June 2, 2021

What's New

Connectors

Now, we enhance the customer experience, by enabling full and incremental ingestion of merges and matches data into Snowflake.

Fixes

Match and Merge

  • Earlier, all the endpoints associated with external matching limitations were removed. Now, the External Match Limit API displays the default value of the External Match Limit, if the default value is specified in the configuration of the tenant or if the default value for the environment is specified in the property file. Limits are managed by Quotas and Limits of the tenant.
  • Earlier with Proximity Match Rule, the merges did not occur as per expectation. When we had several nested attributes in one entity, multi operand used to build all possible combinations with simple attributes inside nested structure and with a simple attribute from another nested attribute. Now, the multi operand builds a combination only with attributes from one separate nested attribute.
  • Now, the issue of records not automatically merging is resolved.

Search

Earlier, Interaction Search API was not working as expected when interactions were deleted. Now, this issue has been resolved.

Workflow

  • Earlier, the External Match Report included only the mapped attributes, and the unmapped Additional attributes were excluded. Now, this issue is fixed, and the Additional attributes are included in the External Match Report.
  • Earlier, some of the newly created Data Change Requests were not assigned to Data Stewards. Hence, they were not able to approve or reject them. Now, this issue is fixed, and all Data Change Requests are assigned to Data Stewards.

Release notes for Fix Release 2021.1.14.2 - May 28, 2021

Fixes

Reference Data Management

Earlier, in the RDM tenant, a new Lookup type could not be created. Now, this issue is resolved. Also, we have taken care that it will not occur in future too.

Release notes for Fix Release 2021.1.14.1 - May 26, 2021

Fixes

Reltio Platform

Earlier, merging of the entities with identical crosswalks (specifically, surrogate crosswalks) did not happen. After some time, these entities automatically merged in the background. The outcome of these unnecessary merges leads to significant degradation of performance. Now, this issue has been resolved.

Release notes for Weekly Release 2021.1.14.0 - May 26, 2021

What's New

Export

Now, in Export Version 2, using Filename Template, you can name the output files. For more information, see Naming Output Files.

Fixes

Export

  • The production tenant was slow due to issues with the internal export pipeline. The code has been optimized to improve the performance.
  • Earlier, the outcome of Export displayed duplicate records in case of multiple nested attributes in the tenant configuration. Now, this issue is fixed, and the outcome of Export does not display duplicate records.

Hub

  • For a potential match review request of selected profiles, a blank screen was displayed. Now, this issue is fixed, and the potential match review is successful.
  • In some cases, the saved searches list did not display the correct count of records. But, when the saved search was selected, the correct number of records was displayed. Now, this issue is fixed, and the saved searches list displays the correct count of records.

Reltio Data Science

The GBQ loader incorrectly parsed entity types/relation types/interaction types when they had _ character in their names. we have updated the GBQ Batch processes to fix this issue.

Reltio Platform

  • Earlier, in an External Match Job, only a limited number of records could be run each day. Now, these limitations are removed. Based on their entitlement, customers can run any number of records in an External Match Job.
  • Earlier, the Force Stop API changed only the status of the task, and not stop the task. Now, the Force Stop API allows to force stop the task.
  • Earlier, when there were no change requests associated with relation, Null Pointer Exception (NPE) was displayed. Now, Platform API handles these issues.

Workflow

  • Earlier, using Workflow Modeler, customers were unable to deploy process definitions on tenants. Now, this issue is fixed to enable deployment.
  • Earlier, while executing workflow tasks, the workflow requests to the platform timed out due to delayed responses. Now, this issue is fixed, and the timeout is increased for these workflow requests.

Release notes for Weekly Release 2021.1.13.0 - May 19, 2021

What's New

Export

We have reduced the number of empty output files for Export V2.

Hub

  • Earlier, the text values were not clearly visible in the Filter pop-up menu. Also, the filter was applied only after clicking outside the Filter pop-up menu. Now, the behavior of the Filter pop-up menu is enhanced by increasing its minimum width. Thus, the text values are clearly visible and the filter is applied when the input is provided.
  • Bulk Update, the feature available in the New Search experience, enables you to manage tags of profiles. For more information, see Overview of Bulk Updates and Bulk Update - Attributes.

Fixes

Console

  • Earlier, in User Management, the Next Page icon was not displayed, due to incorrect styles in the Cascading Style Sheet (CSS). Now, the Cascading Style Sheet (CSS) is fixed, and the Next Page icon is displayed.
  • The hidden attributes were not included in the list of exported attributes when the export was redirected from the Hub to the Console. Now, with this fix, by default, all the basic (URI, type, createdTime, updatedTime, analyticsAttributes, label, secondaryLabel) and non-hidden attributes are exported.

Connectors

Account and contact entities were missing NPI DT records in the Potential matches view because entity type metadata was not being converted for search request with cross entity type subscription mapping. We have updated our code to fix this issue.

Reltio Platform

Earlier, matchOvOnly was not recursively applied to the sub-nested attributes. Now, if the matchOvOnly flag is true, it is assumed that all nested and corresponding sub-nested attributes are non-OV values.

Reporting and Analytics

Access to Reporting and Analytics applications on the Reltio console was disrupted. We have updated the particular tenant configuration endpoint to fix this issue.

Release notes for Weekly Release 2021.1.12.0 - May 12, 2021

Fixes

Reltio Data Science

  • Due to an unexpected logic for merge, entities were absent in the entity_HCP table. We have fixed the BigQuery links to fix this issue.
  • Export Version 2 was using the tenant transcoder implementation without considering the context handler and this caused NullPointerException errors in JSON body of an entity exported with V2. We have updated our code to fix this issue.

Reltio Platform

  • Earlier, deleted event API returned invalid URIs. The ENTITY_REMOVED_GDPR events for the event scanner were skipped. Now, event API returns valid entity IDs for event type='DELETED'.
  • After the removal of duplicates, redundancy in attributes was observed. Now, modified entities and relations are saved before removing duplicates in attributes.

Search

Attribute URIs in the crosswalk section were unexpectedly empty when the ovOnly filter was used. We have updated the code to recalculate OV when the filter is applied on the crosswalk to fix this issue.

Security

The Auth Service is enhanced to respond to requests from the LCA service, without any alerts being triggered from LCA.

Workflow

Sometimes, when the load on the system is high, the insertAll API fails to insert data into GBQ and http error 502 error appears. We have added a retry logic to ensure Workflow APIs are inserted correctly into GBQ.

Release notes for Weekly Release 2021.1.11.0 - May 5, 2021

What's New

Hub

  • The Identity 360 customer profile is now enabled to view interactions and their related attributes.
  • The Bulk Update feature has been enhanced to delete multiple profiles at the same time. For more information, see Overview of Bulk Updates.

Match and Merge

The Match Rule Analyzer inspects the match rules and provides suggestions to improve the performance of these rules. A match analyzer can detect and inspect the malicious behavior of match rules. For example, overcollisioned match tokens lead to large amounts of matches, which cause many comparisons that significantly load the platform. Popular token phrases and corresponding entities are detected and notifications are triggered or other actions, such as match rule disablement are invoked. The proactive notifications include information about entity types and match rules.

Reference Data Management (RDM)

RDM API has only an endpoint to remove unmapped values in the RDM tenant by URIs. It is difficult to use it for removing a large number of unmapped values. Now, a new task deleteUnmapped is available to remove all unmapped values in the RDM tenant.

Fixes

Hub

When the user deleted a reference attribute using the Bulk Delete operation, the reference attribute and the corresponding relation were deleted. But the mail sent to the user indicated a failed operation. This is now updated to reflect the correct success message.

Reltio Data Science

We have updated the Update Converter to ensure that information about inactive and deleted objects is present in S3 and the records are in sync with the Primary Data Storage.

Reltio Platform

  • Earlier, the delta was not written to the history of a particular entity. The delta for these attributes for the entity added in the description are restored and all other entities of the tenant are checked now.
  • Earlier, the POST /entites?options=partialOverride,updateAttributeUpdateDates did not override singleAttributeUpdateDate unless there were changes in the attribute values. However, with this fix, the API will use updateDate provided in the request to override the existing singleAttributeUpdateDate even if there are no changes in the attribute values.

Reporting

We have updated the Reporting and Analytics UI to now display projects correctly depending on the environment flag.

Release notes for Weekly Release 2021.1.10.0 - April 28, 2021

What's New

Export

You can now export Entities' URIs/labels from the activities data field to the output CSV file in the existing URIs and Labels columns without creating new columns.

Reference Data Management (RDM)

While creating lookups, you can create unmapped blocks when the information about canonical code is not available. Unmapped blocks are created in an unmapped drawer. When lookups without canonical code are uploaded to the RDM tenant, the automatically created unmapped data is displayed by the unmapped drawer.

Reltio Platform

A new parameter for survivorship mapping sortAs is implemented. This parameter is supported only for MinValue/MaxValue strategies. In the business configuration, some customers store values of integer, double, boolean, and other types in fields of the type String. The default implementation of minimum/maximum Operational Values (OV) strategies in such cases provides only a comparison of these values and sorts them in lexicographical order. To be able to compare these values for OV calculation with the cast to target types, the existing behavior of the Min/Max OV calculation strategy was extended with the additional parameter sortAs.

Fixes

Cleanse

Sometimes, addresses were not getting verified automatically even when pre+c+g cleanser process was selected. We have updated our code to fix this issue.

Connectors

There were validation errors when a relationship was defined between entity types in the L2 configuration, and this relationship was used in the Salesforce connector mapping. The incorrect validation errors have been fixed now.

Security

Earlier, customer administrators were not able to duplicate system roles. Now, the customer administrators can duplicate any system role in order to create appropriate customer-specific roles.

Workflow

We have updated our code and are now getting the correct results when the task filter is applied in the Reltio Inbox.

Release notes for Weekly Release 2021.1.9.0 - April 22, 2021

What's New

Search

Now, validation warnings appear for incorrect configuration while specifying entity or relation type attributes with names that only differ in the register and are on the same level.

Fixes

Console

If a crosswalk was already used to load data into a different entity type, then the job failed with an ERROR state. With this fix, instead of an error, the data load job will end in the COMPLETED WITH ERROR state and generate error files.

Export

There was a mismatch in the number of activity items per activity that the Reltio platform and the Export service could handle. As a result only 100 objects were exported for activities with more than 100 items. We have realigned the limits to fix this issue.

Match and Merge

  • Earlier, the endDated attributes were included in the Match documents and participated in the matching process. Now, when the Match document is built, the endDated attributes are checked, and not included. The endDated attributes do not lead to merges anymore.
  • Earlier, the ProximateGeoToken failed to build match tokens for negative longitudes. Now, this issue is resolved. The newly created tenants use the fixed version of ProximateGeoToken. For the tenants that already use ProximateGeoToken, the old match tokens class will be retained. To migrate to the fixed version, contact Reltio Support.

Reltio Platform

When partial override requests were processed, null values were not skipped. If the value for an entity was null, it was parsed to null entity objects. Now, when partial override requests are processed, these objects are skipped.

Security

When new customer-specific roles were created and assigned to client IDs, the system was unable to evaluate permissions of these client IDs for the newly assigned roles. For example, a new customer-specific role was created by copying the ROLE_DATALOADER system role and assigned to a client ID. When the data load operation was run, it resulted in failure because the system could not evaluate the new role. Now, this issue is resolved and the system is able to successfully evaluate permissions for new customer-specific roles when they are assigned to client IDs.

Release notes for Fix Release 2021.1.8.1 - April 15, 2021

Fixes

Reltio Platform

Get Entity API response did not contain the entity history. An empty response was observed. This happened because some of the historical events were processed incorrectly. As part of the fix, all failed events were reprocessed from the dead letter queues (DLQ).

Release notes for Weekly Release 2021.1.8.0 - April 14, 2021

What's New

Match and Merge

  • Synonym dictionary is supported during the Match IQ training process now. It is considered during the intra-tenant matching and external matching. This support is also added for RDM based match cleansers. Now the match pairs that have synonym names are also considered during the training process.
  • The _notMatch endpoint now supports filtering and sorting data on the Potential Matches Perspective (EA) page.

Fixes

Search

  • The GET activities API was not returning the same records as activity/_scan API because of a mismatch in the number of activity items per activity that the Reltio platform and the REST API could handle. We have realigned the limits.
  • The Search API results returned duplicate records and missed some valid records because of an error in the pagination functionality. We have updated the internal sorting to fix this issue.

Export

  • Exporting entities by using the CSV exploded format failed for entities with analytics attributes. We have updated the Export Service to handle entities with analytics attributes correctly.
  • Some activity log events having attributes based on entities' URIs were exported as a separate column in the export CSV file and this caused task to freeze and be unresponsive. We have limited the number of columns to 100 to prevent file overload.

Workflow

Uploading data from an excel file by using the Console Data Loader utility failed with an Error :Parser failed to read file due to null error. We have updated the streaming library to the latest version to fix this issue.

Hub

  • While adding a new relation, Hub allowed you to save and apply the changes even without highlighting any missing mandatory information. The fix ensures that the mandatory fields are highlighted and the Apply and Save buttons are disabled until the missing information is entered.
  • The Potential Match facet in the Profile was not displaying potential match names for the selected profile. This was due to the absence of negative rules for the matches containers. Now, negative rules are supported for both simple and ML matches and the potential match names are displayed in the facet.

Reltio Platform

  • Enhanced error messages are now displayed when the tenant limits for the number of crosswalks are exceeded. The new error message now has the name of the parameter, the current limit size, and the exceeded value.
  • Stack overflow error occurred in some exceptional configurations. This caused data load for few records to fail and a JSON Mapping exception was thrown. Reference attributes for the relations of the same type were not supported. Now, this has been resolved.
  • Earlier two relationship attributes with the same name were created unexpectedly while applying L3 on the vertical. Now, this has been resolved and the attribute definition in L3 replaces the attribute with the same name in vertical.
  • The optimization logic combines events for similar objects generated in the same operation. Earlier, two events were combined in a way that the final event was marked to be processed by a limited number of processors excluding the streaming processor. Therefore, the event did not get passed to the external queue. Now, this logic has been rectified.

Release notes for Fix Release 2021.1.7.1 - April 12, 2021

Fixes

Reltio Platform

There were some unexpected errors while using the _changes With Total and _changes API requests for tenants with enabled history cache only. The entities which had unmerge or potential match events in history were affected. This issue is fixed by using an updated cache history format.

Release notes for Weekly Release 2021.1.7.0 - April 7, 2021

Fixes

Match and Merge

Transitive matches now support filtering and sorting data on the Potential Matches Perspective (EA) page.

Reltio Platform

  • Reltio recommends that you do not use the _tree request in scripts because this request always reads several graph levels and consumes several platform resources. Also, the response could take a long time (up to several minutes) for large hierarchies.
  • Earlier, slice IDs were not getting generated and DATA_ON_BEHALF_OF_MULTIPLE_CONTRIBUTORS_RELATIONS error was observed before the cumulative update. Now the slice IDs are generated properly.

Search

Search was not working properly when the relationship/entities attribute was used. We have updated our search engine to handle attributes with id names correctly.

Workflow

Sometimes, Task API requests were not getting executed. We have updated the APIs to fix the issue and enhanced the Get Users method to ensure it retrieves the details faster.

Release notes for Weekly Release 2021.1.6.0 - March 31, 2021

What's New

Reltio Platform

Now, validation warnings appear for incorrect configuration while organizing Graph Type reference to non-existing relationship types.

Fixes

Hub

  • When the user searched for a profile, invalid characters were displayed for certain attributes. This was resolved after the page was refreshed. This happened due to an incorrect escaping method. This is now fixed and the profile displays the correct attribute values.
  • Multiple requests sent from the same host at the same time led to slower performance for check token operation. This in turn led to backend service performance issues. This is now fixed with the necessary configuration changes to enable multiple requests from the same host.
  • On successful completion of bulk update, the mail received by the user indicated that the operation had failed. This is now fixed and the mail received by the user indicates the correct status after a successful bulk update.

Reltio Platform

  • There were too_many_connections errors due to instability in the environment. Therefore, the counter of free slots for simultaneous requests broke and degraded to zero. Now, this counter is reset to avoid cumulative, long-run degradation.
  • When multiple records were loaded in the same request through Data Loader, the same crosswalk IDs were generated instead of multiple IDs. Due to this, some records merged by the crosswalk. Now, the sequence generator sends each record separately and this issue is resolved.
  • When a Suspect match rule was changed to Automatic and the rebuild match table task was run, only the ENTITIES_MERGED event was generated for the auto-merged profiles. Now, the Reltio Platform generates all the required events such as, ENTITIES_MERGED, ENTITY_CHANGED, and LOST_MERGE.

Workflow

  • Some records were failing while loading data and the error messages were not clear. We have updated Data loader error messages to provide clear explanations when jobs fail and optimized the data loader jobs to eliminate failure scenarios due to low throughput.
  • When the pod that was executing the job was shut down while loading a large number of records, the job status incorrectly displayed UPLOAD_TO_S3_FINISHED. Therefore, Dataload jobs failed to resume the incomplete job. This issue occurred due to the missing Data Flow (DF) error file. We have added checks to ensure that the DF error file exists, before starting to load the records to GBQ.

Release notes for Weekly Release 2021.1.5.0 - March 24, 2021

What's New

Workflow

We have enhanced Data Loader to continue loading and processing data from multiple files even if parsing one of the files fails because of the wrong format. The logs are also updated to show the files that were not loaded and include the reasons for failures.

Fixes

Reltio Platform

  • During the partial override of entities, though some of the auto-generated attributes did not participate, their corresponding pin or ignore flags displayed unexpected behavior. We now ensure that the unexpected behavior of auto-generated attributes is controlled.
  • Earlier, the platform displayed unnecessary attribute URIs in the crosswalk section when the ovOnly filtering option was used. Attributes are now displayed appropriately in the crosswalk section.

Security

When a new client is created and token requested through the client_credentials grant type, ROLE_API is assigned to the client by default. Administrators can now change the default role entitlements that are mapped to the client IDs. By default, this feature is disabled.

Hub

  • The Potential Match Perspective (EA) page has been modified to display the potential matches from Data Tenant Subscription Service (DTSS) for existing data tenants. The Potential Match Perspective page enabled you to work with these details and we are now providing the same experience through the Potential Match Perspective (EA) as well.
  • Attribute values were not sorted as per the survivorship rules before paginating the values in a Single Attribute View facet. Now, Hub displays the attribute values sorted correctly even when the results are displayed across pages.

Workflow

  • The console dataload jobs failed as the load error messages were not written to the external file. We have now updated the Load Prepare File (LPF) task to check for and write batch errors to the external file, if few records in a batch fail.
  • We have fixed dependency conflicts in AWS libraries to avoid errors related to missing libraries, while approving or rejecting Data Change Requests.

Reltio Data Science

  • Spark export was missing some objects with large number of attributes. We have updated our code to consider objects with more that 2000 attributes and export them correctly.

Reference Data Management (RDM)

Transcoding of attribute values uses only those crosswalks that have not end-dated. When the transcodeByEndDatedCrosswalks parameter is set to true, the end-dated crosswalks are considered for transcoding attribute values.

Release notes for Weekly Release 2021.1.4.0 - March 17, 2021

Fixes

Match and Merge

During Match Calculation for nested attributes, the weight of the nested attribute was set to 1 while calculating the relevance score, regardless of the sub-attribute values. Now, the Relevance Score is calculated using the configured value of the parent nested attribute. If the weight of the parent nested attribute is missing, then the maximum of the weight from the sub-attributes is used instead of the fixed value of 1.

Reltio Platform

Earlier merges did not happen in the tenant on time and certain entities were not auto-merged. Now, an additional logic is added and the match events are generated if CRUD events are retried.

Export

Export jobs were waiting in the Schedule state for a long duration as the scheduler prioritized distributed tasks over single tasks. We have now updated the export task scheduler logic to ensure that distributed and single tasks have the same priority.

Workflow

The apply Data Change Request (DCR) request from Workflow to the platform was timed out as the applied DCR was not validated in time, due to issues with background validation. The background validation service is now fixed.

Reltio Data Science

When Data was loaded into Reltio, time to sync it to Reltio Analytics BigQuery warehouse was high. Events are now processed correctly and the sync times are lower.

Reference Data Management (RDM)

Earlier, retrieve lookups using direct API calls to RDM were not able to filter disabled lookups. Now a new option is added to the MDM tenant physical configuration to hide the disabled lookup. Contact Reltio support if you want to hide the disabled lookup.

Release notes for Weekly Release 2021.1.3.0 - March 10, 2021

Fixes

Core

  • The comparison of attribute values with lookups worked incorrectly when the attribute value in the database and the value received through an update relation request were compared. Now, the platform compares such attributes appropriately.
  • Earlier, when the POST /api/{{tenantID}}/relations API request was submitted with an empty body, a Null Pointer Exception (NPE) was thrown. Now, an appropriate error message is displayed instead of the NPE.
  • Now, when an empty filter is set for the Update Attributes task, an appropriate error message is displayed instead of the Null Pointer Exception (NPE).
  • Earlier, when the POST /api/{{tenantID}}/entities/{id}/_update API request was submitted with an empty body, a Null Pointer Exception (NPE) was thrown. Now, an appropriate error message is displayed instead of the NPE.

Reltio Platform

Sometimes, the platform skipped generating events for relations due to an old optimization that did not work correctly. This led to inconsistencies in RIQ and search options when the indexing of relations was enabled. Now, this optimization has been disabled to avoid inconsistencies.

Search

The activity reindex task was generating a large number of events which resulted in increased CRUD (Create, Read, Update and Delete) queue size. We have optimized how events with expired time to live (TTL) are handled to resolve this issue.

Workflow

  • Potential Match Review process when triggered from Search in HUB, failed with an error due to multiple updates in the database leading to deadlocks on column indexes. The issue is now fixed by disabling the filling of the cache, if the corresponding feature is disabled. The permanent solution to this issue is under progress and filling of the cache will be enabled along with the permanent fix.
  • The load prepared file (LPF) tasks were ending up in infinite loops when errors were reported by cleanse and other APIs. The updated code now checks for errors reported by other APIs and reports the Periodic Task (PT) as failed.
  • The Dataloader Job showed incorrect Completed status during a partial file load. The issue is now fixed by modifying the error report for batch errors, whenever the dataload for a batch fails with a common exception.
  • Data Loader was not indicating any errors or failed records whenever the processes were ending abruptly without processing the entire input file. The Dataloader API is now updated to re-throw the error to the caller and set the task status to failed.

Release notes for Weekly Release 2021.1.2.0 - March 3, 2021

Fixes

Export

Spark export was failing with the Couldn't upload object to s3 error, when file upload was interrupted due to connectivity issues. We have fixed our retry functionality for uploading operations.

Hub

  • When the user clicked the search field in the Advanced search page, the drop-down dialog box with the select options moved around the page. This is now fixed and the dialog box is displayed in the correct position when the you click the lookup button.
  • In the new search experience, when the user tried to clear, find and replace, or find and remove attribute values for a profile using the Bulk Edit operation, the values were not getting updated. This is now fixed and all values are updated when the user tries to clear, replace or remove attribute values using the Bulk Edit operation.

Match and Merge

Users used the cleanser not only as a 'first name' cleanser, but also as a general-purpose cleanser. The nameDictionary parameter was not suitable for all Match Cleanse cases. Hence we have now added support for the dictionary parameter for the Match Cleanse configuration. The support for nameDictionary parameter remains available for backward compatibility.

Reltio Platform

Previously while running SAP Reltio load, the queue used to get stuck because of the relations which had the same crosswalk but different start or end objects. The platform merged such relations during events processing, but it led to an exception. The platform performed the action repeatedly until the event expired. Now the platform identifies such events and does not send them back to the queue. This ensures that the queues do not get stuck.

Search

The search engine was building incorrect search queries when a missing condition was added to inSameAttributeValue. The missing filter is now handled properly and the query returns appropriate results.

Release Notes for Weekly Release 2021.1.1.0 - February 24, 2021

What's New

Workflow

Inbox is now enhanced with the Bulk actions option which allows you to multi-select a group of tasks from Inbox and approve or reject them in one action. For more information, see Overview of Workflow Tasks.

Fixes

Export

While exporting data from S3, the OV strategies worked incorrectly for some attributes. We have now added the missing information (singleAttributeUpdateDates) to our storage and the Operational Value (OV) is defined in the same way for the entity (that is, during the export, through the API), regardless of the method.

Reltio Analytics

Events were delivered later than expected because autoscaling was disabled in the Google Dataflow job which served the whole environment. We have now enabled autoscaling for all Dataflow jobs.

Reltio Data Science

Data Quality statistics showed incorrect values for completeness percentage. We have added unit tests to cover scenarios where attributes have multiple values and fixed the completeness percentage and DQ values.

Reltio Platform

In some cases, when the generateIfNotEmpty parameter was set to false and the generatedValueUniqueForCrosswalk parameter was set to true for autogenerated attributes, the surrogate crosswalk was incorrectly compared to other instances of surrogate crosswalk of a similar type. Therefore, the updated value of an attribute was not considered and updated correctly. Now, the updated attribute values received through the request are updated correctly, as expected.