release notes
Release information
We are pleased to announce the Preview Environment of 2018.3 release.

We will be releasing 2018.3 to the general public on October 28th. Release Notes can also be accessed at our Documentation Portal.
Platform Reliability, Availability, Scalability, and Performance
Reltio is continuing its investment in ensuring its platform is highly reliable, available, scalable, and performant to support our customers' needs now and as they grow and expand. Multiple projects were undertaken to support this critical initiative.
Database Resiliency

The goal of this feature is to improve database resiliency when subject to extreme traffic loads. This will increase reliability and consistency of services for Reltio customers. The service will take pre-emptive actions to localise the impact of traffic spikes.

Retry with Exponential Back-off

The goal of this feature is to help protect the backend infrastructure from resource depletion during heavy data loads. Reltio APIs will retry an operation, with an exponentially increasing wait time, until a maximum retry count is reached (e.g 4 retries). The maximum retry count is configurable.

Data Inconsistency Remediation

We have hardened monitoring and processing capabilities to proactively detect and resolve cases in which a user may observe information in the UI/search results that is out of sync with the database.

Platform Security
Ensuring the right access is granted to users and protecting customer data are top priorities for Reltio. We have made the following enhancements to meet these goals.
User Management

In the 2018.3 release we introduced a new User Management module (accessible within the Reltio Console) that provides customers with a clean and easy to use web interface to manage user access privileges (including role definition management). This new module replaces the existing “Roles and User Management” module within the Reltio Desktop UI.

IP Whitelisting

The goal of this feature is to offer customers another layer of protection of its data in which Reltio services can only be accessed from the customer’s corporate network (defined via a whitelist of IP addresses). Customers who are interested in this feature can reach out to their Reltio Customer Success representative.

TLS 1.1 Retirement
See the Retirement Notice section below
Endpoint Security API Retirement
See the Retirement Notice section below
Update User Tenant and User Role API Retirement
See the Retirement Notice section below.
MDM Core
Immutable Reference Attribute

This feature can be used to prevent certain source system(s) from updating the information of the existing referenced entities. In certain scenarios some source system may post redundant updates to the referenced entity that may lead to the cascading updates to other entities that references the this referenced entity. For example if you have an Individual entity and a reference attribute Address which is constructed using the Location entity, in this scenario using this feature you will be able to prevent configured source system from updating the Location entity through the Individual entity updates.

OV Value Change Detection in the Referenced Entity

Before 2018.3, any change in the entity used to trigger update events for all entities that references this entity. In most of the scenarios, it is desirable to trigger the update events for the entities only when there is a true update to the referenced entity that is when the OV (Operation Value) of the attribute is changed. We are very happy to announce that starting 2018.3, customers would be allowed to configure this behavior for the entities that are referenced by other entities. A referenced entity can be configured to triggered update events for the entities only when there is a change in the OV values of the attributes.

Match and Merge
Relevance Based-matching

In this release we are introducing a new match rule type, called relevance based match rule.This rule type will allow customers to define a match rule and associate an action to be performed based on the relevance score of the match pair. In this type of match rule, customers will be able to assign different weightages to the match attributes.

Learn more
Reltio RDM tenant for Storing Synonym Names Used in Matching

Starting 2018.3, Reltio inbuilt synonym name dictionary will be additionally maintained in the RDM tenant. This feature is also available to the customers who want to maintain their own version of the dictionary of synonym names which can be used in the matching process.

Learn more
External Match API using Google Cloud Storage

We are also excited to announce that the external match API will support Google Cloud Storage (GCS) for storing input and output files.

Support for Processing of Match Consistency Check and Rebuild Match Table Jobs on Selective List of Entities

Starting 2018.3 release, match consistency check and rebuild match table jobs will accept list of entity URIs in addition to the existing supported parameters. This will allow processing of subset of entities through these jobs.

Enhanced Search API
We have enhanced our search API to support additional conditions like "contains" and "Doesn't Start with" filter.

Our search API will also support Accented Characters and Fuzzy search.
Improved Export Capabilities
  • Our export service is enhanced for faster exports, we will be gradually rolling this feature out to all our customers.

  • Starting 2018.3 we will also support exporting without end dated entities.

  • We can now export group nested and reference attributes by anchor attributes.

Data Cleansing

The Reltio Cleanser now enables configuring the casing of the output of the address cleansing. The supported output casings are Upper, Lower, and Proper cases. In addition to the output casing feature, we have introduced a few other configurable options that may be relevant for certain datasets. Please reach out to your Reltio Customer Success representative to review these options for your use case.

Learn more
Life Cycle Actions

Life Cycle Action ( LCA) jar can now be deployed and managed using the IAM roles. Customers are no longer required to share their AWS Keys for the deployment of LCA.

