Reltio Cloud Release Notes 2017.1

User Experience

Improvements have been made to the APIs and the user interface to enhance user experience.

Security/Compliance: Improvements include SSO and ADFS updates.

Platform Robustness and Performance: Improvements have been made to increase platform robustness and performance.

To enable any of the new features, or if you have any questions, please contact

The following Reltio early access components* are not included in this document:

  • Reltio Insights
  • Reference Data Management
  • Workflow Task Management Portal
  • D&B Connector
  • Reltio Snap Pack

* To obtain release notes for these features, contact

Reltio EnvironmentsPreview environment

Each Preview environment includes new features for this release and is provided for user acceptance testing. The Preview environment for release 2017.1 is rolled out as Reltio Cloud 2017.1.RC1.

  • Based on requests for the Preview environment placed through January 19, 2017, Reltio Cloud 2017.1.RC1 will be available on January 30, 2017.
  • If your request for the Preview environment was not made before January 19, 2017, please send email to to have your request handled individually in a timely manner.
Production, Development, and Test environments

Reltio Cloud 2017.1 GA is deployed on the Development, Test, and Production environments.

  • Rollout of Reltio Cloud 2017.1 GA is targeted for February 27, 2017. Your Development, Test, and Production tenants will be upgraded by 8:00 am on February 27.
  • The upgrade window is from 8:00 pm (PT) on February 26, 2017, to 8:00 am (PT) on February 27, 2017, with no planned downtime.
Data-Driven Applications for Business TeamsDesktop and Mobile UIAuto-populate single value for lookups [2017.1.RC1]

As a usability enhancement, Reltio Cloud desktop and mobile users are no longer required to select a unique derived value to auto-populate drop-down lists when defining attributes in the product UI. Customers can now configure drop-down lists to auto-populate with multiple attributes.

Configuring dependent lookups based on multiple attributes [2016.3.0.1]

Users can now configure dependent lookups based on multiple attributes.

For example, in a case where Country Code and Organization Type are configured as parents of the Organization Subtype attribute, the values in the Organization Subtype drop-down list are determined by the combination of the Country Code and Organization Type attributes. This new functionality provides the flexibility to present lookup values based on multiple dependent parent values. The enhancement supports a data model in which multiple attributes can have associated parent values and specific subtype values.

Error notifications for dependent lookup values [2017.1.RC1]

Dependent lookup values are subject to validation. When a dependent lookup value is not filled, the corresponding field is highlighted on the page for the user to make necessary corrections.

Improved About box [2017.1.RC1]

The About box now contains release versions for all Reltio components, such as Reltio Cloud Platform (Core Engine, Authentication, LCA, DTSS, Image Hosting, and so on), UI, Mobile UI, Workflow Adapter, Workflow UI, and Collaboration.

Role-based visibility of bulk operations in the UI [2017.1.RC1]

In some organizations, there is a need for bulk operations to be available only to specific users only. To address this requirement, Reltio Cloud enables customers to configure the visibility of bulk operations buttons based on user roles.

SearchSearches containing special characters [2017.1.RC1]

Search strings that contain special characters that are found in European languages (such as the German umlaut, the acute, the tilde, and so on) now also return results without these special characters. Customers are no longer required to enter diacritical marks and other special characters in a search string. For example, when a user searches for “Zurich”, the results return “Zurich” and “Zürich”. This increases the convenience of the search feature on desktop and mobile devices.

Searches containing hyphenated words [2017.1.RC1]

When searching for target strings that contain hyphens, users can now search for the string without a hyphen and receive matching hyphenated results. This is useful because customers sometimes forget to include a hyphen on desktop searches, and can search more easily on mobile devices.

Data ModelNew L1 Dun and Bradstreet attributes [2016.3.0.1]

L1 attributes have been added to support D&B integration.

New L1 CASS/RDI attributes [2017.1]

The Reltio Cloud cleanse plugin system now includes a data cleanse function for L1CASS/RDI attributes. Customers can also configure CASS/RDI attributes as custom L3 attributes.

