Deprecation Notices

Notices of deprecation are intended to give you advance warning of functionality that is planned to be removed, usually in lieu of new functionality.

Deprecation Policy

Reltio will announce if it intends to discontinue or make backward incompatible changes to the Services and APIs.

Reltio will use commercially reasonable efforts to continue to operate those services, versions and features identified without these changes for at least one year after that announcement, unless (as Reltio determines in its reasonable good faith judgment):
  • required by law or third party relationship (including if there is a change in applicable law or relationship), or
  • doing so could create a security risk or substantial economic or material technical burden.

Discontinuance of Services and API

Reltio may discontinue any API, Services or any portion or feature for any reason at any time without liability to the customers.

Deprecation Details for 2021.1

Search Dbscan API

Reltio is deprecating the following APIs that allow customers to iterate over entities by EntityType and relations by RelationType:
  • POST {TenantURL}/entities/_dbscan
  • POST {TenantURL}/relations/_dbscan

Why?

Reltio is deprecating these endpoints because these APIs retrieve records directly from the primary storage and retrieving records from the primary storage is inefficient. A full database scan is performed regardless of whether a filter is applied or not.

  • For the use case of iterating over entities and relations, we recommend using entities Search API and Relations Search API.

  • For the use case of fetching entities and relations from Reltio Connected Customer 360, we recommend using the Export Service API.

When?

This API will be deprecated on February 1, 2022. Reach out to Reltio Support if you need any guidance.

Skip Post Processing Parameter

Reltio plans to deprecate the API query parameter - skippostprocessing available in Export V1 and V2 APIs. This parameter is used to specify if the result of the export output will be delivered in a single file or multiple files.

For more information about this parameter, see the following links:

Why?

When the skippostprocessing parameter is set as false in the export API calls, it negatively impacts the performance of the export.

Reltio continuously monitors the platform and identifies different aspects that can lead to stability, performance or consistency issues. The skippostprocessing=false query parameter is identified as a feature that can lead to performance degradation of export jobs.

When?

This parameter will be deprecated on Dec 31, 2021. Reach out to Reltio Support if you need any assistance.

Also, we are proactively auditing the tenants that use these properties and will contact you to provide recommendations, if needed.

FAQ

Q: Are any actions required on the customer side?

A: No actions are needed if you are using the skippostprocessing=true query parameter. If you are using the skippostprocessing=false, we recommend you change the query to true.

The Reltio product team will reach out to you through an email, if additional measures are needed.

Deprecation Details for 2020.3

End of Support for Internet Explorer 11

Reltio plans to stop the support for Internet Explorer 11 effective August, 2021. Microsoft has announced that they will not support IE 11 from August 2021.

Microsoft has also announced plans to make Edge broadly available across more versions of Windows beyond Windows 10. If you are currently using IE 11, we recommend you switch to Edge or another supported browser before August 17, 2021.

What do I need to do?

Update your systems to ensure that you use a browser that will remain supported. See the Reltio Browser Requirements.

Whom should I contact if I need help or have questions?

Contact customer.support@reltio.com if you need any help or have any additional questions.

APIs for Registering and Unregistering of Tenants with Salesforce Connector

Reltio will be deprecating the APIs for registering and unregistering of tenants with the Salesforce Connector in October 2020.

It is recommended that you do not use the following APIs any more:
  • PUT {SFDCConnectorURL}/registration/{tenantId}
  • DELETE {SFDCConnectorURL}/registration/{tenantId}

You will receive a warning message if you continue using the deprecated APIs.

For more information, see:

Why?

You now have two new APIs for registering and removing your tenant with the Salesforce Connector.

  • PUT {SFDCConnectorURL}/registration/{tenantId}/{profileName}
  • DELETE {SFDCConnectorURL}/registration/{tenantId}/{profileName}

These two APIs are specific to your Salesforce Connector configuration profile with a more efficient process of activating/deactivating synchronization between Reltio and Salesforce organizations.

When?

These APIs will be deprecated on October 14, 2020 and will be discontinued from February 24, 2021. Contact Reltio Support if you need any guidance.

Deprecation Details for 2020.2

"maxObjectsToUpdate" Parameter

Reltio will be deprecating an API query parameter - maxObjectsToUpdate available in POST entities and POST objects APIs. This parameter is used to specify the maximum number of events for related objects which could be produced by one request to create/update entities or relations.