Learn more
Reltio MDM UI
Role Permissions UI Enhancements

Hide and show controlled attributes. We now provide an ability to display non-OV values only to the list of users who are part of configured user role(s). This is especially useful for customers who want the ability to restrict certain users from having visibility on controlled attributes.

Inclusion and exclusion of source systems. Having the flexibility to limit the visibility of values from certain source systems is important for business processes. With this enhancement, customers can now hide values coming from specific source systems based on user roles.

Learn more
Search and View Inactive Entities and Relationships

In this release, users can now search and edit inactive entities and relationships. This is useful if users want to manage entities or relationships that are inactive.

Learn more
Potential Matches Enhancements

We added the capability of filtering on sources and match rules, which now allows users to focus on select potential matches based on these two criteria. In addition, we’ve added the ability for users to do bulk-merge from the potential matches right panel - eliminating the need to first bring the entity into the main screen to do a merge.

Learn more
Search Enhancements

Apostrophe character. We now support searching for values that include apostrophe character. For example, you may now search for a profile with the last name, “O’Malley”, that includes an apostrophe in the text string.

Exact count on potential matches. If you want to search for entities with an exact count of potential matches, you may now do so using our newly added capability through the Advanced Search. This is useful if you want to search for singletons - profiles with 0 matches.

Learn more

We are extremely excited to announce the Beta release of the Explorer application. We are revamping the search experience of our Reltio Cloud MDM platform for a more business-user friendly experience. We are going to retain the robust search functionalities we currently have with our existing Search page, and expand on it by build intelligence, adding more location-based capabilities, and creating a seamless experience between desktop, tablet, and mobile.

Please contact your Customer Success representative if you are interested in becoming part of the Beta program and helping to influence the design of the application.

DTSS Enhancements
  • Contract Threshold Limit Sync Option
    • Decide if connectivity should be disabled or continue to remain enabled for all existing consumed objects in CT after contract threshold limit has been reached
      • Expiration Policy: No_sync (default), Updates_only
      • GET {DTSSURL}/subscriptions/contracts

  • Contract Report
    • A report that shows you aggregated counts of consumed profiles from DT into CT
    • Ability to filter by date/time range, user and entity type(s)
    • POST {DTSSURL}/actions/report/contract
    • Report is generated by a DTSS task for Contract of ID provided in the request. Once the task is finished an email with the report CSV file is sent to email provided in the request

  • DTSS is now deployed natively on GCP and also has support for Pub/Sub

  • Contract Threshold Limit Email Notification Templates
    • Ability to personalize the “Subscription Transaction Limit has been reached” email notification
Hierarchy View

We have added several usability improvements in RDM. RDM users can now view their lookup types in a hierarchical view to understand and visualize the parent child dependencies.

Learn more
Optimized Performance

As a part of better performance in MDM including faster exports, we have optimized RDM architectural design. As a part of this change any change to RDM records will not be automatically applied in MDM but instead customers can invoke a “refresh” job in reltio console to update MDM records with RDM changes. This change will be slowly rolled out via your customer success representative.

Learn more
Reltio Console
Data Loader

Users can access

  • UI via Reltio Console for business users

  • API Endpoint for IT users who want to integrate the Reltio service with their existing ETL tools

Key New Additions Features after EA

  • No limit on volume

  • Available for free to all Reltio customers

  • Ability to assign granular roles for each key step (creating jobs, mapping, executing the load etc.)

  • Data Loader Full self service capabilities provides you with
    • Ability to configure data load in a clear way using UI (either for ad-hoc, initial or ongoing loads)
    • Ability to save such configuration for future re-use and schedule it to run automatically
    • Ability to create, save and select from existing mappings for fast data preparation/conversion across tenants
    • Data pre-processing (mapping, basic transformations etc.)
    • Data preparation (transformed data into batches of JSONs representing Reltio objects - entities, relations etc.)
    • Load pre-processed data into the tenant
    • View relevant statistics at each stage of the process
External Match

External match application enables customers to match an external file against existing records in your tenant using your existing match rules, ability to view job status and download results

Link to access External Match App will be available on Oct 15th

The following capabilities will be incrementally added as we progress with EA

  • Run external match on an entity type using a specific match rule
  • Recommended match rules
  • Downloading results by match rule
  • Download error records
Data Modeler

Ability to create new attributes via the data modeler application in the console.

DQ score / Rank

