2019.1
release notes
 
 
Release information
 
We are pleased to announce the Preview Environment of Reltio Cloud version 2019.1.

General Availability (GA) of 2019.1 is February 17, 2019.

Release Video can be viewed here.
 
 
Core Platform
 
We have continued to strengthen the Reltio Cloud platform. One area of improvement is the stability and performance of Reltio’s queue management service for internal event processing and streaming to customer applications. Real time monitoring, alerting, and visualization have also been improved for quicker detection and diagnosis of issues. In addition, safeguards have been added to improve resiliency and performance of the queue management service.

We have strengthened the platform’s ability to detect and resolve data anomalies helping to ensure that results seen in the search screen are current and synchronized with the database.

We have improved the performance of the export service. It is more consistent now for jobs of the same data set size. Monitoring has also been improved to provide more detailed visibility of job health at each stage of the export lifecycle.
 
 
Platform Security
 
 
For 2019.1, investments have been made in a number of areas, some of which have already been released in hotfixes. One of these is an improvement in authentication performance. We have also created a new system role, ROLE_ADMIN_USER. This role grants an authorized user to manage user accounts without being a Customer Administrator. This new role only has access to perform user account management and not to any other parts of the Reltio platform. This helps address segregation of duty concerns. Every change made to a user account is recorded in the security audit log.
 
 
Attribute Value Survivorship Processing
 

In 2019.1 we have optimized the survivorship rule engine for better performance. Additionally, enhancements were made to the behavior of the Recency rule and the Oldest Value rule. We also have introduced an ability within the Source System rule to restrict the Operational Value (OV) for an attribute to be sourced from only a subset of the full set of sources defined for the tenant.

 
 
Cleanse Functions
 

In this release, we have made significant changes to the monitoring of the address cleansing service. Starting 2019.1, the address cleansing module will the capture the failed address cleanse requests and will attempt to re-cleanse before returning the failed response.This will enable the Reltio to detect and remediate address cleansing issues automatically.


Prior to 2019.1 Address Cleansing supported nested attributes up to 3 levels deep. In this release, the number of supported levels has been extended to 5. In addition to this, we are introducing a new cleanse functions listed below:

  • String Function Cleanser – This cleanser provides string function processes that support padding, removal of unwanted characters and case coercion.

  • Full Name Builder – This cleanser synthesizes a full name through concatenation of the first name, middle and last name elements.
 
 
Match and Merge
 

We are excited to introduce the match group rule "scope" feature. It allows you to control the scope of execution of a match group rule. Four possible scope values are:

  • None – Match groups marked with scope, "none" will not participate in the matching process. This will enable customers to temporarily disable any match group rules that customers do not wish to consider for matching without having to physically remove the entire match group configuration from the Level 3 (L3) configuration

  • Internal – Match groups marked with scope, "internal" will be used to match records that reside within the Reltio tenant

  • External – match groups marked with scope, "external" will be used to match records from an external source to records that reside within the Reltio tenant

  • All – match groups marked with scope, "all" will be used to match records that reside within the Reltio tenant, as well as those from an external source to records that reside within the Reltio tenant.

Match groups without a scope declaration will behave as if marked "all". This will ensure backward compatibility for existing configurations.


In this release, we are introducing a new version of the "rebuildMatchTable" API for the re-tokenization and matching of the records. This enhanced version will have the ability to run more granular matching related tasks such as generateMatchStructure, truncateTable, performMatch, mergeAutoMerges, etc. This will allow you to run a specific task of interest instead of running the entire matching process. This can improve processing time significantly.


Matching Strategy allows customers to choose the way match engine behaves when any record is created/updated/deleted in the tenant as per their requirement for matching. In 2019.1 we have optimized the supported matching strategies for better performance and stability. Additionally, the enhanced set of matching strategies at the tenant level are described below. Contact Reltio Support to set your tenant to the desired matching strategy.


  • NONE – Matching is disabled. Match & DTSS related tasks will not occur on any of the configured entity types.

  • INCREMENTAL – Any update to an entity causes the entity to be rematched on the fly. Merge-on-the fly is enabled by default at the tenant level but can be disabled for any particular entity type using metadata configuration.

  • INCREMENTAL_V2 – Same behavior as INCREMENTAL except that Merge-on-the fly is disabled by default at the tenant level but can be enabled for any particular entity type using metadata configuration.

  • ON_REQUEST – Matching only occurs when invoked as a batch job.

 
 
Export
 

Version 2.0 of the export API is now available to all customers. This version of export will perform automatic optimization for all export use-cases including:


  • Full Export of all the objects in an tenant
  • Delta Export of objects that changed since last extract also called as time based filter
  • Filtered Export based on conditional values

Version 2.0 uses highly distributed Spark-based technology for faster extracts. Additionally, whereas the previous version would produce a single output file regardless of size, version 2.0 will automatically break the output into a collection of smaller files.


In this release, we have also enhanced our export API for better monitoring around job execution delays and failures and improved overall job queuing time.

 
 
Reltio MDM User Interface (UI)
 
In this release Reltio Cloud MDM User Interface (UI) users will experience a 2 times faster performance around the initial rendering of a record, navigation between records, and switching between Read and Edit mode within a record. Users will also experience performance improvements in the Potential Match review screen.
 
 
Reltio Console
 

External Match application is available as an EA program. The External Match application can be used to match external data with data that resides within a tenant, while providing match results and status of the external match job.

DQ IQ application is available as an EA program. The DQ IQ application has been enhanced to support both nested and simple attributes for calculating the DQ scores.

The Match Analyzer is available through the Data Modeler application. It analyzes the performance of the configured match rules and can provide suggestions for improvement.


Tenant Management – For customers whose tenants are hosted on Reltio’s AWS platform, we have added the ability for a Customer Admin to clear the Match Processing Queue in a self-service manner, rather than having to submit a Support Ticket.

 
 
Future Changes

  • The default value for the useOnlyOvValuesInReferencedEntities property of the entity type will be changed to true in 2019.2. With this change, only Operational Values (OV) values of the attributes of the referenced entity will be returned in the reference attribute

  • The default value for the ignoreNonOVChangesWhenUpdateThroughReferencedEntity property of the entity type will be changed to true in 2019.2. This will prevent cascading events to the entities when the Operational Values (OV) values of the referenced attributes are not changed.
 
 
Deprecations

  • Starting 2019.2, preview tenant will be a clone of the customer’s Dev tenant only.

  • Export version 1.0 will be deprecated using our standard deprecation policy. This means its current functionality will remain active and supported for a period of 1 year from the release of 2019.1. It will become inactive on Feb 28, 2020.