Data TenantsNPI DT updates [2017.1]

To better address data quality issues inherent in NPI data, the following improvements have been made to the NPI data tenant:

  • DQ Score Attributes: NPI-supplied HCP State License data sometimes has blank key values, such as State License Number or State Code. For customers who do not want this data to be present in their CT, the new “DQ Score” attribute enables customers to filter out NPI license data that has a blank State Code value.

  • Alternate Name: NPI data provides two versions of an HCP’s name: "Name" and "Other". In previous Reltio Cloud releases, both versions were loaded into the HCP Name attribute in the NPI DT without labeling them as "Name" and "Other". This improvement eliminates that confusion.

  • Taxonomy Code: NPI supplies State License Numbers, Taxonomy Codes and the associated State as a set of three attributes. In previous Reltio Cloud releases, the Taxonomy Code nested attribute in the NPI DT did not support the State Code for the taxonomy, and there was no way to determine the state for which the taxonomy code was valid. To address this issue, a new attribute "StateCode" has been added to the HCP Taxonomy nested attribute.
Transformational Data Management for IT TeamsCore PlatformAuto-generated IDs [2017.1.RC1]

Reltio Cloud now supports automatically generated IDs (UUIDs) for simple and nested attributes. These UUIDs can also be pre-pended or appended with additional alphanumeric characters to meet specific system needs.

Rematching in background [2017.1]