For more information about this parameter, see the following links:

Why?

When the maxObjectsToUpdate parameter is specified in the API calls, the system limits the number of events generated for related entities and will rely on background processes that will eventually update all related objects. It is required to regularly run reindex or consistency check tasks for the tenant to sync the updated objects for which events were skipped, otherwise, such objects may be in an inconsistent state.

Reltio continuously monitors the platform and identifies different aspects that can lead to inconsistencies. The maxObjectsToUpdate query parameter has been identified as one such feature that can lead to inconsistencies because it requires customers to execute periodic tasks like reindex and consistency check, this is something that can be easily missed and lead to inconsistency.

When?

This parameter will be deprecated on August 12, 2021. Reach out to Reltio Support if you need any guidance.

Also, we will be proactively auditing the tenants that are using these properties and will contact you to provide recommendations, if needed.

FAQ

Q: Are any actions required on the customer side?

A: No actions are needed for customers that are not using the maxObjectsToUpdate query parameter. For customers that are using this parameter, we recommend them to use Immutable Reference Attributes to achieve similar functionality. In cases where Reltio identifies customers that need additional measures to be taken, Reltio Product team will reach out to them in a separate email.

Older version of Hierarchy Facet

Reltio plans to deprecate the older version (Classic mode) of Hierarchy facet in June 2021. You are requested to enable the new version of the Hierarchy facet at the earliest.

As part of the Connected Customer 360 2020.2 release, we have introduced a new version of the Hierarchy facet which is enabled, by default, only in your development environment. We strongly recommend that you enable the new version in your other environments as soon as possible. To know more about the new Hierarchy Management facet and instructions on how to enable the new version, see Hierarchy Management Facet and Hierarchy Management Facet Settings.

Export Version 1

Reltio plans to deprecate Export Version 1 on 3rd July, 2020, as announced earlier.

We have begun the migration of the customer-facing tenants to Export Version 2. The following endpoints will be deprecated for Export Version 1:

Table 1. Deprecated Endpoints
Deprecated Endpoints Alternative Endpoints Related Documentation
Entities
  • {{ExportServiceURL}}/export/{{TenantId}}/entities/_all
  • {{ExportServiceURL}}/export/{{TenantId}}/entities/_dbscan
  • {{ExportServiceURL}}/export/{{TenantId}}/entities/_scan
Use {{ExportServiceURL}}/export/{{TenantId}}/entities instead of the three deprecated endpoints Export Entities
Relations
  • {{ExportServiceURL}}/export/{{TenantId}}/relations/_all
  • {{ExportServiceURL}}/export/{{TenantId}}/relations/_dbscan
Use {{ExportServiceURL}}/export/{{TenantId}}/relations instead of the two deprecated endpoints Export Relations
Additional version 1 endpoints - {{ExportServiceURL}}/export/{{TenantId}}/all Use the following endpoints separately for each type of export:
  • {{ExportServiceURL}}/export/{{TenantId}}/entities
  • {{ExportServiceURL}}/export/{{TenantId}}/relations
  • {{ExportServiceURL}}/export/{{TenantId}}/activities
  • {{ExportServiceURL}}/export/{{TenantId}}/entities/_crosswalksTree
Following are the links to the topics:

Deprecation Details for 2019.3

Ciphers

Reltio will be deprecating weak security ciphers used for communication between customers and Reltio services over HTTPS (Hypertext Transfer Protocol Secure).

Why deprecate weak ciphers? - Weak ciphers can lead to attackers compromising the communication channels between customers (browsers/applications) and Reltio services.

When will the deprecation take effect? - Reltio will time the deprecation of weak ciphers with the 2019.3 GA release (October 13th, 2019).

What are the next steps? - You will find instructions for your Information Security and Application Development teams here.

Need more information? - Contact the Reltio Security Team (team-security@reltio.com).

Current functionality will remain active and supported for a period of 1 year from the Date of notice of deprecation. The following features will be deprecated:
  • Export version 1.0 - The current functionality will remain active and supported for until July 3rd, 2020.
  • Support for “DYNAMIC” mode of indexOVstrategy
  • Support for “Short URL” feature from the Reltio UI
  • Support for the export entities feature using the abstract entity types
  • Support for the DTSS Subscription Endpoint Security API