Before, our integrations with MuleSoft and Salesforce only supported basic authentication with username and password. Now, as part of our continuous effort to improve security, we've added support for client credentials. For more information, see topics Configure the MuleSoft connector to authenticate with client credentials and Migrate Reltio Integration for Salesforce to client credentials authentication.

Our Product, Engineering, and Documentation teams have been busy wrapping up new features for the upcoming major release. We have all the details in our 2024.3 major release notes.

We've updated the Reltio Address Cleanser to improve the quality of your address data:

• Expanded support for new postal code formats and improved address validation in Israel, Taiwan, and Türkiye.

• Rebuilt country data for the United States, where a new data source has improved validation accuracy.

• Refreshed country data for over 30 countries, incorporating the latest available address information.

• Improved parsing for Canada (notably in Québec), France, Germany, Greece, Denmark, and Taiwan, ensuring more accurate address validation.

For a full list of changes, see topic Reltio Address Cleanser update - Sep 2024.

We've increased the sample of records in the batchUnmergeEntities task response from 10 to 1000 to give you more clarity about the entities that are going to be unmerged. For more information, see topic Automatic Unmerge Task.

The countdown to our third major release of the year is underway. Register to join our Product Managers in the 2024.3 Product Release Customer and Partner Webinar on 26-Sep-2024. Then check out our Release Notes next week to learn more about the key new features available to you to preview in your own tenant.

The Engage API will no longer allow customer access to the get all ID generators endpoint. Ensure that you have a record of your existing ID generators and any new generators you configure as you won't be able to retrieve the generator details without the name of the generator. If you don't have this information readily available, please contact us for assistance.

Multi-Factor Authentication (MFA) adds an additional layer of security by requiring you to provide a second form of verification in addition to your password. This makes it much harder for attackers to gain access to accounts. Even if a your password is compromised, the second verification factor prevents unauthorized access. Reltio offers the following two options for MFA:

We've changed the dates for implementing Single Sign-On (SSO)/Multi-Factor Authentication (MFA) feature. For more information, see topic Enhance your security with Single Sign-On (SSO) and prepare for Multi-Factor Authentication (MFA).

Previously, when you loaded data using a JSON file, the data loading job's transformation process converted the data into a table.

Now the Data Loader supports loading jobs for RELTIO_JSON files which don't need to go through the transformation process. This enables you to load a large number of records with a single data loader job 2024.2.1.0 weekly release notes | 24-Jun-2024.

We're rolling out this capability through our API first. In a future update this functionality will be made available in the Console UI.

Previously, you could only control whether the Data Loader consolidated records with the same crosswalk using the Data Loader. Now, you can enable/disable this behavior with the Consolidate records with same crosswalk value option in the Console Data Loader.​ For more information, see topic Group multiple records into a single entity.

• Refreshed the data of several countries, including Afghanistan, Australia, Canada, Spain, and the US, with updated address information.
• Corrected geocode data in Mexico, handled missing administrative areas in Spain, and resolved parsing issues for sub-building fields in Denmark.
• Standardized postal code lengths to 7 digits for Israel.
• Renamed the administrative area Csongrád to Csongrád-Csanád in Hungary.

Just a reminder to start migrating your service accounts to client credentials as soon as possible. This is crucial for ensuring the continuous operation of your automated processes and integrations, as well as maintaining security and compliance. For more details, see topic Migrating service accounts from password to client credentials authentication.

We're introducing a new API endpoint designed to improve your experience with testing cleanser configurations for matching rules. With the new endpoint, you can test cleanser configurations by passing an array of simple values and the cleanser configuration, to then receive cleansed outputs for each of the values. For more details, see topic Cleanse simple values with custom configuration.

Previously, you couldn’t control whether the Data Loader merges records with the same crosswalk in data load jobs. Now, you have an option to enable/disable this behavior via the Reltio API. When disabled, the Data Loader skips the pre-processing step to check for duplicate crosswalks, resulting in faster load times.​ For more information, see topic Create one entity from multiple records.

Previously, when you were performing a data loading job and the error threshold limit was reached, you would see the status "COMPLETED_WITH_ERRORS". Now, the status is "STOPPED" with an additional error message like: "The job was stopped as error threshold limit 15% was reached. Actual is 16.8% (306 to 1819 profiles)." For more information, see topic Data Loader.

In our 2024.1.16.0 release, we introduced new options to filter profiles by pinned and ignored attributes. These options are now also available in the Advanced Search UI. For more information, see topic Advanced search with pinned or ignored attributes. For the API details, see topics Search for Pinned or Ignored Entity attributes and Search for Pinned or Ignored Relation attributes.

For more information, see topic Configuring Cleanse to use Raw Value when lookup fails.

The Reltio Enrichment with D&B previously processed your entry files for updates to Reltio sequentially. With the new parameter IS_PARALLEL_FILE_PROCESSING set to true, the integration processes the entry files in parallel for improved performance. For details on performance parameters, see section Configuration parameters in topic Modes of Operation.

Have you used the Collaborative Profile Creation feature, and its authoring workflow, to create profiles? Well, we've streamlined this process to make it even easier to accept or reject workflows. Now, instead of having to navigate to the Notification Inbox, reviewers and approvers can approve or reject them directly in the Profile view. For more information, see topic Suggest and save profiles using the authoring workflow.

Our Proactive Monitoring System bypasses match rules that could slow things down. We've introduced a new inspection rule to keep the system running smoothly. When an Automatically Group match rule generates many groups with 50+ participants, it will be skipped until you take action. For more information, see topic Proactive Monitoring System for Match Rules.

Starting in June 2024, the United States Postal Service (USPS) is updating counties per changes by the Connecticut legislature. In June 2022, the State of Connecticut adopted nine planning regions as county-equivalent geographic units, replacing the eight counties which had ceased to function as governmental and administrative entities in 1960.

For example, the city of Hartford, formerly in Hartford county, is now in the new Capitol planning region.

For more information, see topic Mapping Input Attribute.

In the Hub Profile Relationship view, arrows depict relationships between the start and the end entity. We've corrected an error where the arrow directions and labels were inconsistent. Now the labels match the direction. For more information, see topic Detailed View of the Related entity.