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

General Availability (GA) of 2019.2 is June 23, 2019.
 
 
2019.2 Post Preview Updates
 

Please note that certain items detailed in the prior release notes have been moved to post GA delivery.


These features are on Hold. An update would be provided post the GA release.

  1. Core: Change to the survivorship rules to handle the pinned/ignored values.

    Support to merge the attribute values based on the transcoded value of the lookup attribute.

  2. Inbox: The ability to remove attributes from a Data Change Request (DCR), or partially reject suggestions from one task.

 
 
Documentation Portal
 

We are excited to announce the release of our new Documentation Portal. You can access the new Documentation Portal here.


We improved the user experience to allow our users to Search easily and find the most relevant information faster. In addition, the new portal enhances the look, feel and usability of our content.

 
 
Platform Security
 
 

Reltio is pleased to announce a new product offering, Reltio Shield. Commonly referred to in the industry as Bring Your Own Key (BYOK), Reltio Shield empowers customers to safeguard the data in Reltio using their own generated encryption keys. It provides the security infrastructure for encrypting data stored in Reltio’s data repositories, using the Advanced Encryption Standard (AES) with 256-bit keys. This offering helps customers comply with common compliance and data privacy standards such as PCI DSS, HIPAA/Hitech, and GDPR. These are particularly important to customers in Financial services.


Reltio Shield puts key management under control of customers. Customers can generate new keys in accordance with customer security policies and practices. New keys can be generated on demand with background re-encryption of data using the new keys or automatically performed according to a schedule. New keys are automatically distributed via secure automated processes without involvement or handling by Reltio staff, with no service downtime.


Reltio Shield provides fine grained access control, supporting policies such as full access, administrative access, and blocked. This can prevent root users on hosts from seeing the data in clear text while still allowing them to perform their functions.


Reltio is currently accepting Early Access (EA) program applications for users of Reltio Shield. Feedback from the EA will be fed back into the product before general availability, anticipated in 2019.3. Reltio Shield will be available as a new add-on subscription.

 
 
Core
 

Starting 2019.2 customers will be able to validate the tenant metadata configuration (L3) for any errors or misconfiguration. We are introducing a new API that customers can leverage to check for any errors in the configuration before posting the L3 to the tenant. In a future release this API will become an integral part of the configuration API.


 
 
Address Cleanse
 

Reltio Address standardization was improved to fix spelling errors, correct abbreviations, and fix capitalization to match the postal code standards. Address standardization is the first step in address deduplication, so this feature will improve match rates significantly.

 
 
Match and Merge
 

In 2019.2 we have made significant improvements to the external match API which will allow users to receive important information about the match entities in a more organized manner. External match API now has the ability to return the attributes of the matched Reltio entities in addition to the URI of the entity. In addition to the Reltio entity attribute users can also see the attributes of the input records in the output file which will help in comparing the input data with the matched records. We have also revised the format of the output to consolidate all matched entities for any particular input record in one single JSON object. We are also introducing additional statistics in the external match job status such as number of matched/non-matches records, number of skipped/processed/error records and other important statistics.


In this release, we are introducing a new feature to notify the subscribed list of user of any poorly performing match rules. In this version of this service, the feature looks for any match rules that is generating too many tokens or too many entities sharing the same token to detect the poorly performing match rule. This will be a configurable feature and will need to be enabled in order to take advantage of.


We are excited to announce a new unmerge API to split all the contributors of any entity in a single API call. This will eliminate the need to unmerge one contributor at a time from an entity thereby saving a lot of time and effort.

 
 
Reltio UI Navigation
 

Users can now navigate seamlessly between Reltio applications like Console, MDM UI and Reference Data Management (RDM) for same tenants. This navigation is based on user’s tenant access.

 
 
Reltio DTSS
 

Reltio DTSS was improved with the addition of monitoring capabilities. Monitoring capability gives the ability to understand/monitor the working status of DTSS. You can monitor load on current DTSS service, lists all the current DTSS sync tasks/jobs along with the state (In progress, Completed with errors, completed successfully) and see metrics about each task.

 
 
