RDM now supports new locales

Reference Data Management now supports the following locales without a region attached: en (English), pt (Portuguese), and zh (Chinese). This allows you to load multilingual data from legacy systems that don't include region-specific language settings.

This feature and related documentation will be available on the Production tenant on December 19, 2025.

Workflow tasks now load faster in Inbox Team and All pages

We have improved how the Inbox application retrieves Workflow tasks on the TEAM and ALL pages. You'll now experience significantly faster task loading, with up to 10× better performance.

The Workflow API behavior and responses remain unchanged, only its performance is optimized.

Configure object types and sub-resources in the business Configuration API

You no longer need to update the entire tenant configuration to make a change. With new Configuration API endpoints, you can now retrieve, update, or delete individual object types like entityTypes, relationTypes, groupTypes, and more, without touching unrelated sections of the L3 configuration.

This gives you more control, better automation, and safer updates. You can also manage sub-resources such as cleanseConfig and survivorshipGroups using their own targeted endpoints.

For more information, see Manage configuration by object type and Manage configuration sub-resources.

Survivorship insights in entity and relationship APIs

We've added showAppliedSurvivorshipRules and explainOv as optional parameters to the Get entity and Get relationship APIs. Use them to return applied survivorship rules, group names, participation status, and matched filters in the ovDetails section — making it easier to inspect and debug survivorship behavior. For more information, see Get Entity and Get Relationship.

Partial update support for RDM lookups

You can now make partial updates to RDM lookups without replacing the entire object. The new Partial update API supports insert, update, and delete operations on specific lookup components, including source mappings, localizations, parent relationships, and attributes. This approach reduces payload size, limits unintended data changes, and improves performance for high-frequency lookup updates.

This feature and related documentation will be available on the Production tenant on December 19, 2025.

We're finalizing the 2025.2.3.0 release. DEV and TEST deployments, along with their Release Notes, will be available next week.

Zero Copy Integration with Snowflake

Zero Copy Integration with Snowflake enables Reltio Intelligent 360 to retrieve and build an interaction timeline using data directly from Snowflake in real time, without copying or duplicating it. By federating secure queries to external tables, this feature delivers up-to-date insights while preserving governance and minimizing data movement.

Configure the integration using APIs to link Snowflake tables to interaction types and map external fields to Reltio entities. As profiles are accessed, Reltio Intelligent 360 fetches the latest interactions on demand, no ETL required.

For more information, see Reltio Zero Copy integration with Snowflake at a glance.

Search by Entity ID and System Attributes in Bulk Match Review

You can now refine your search in the Bulk match review screen using system-level attributes such as:

• The entity URI of the record
• Crosswalk details (like source system or load date)
• Audit metadata (like createdBy or updatedTime)

This makes it easier to locate specific records without relying only on domain attributes like name or phone number.

For more information, see Bulk match review at a glance.

Edit submitted DCRs before approval

Reviewers can now edit attribute values directly in an open Data Change Request (DCR) task before approval, without restarting the workflow or submitting a new request. This enhancement helps streamline approvals and reduce data correction cycles in large review queues.

The new full-screen DCR view displays a grouped summary of suggested changes with inline editing, real-time validation, and visual indicators for updated or rejected fields. Users can refine submissions collaboratively, eliminating the need for partial rejections and re-submissions.

For more information, see Edit submitted DCRs before approval.

Support for soft-deleted relationships based on endDate

The Salesforce Connector now supports soft deletion of relationships based on the endDate attribute in Reltio. When endDate is mapped and its value is less than or equal to today's date, the connector skips creating the corresponding Salesforce record. If the record already exists, it's updated with the endDate value, allowing Salesforce to treat the relationship as inactive without requiring a hard delete.

This enhancement helps preserve audit history and maintain synchronization fidelity across systems by avoiding unwanted deletions while reflecting accurate relationship states.

For more information, see Relation Synchronization from Reltio Platform to Salesforce.

New option to skip unchanged attributes in outbound updates

A new profile-level flag, skipUnchangedAttributes, is available in the Salesforce Connector to suppress updates when attribute values haven't changed. When enabled, the connector excludes unchanged attributes from outbound payloads, preventing unnecessary timestamp refreshes and improving stability for survivorship strategies that rely on Last Update Date.

This enhancement is especially helpful when working with nested attributes like Email or Phone, which may otherwise cause frequent no-op updates due to platform refresh cycles.

To enable the flag, add it to the section of your connector profile.

For more information, see Prevent timestamp updates for unchanged attributes.

Skip inactive Salesforce records during sync to Reltio

The Salesforce Connector Managed Package now skips outbound synchronization for records where the IsInactive__c field is present and set to true. This applies to all supported SObject types.

This enhancement prevents stale or logically deleted records from being pushed back into Reltio, helping maintain clean and consistent data across systems. If the field is missing or set to false, records are processed normally.

Skipped records are noted in connector logs with the message: Skipping record due to IsInactive__c = true.

Segmented Grouping: Create Groups at Scale — No Merge Required

You can now logically group related records using match rules, without physically merging entities or inflating profile size. With Segmented Grouping, Reltio automatically creates lightweight group entities that can include hundreds of thousands of members. This preserves lineage and improves search, navigation, and downstream analytics performance. When a group is formed, you'll see a new Members panel in the Profile view. You can explore all associated records directly in the UI, based on the Data Modeler configuration. This capability supports use cases such as householding, merchant hierarchy, and policy-to-person segmentation, delivering insights without compromising operational performance. For more information, see topics Segmented grouping via match rules and Members perspective.

Reltio Address Cleanser update – September 2025

You can use CassUseUSPSPreferredCity to return USPS-preferred city names, or CassPreserveAlias to retain alias street names when using CASS for address verification. For more information, see Reltio Address Cleanser update - Sep 2025.

Disable external streaming without disrupting data pipelines

A new streamingAPIEnabled parameter in tenant configuration allows you to disable external streaming — such as SFDC or DnB — without interrupting internal pipelines like Grouping and DataPipeline. This is especially useful during bulk loads, debugging, or maintenance windows.

Default value is true. Available in Console > Tenant Management > Tenant Configuration > MessageStreaming.

For more information, see Message streaming

Address Auto Complete and Contact Verification updates paused

The Address Autocomplete and Email and Phone Verification features were previously listed in the 2025.2 release (see 2025.2 major Release Notes) but have been temporarily withdrawn as we continue fine-tuning them for a better experience.

Track Interaction updates

We are introducing an enhancement that allows easier visualization and management of interaction data when updates are managed through append transactions . This feature allows users to track changes to interactions (e.g. hotel reservation updates) without modifying existing records — ensuring history is preserved and the latest state is always visible. Here are some key highlights:

• Append only model - Each update creates a new interaction with a unique URI
• GroupKey support - Use a simple attribute as the primary key and set it in the data model
• Streamlined UI - Shows only the latest interaction, and logs previous versions

For more information, see Append interactions using Groupkeys.