Typically, when matching rules are changed, match tables must be rebuilt. Starting in Reltio Cloud 2017.1, match tables can be rebuilt by running a task in the background (for more information, and can include updates made since the task started. After rebuild tasks are complete, match tables are updated with new match rule values, which makes the update process seamless.

API: OV Rulesets per user [2016.3.2]

In some organizations, there can be variations per department or group in the way that users treat sources as trusted or different OV logic to build their “golden records”. Additionally, on the business applications layer, various applications or processes may need different OV values. To support these use cases, the ability to define OV Rulesets per user or user role is now available in the Reltio API. OV rule sets can now be associated with specific user roles, or with individual users at a higher priority than role-based associations.

Configuration Validation [2016.3.1]

Reltio Cloud performs pre-deployment tenant configuration validation. In previous versions, if tenant configuration was incorrect, user access was blocked, and assistance was required to reset the configuration. Reltio now supports verification and validation checks for issues that can cause tenants to become unstable or unavailable.

The following validation checks are performed:

  • Misspelled words
  • Incorrect or alternate URI values
  • Incorrect case or spelling for Reltio-reserved words, for example, :RelationTypes instead of relationTypes
  • Badly formed configurations, for example, "entityTypes": [{"uri": "{{replace}}"}
  • Badly formed JSON code

These systematic checks are executed automatically, and prevent invalid configurations from being applied to tenants.

Life Cycle Actions
Conditional LCA execution [2017.1.RC1]

In some cases, it can be more efficient from a computing perspective if an LCA is triggered only under certain conditions. Administrators can now specify LCA execution conditions by using the same format as for search criteria.

Validation ServicesValidation service for attributes [2017.1.RC1] [EA Feature]

The Reltio Validation Framework enables customers to write custom Java code to validate records entered in the UI, and is based on the LCA Framework. Validation has no impact on the data load, and custom error messages can be localized. For more information see Internationalization and Localization.

SecurityReltio Cloud SSO support for ADFS [2017.1.RC1] [EA Feature]

A new “early access” Reltio SSO feature supports Active Directory Federation Services as an external IdP. For more information, see ../security/sso.html#sso__oauthconcepts and OAuth2 Single Sign On (SSO). [2016.3.2]

Reltio Authentication APIs now support SSO authentication. SSO configured tenants retrieve access tokens by exchanging access tokens from SSO providers. Customers can use access tokens generated by third-party authorization servers as credentials to call Reltio APIs.

Release Considerations

Deprecated APIs and features

The APIs listed in this section have been deprecated in this and previous releases of Reltio Cloud. Generally, support for deprecated functions continues for two more major releases unless otherwise indicated. For more information, see Deprecation Notices.

Deprecated in Reltio Cloud 2017

The following APIs have been deprecated in Reltio Cloud 2017.1 and its minor releases.

Deleted tenants automatically removed from user access list [2017.1.RC1]

Users no longer have nonexistent tenants in their access list. When a tenant is deleted, users who had access no longer see the deleted tenant as available.

Deprecated in Reltio Cloud 2016.3

The following APIs have been deprecated in Reltio Cloud 2016.3 and its minor releases.

End of Java 7 support

Due to security concerns, Reltio Cloud no longer supports of Java 7. Effective immediately, all Reltio Cloud customers should update their Java software to the latest version 8 hotfix. Customers who use Reltio LCA solutions that require Java 7 for data load activities, or who use the Reltio REST API in other ways that depend on Java 7 should upgrade to Java 8. Java 7 support ends on 10/27/2017.

End of Transport Layer Security (TLS) v1.0 support

Effective 11/28/2016, Reltio Cloud no longer supports TLS v1.0. Alternative solutions using TLS v1.1 and TLS v1.2 are now supported. Support for TLS v1.0 ends 12/10/2016 for all Reltio Cloud customers.

Authentication for /status endpoint

Effective immediately, all requests for the Reltio Cloud /status endpoint require authentication.

Deprecated in Reltio Cloud 2016.2

The following APIs have been deprecated in Reltio Cloud 2016.2 and its minor releases.

Workflow Adapter APIRetrieve tasks response changes [2016.2.2]

For better performance, the total field has been removed from the following Workflow Adapter operations responses:

  • Retrieve tasks
  • Endpoint: POST {tenantId}/tasks
  • Retrieve group tasks for a user
  • Endpoint:
  • Retrieve closed/open tasks for an object URI
  • Endpoint:
Localized environment URL [2016.2.2]

Prior to this release, to access a localized Reltio Cloud environment, users added a locale identifier to the environment URL. For example, the URL for Russian could be With the new localization paradigm, users can specify their desired locale in their browsers and access Reltio Cloud environment using the standard URL, for example, Locales not not available in the environment default to US English.

Enable or disable LCA flag

The flag used to automatically enable or disable LCA on a tenant at registration time is now deprecated. The Register Tenants, Unregister Tenants, and Retrieve Registered Tenants APIs no longer use this flag.

Secured procedure of exported data access

When users generate data exports in Reltio Cloud, data files are stored in Amazon S3, and users receive email notifications with download links. Prior to Reltio Cloud 2016.2, notifications were sent via unencrypted email and the download links contained Amazon access tokens. This allowed anyone who could access the email to download the data export file.

For greater security, in Reltio Cloud 2016.2 and later, email notifications contain links to a download page in the Reltio Cloud environment that require users to log in with a valid account to download the file. This security update restricts access to exported data to authenticated Reltio Cloud users of the originating tenant for that data.

Deprecated undocumented GET authentication

In an effort to continuously improve Reltio platform security by adhering to the OWASP Top 10 guidelines, Reltio Cloud is deprecating support for undocumented GET requests used for authentication.

Any code that uses the following type GET request must migrate to the POST method for authentication as described in the Authentication API documentation:

GET {{urlAuth}}/oauth/token?username=<>&password=<>&grant_type=password

For more information, see the Authentication API

Note: : For security compliance reasons, this function is deprecated effective with the 2016.1 GA release. This deprecated API was permanently removed on May 22, 2016.

Deprecated in Reltio Cloud 2016.1

The following APIs have been deprecated in Reltio Cloud 2016.1 and its minor releases.

Data APIEntity Events API

The Reltio Activity Log API replaces the following deprecated Entity API functions:

  • Get entity events
  • Get entity event stats
  • Get entity events stats per entity
  • Search entity events with cursor

The following endpoints have been deprecated:

  • POST /subscription/task
  • POST /subscription/task/copy
Reltio UIListView facet

The following UI facets have been deprecated:

  • ListView
  • The new class RelationsView should be used instead.