Reltio Connectors
 

Reltio Connector now supports Mulesoft SDK v4. All the functionality supported in the earlier version will be available in this version. For more details on Reltio Mulesoft Connector see here.

 
 
Reltio Console
 
Data Loader
 

Data Loader is enhanced with exciting features in 2019.2. Data Loader will support loading relationships along with loading of the entities. Data Loader can now combine entities distributed in multiple rows and load them all together. The Data Loader is enriched, the mapping screen now displays the attribute property if its required/hidden.

 
 
Tenant management
 

The Queues dashboard in Tenant Management app has been updated to display the size and processing speed of the queues (CRUD, Match) along with the count of failed messages and dead letter queue metric. This helps in identification of any issues in queue in a self service manner. External queues can also be monitored through the Tenant Management app, using the new dashboard which displays the number of messages sent to the external queue.

 
 
Data Modeler
 

Data Modeler offers some exciting new features in 2019.2. You can now create new Entity Types and new Relationship Types through the Data Modeler application. The intuitive UI allows you to easily enrich the new Entity Types and the new Relationship Types by adding attributes.

 
 
Export UI
 

Export app now supports the export of analytics attributes, the mapping screen is also enhanced to display the attribute property - hidden, required, analytics with filter capabilities as well. Users can now choose the relation to be exported while selecting the entities from MDM UI and landing in the export app. Users will get the list of relations that are connected to the entities that are selected in the MDM UI.

 
 
Data Quality
 

The dashboards in Data Quality (DQ) app are enhanced to support the nested attributes used in the DQ configuration. The reindexing of the entity which is done after the scores calculation to make the scores searchable is now configurable to be run manually or automatic after the scores calculation. By default the reindex option is manual.

 
 
 
Inbox
 

In the Inbox application, users will now be able to view the entity type on the summary of each task, making it easier to visually categorize tasks.

 
 
Machine Learning based External Match
 

2019.2 features External Match App that is powered using Machine Learning (ML). Users will be able to match a file (uploaded via GCS) to an existing tenant. There is no need to setup any match rules, once the file is uploaded and you indicate which attributes you want to match against, you will be taken through a series of questions (active learning) that will help optimize the ML algorithm to make more accurate predictions.


This feature is only available in EA mode to limited customers.

 
 
 
Reference Data Management (RDM)
 
2019.2 features RDM Export that will enable exporting RDM lookups in CSV format. RDM will also provide an ability to search for all MDM records that have RDM transcoding errors, this is available both through API and in advanced search in MDM UI.
 
 
Deprecation Notice
 

In the 2019.1 release we announced the deprecation of Export version 1.0 with support ending at the end of February 2020. Please work with your Reltio Customer Success Manager to migrate to Export version 2.0. This new version of Export has generally improved performance. It intelligently selects the appropriate export strategy and then optimizes the export process based on the data set.

 
 
Important Changes
 
  • The default value for the useOnlyOvValuesInReferencedEntities property of the entity type will be changed to true in 2019.3. With this change, only Operational Values (OV) 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.3. This will prevent cascading events to the entities when the OV of the referenced attributes are not changed.

 
 
Items moved to Post GA delivery
 

Please note that certain items detailed in the prior release notes have been moved to post GA delivery.


These features are on Hold. An update would be provided post the GA release.

  1. Core: We have made an important change to the survivorship rules to handle the pinned/ignored values. Customers will now be able to define the preference between pinned/ignored values when entities being merged have 2 different flags for the same attribute value. For example, Name “John” is ignored in one profile and the same value is pinned in another profile and if these profiles are being merged then customers can pre-configure the survivorship rules to determine if pinned or ignored value should survive in the consolidated profile.


    In this release we have enhanced the feature that manages the merging of nested attribute values into a single value when they are determined to be the same value based on the pre-configured rules. With this release we have added the support to merge the attribute values based on the transcoded value of the lookup attribute.


  2. Inbox: Users now have the ability to remove attributes from a Data Change Request (DCR), or partially reject suggestions from one task.