Key enhancements after EA include

  • Phased rollout of both scores & dashboards to all customer tenants in all non-prod environments

  • A new heatmap graph that plots the entities against the two scores more accurately
    • Each heatmap dot contains a normalized range of DQ score and Reltio Rank and number of entities within that group

  • Ability to configure DQ score definition via Console
    • Add/Modify weights to completeness and recency classifiers per entity type
    • Add/Modify attributes to evaluate completeness

  • Ad-hoc triggering of DQ/IQ job calculation via a single button
    • If configuration has changed, DQ IQ job needs to be trigerred to update scores in MDM
    • Only one job can run at a time
    • This job can be run by pressing a single button on top of the DQ main page
Learn more
Tenant Management

Added new Queues tab that displays the following statistics available for Reltio internal queues (i.e. CRUD, MATCH)

  • Number of messages sent

  • Number of messages in-flight
    • Messages are considered in-flight if they have not yet been deleted or reached the end of their visibility window
    • Number of messages received
    • Number of messages deleted

Learn more

New addition to the "Jobs" tab of the EM app

  • RDM Refresh Job
    • When values and mappings are updated in RDM, these updates do not automatically flow through to existing records in MDM. This job helps to update all such existing records
Learn more
ML and Analytics
  • We've upgraded to Spark 2.3. Below are the key features in this upgrade:
    • Removes attribute limit available in R-IQ DataFrames
    • Improved Performance/Stability
    • Number of other updates for broader Algorithm support (Release Notes)

  • Improved monitoring to pro-actively remediate data synchronization or compaction (optimization) processes

  • Performance optimizations to improve DataAccess performance for smaller entity types

  • R-IQ Console updates
    • Interaction data model mapping
    • Consistency in R-IQ usage reporting (Connector Hours)
    • Custom Job support in Console

  • Supporting RIQ for GCP tenants (Planned for Q4, 2018)

  • Include support for Pin/Ignore attributes in R-IQ

  • Supporting crosswalks for start and end objects

  • Supporting crosswalks for relations

  • Foundational architecture and batch prototype to support Reltio MDM
  • synchronization to Google BQ (EA will be after 2018.3)
    • Support for Reporting and Analytical Queries with Reltio MDM data in Google BQ
    • Interface to view Reports in DataStudio UI

  • Qubole move to per second billing (in UI)

  • Added encryption for secret keys (for newly submitted data import job)
Learn more
Integration Capabilities
Mulesoft Connector
  • New Mulesoft Connector released on Anypoint Exchange

  • Added support for 31 new RELTIO operations

  • Recommended data load option for complex ETL use cases
Learn more
Google Pub/Sub Streaming Pipeline

Reltio customers in Google Cloud Platform can now consume Reltio data change and match events in near real time via Google Pub/Sub, a global managed messaging service. Please contact your customer success representative to enable this feature.

Data as a Service (DaaS)
We have added a new data provider (340B - Covered Entities) in the list of Data as a Service offering and made enhancements to the existing data services.

HRSA - 340B (Covered Entities) data is now available as a data tenant. The data is refreshed on a daily basis and available to the customers for subscription.


The DEA Data tenant has been enhanced with nested address and also data model change for improved user experience.


The NPI Data tenant has been enhanced with nested address. At this time the NPI data tenant supports both nested and reference address structure with no impact to subscribed customer.

Deprecation Notice
The following lists all the features that are being deprecated in the 2018.3 release. We are giving customers prior warning to ensure they have sufficient time to make necessary changes.
  • Support for “DYNAMIC” strategy of indexing OV will be deprecated.
  • Support for “Short URL” feature from the Reltio UI will be deprecated.
  • Support for the export entities feature using the abstract entity types will be deprecated
  • Support for the DTSS Subscription Endpoint Security API will be deprecated. Please refer to Security Management for additional information.
Retirement Notice
The following lists all the features that are being retired as part of the 2018.3 release. These features are no longer available.
  • TLS 1.1 Retirement — TLS 1.1 is no longer considered a security best practice by PCI DSS (Payment Card Industry Data Security Standard). Post October 28th, Reltio will no longer support TLS 1.1. All customers are required to move to TLS 1.2 to communicate with the Reltio platform. (TLS 1.2 was first introduced in 2008.)

  • Endpoint Security API Retirement — Reltio introduced a cleaner and more flexible permission model in the 2018.2 release. This new model eliminated the need for the endpoint security API which was complex and had limited coverage. A new API was introduced for programatically managing user access privileges in the new model. The new permission model also provides the ability to restrict a role to a subset of tenants. In the 2018.3 release, the endpoint security API has been retired. Any request to the API will receive a HTTP code of 410 GONE.

  • Update User Tenant and User Role API Retirement — The following two APIs are retired: Update User Role API and Update User Tenant API. Accessing these APIs will now return a HTTP status code of 410 GONE. Assignment of roles and tenants to users is now done at the user account level API.


For any questions, please contact support@reltio.com 

Unsubscribe from email communications