Important notices

Preview initiated

Reprocess Master Data job

You can now run the reprocess master data job to apply the latest data enrichment, validation, survivorship, and search configurations to all master records. The job ensures that your data reflects the latest configuration for data quality, the best version of the truth, and data retrieval.

Ingress records

When you ingress records, you can now update only fields that contain values without overwriting other fields with null values.

Objectives for CLAIRE Copilot

You can now classify records by configuring objectives with the CLAIRE-Based Enrichment plugin. When users prompt CLAIRE Copilot to classify records, data quality objectives that use the CLAIRE-Based Enrichment plugin run. You can also specify whether you want to run objectives automatically when records are created or updated, or on request when users request CLAIRE Copilot to enrich records using objectives. You can configure CLAIRE as a trigger for the on-request objectives.

Note:

By default, all objectives created before the April 2026 release that use triggers, such as ingress, business applications, and REST APIs, are enabled as automatic objectives.

Business events based on native workflows

You can now create and design workflows in Business 360 Console. You can then use these native workflows to define business events for business entity records, related records, and hierarchies.

Relevant stakeholders can then view, act on, and add comments to the related tasks in the task inbox of business applications. They can also view the tickets for workflows for which they're stakeholders in the ticket manager. Tickets are automatically created when workflows are triggered and contain details, such as the statuses of tasks and comments.

Upcoming changes

Migration of rule associations

In the October 2026 release or later, Informatica plans to automatically migrate your existing basic, advanced, and DaaS rule associations in organizations created before the October 2025 release to use Enrichment and Validation Orchestrator.

To avoid automatic migration, Informatica recommends that you run the migrate rule associations job from the Home page before the October 2026 release.

Informatica intends to include this functionality in October 2026 or later but might choose not to in accordance with changing market or technical circumstances.

Validation and cleansing response parameter

In the July 2026 release or later, Informatica requires you to include the groupId parameter in root field objects in the response that an Application Integration process returns for a validation or cleansing request.

To prepare for this change, update existing validation and cleansing processes to include the groupId parameter for root fields. For more information about updating process objects to include the groupId parameter, see Update validation process objects to include group IDs.

Informatica intends to include this functionality in July 2026 or later but might choose not to in accordance with changing market or technical circumstances.

Validation of output payloads from Application Integration processes

In the July 2026 release or later, Informatica requires that all existing Application Integration processes that you use in rule associations return valid payloads. If the processes return empty payloads, the associated rule associations will result in the Exception status instead of the Undecided status.

To prepare for this change, ensure that existing processes return a valid response to MDM SaaS.

Informatica intends to include this functionality in July 2026 or later but might choose not to in accordance with changing market or technical circumstances.

Deprecated support

Search using Application Integration through Customer 360 Extension for Salesforce

Effective in the April 2026 release, the functionality to search for similar records using Application Integration through the Customer 360 Extension for Salesforce package is deprecated. Informatica intends to drop support for this functionality in a future release.

If you are deploying Customer 360 Extension for Salesforce for the first time, Informatica recommends that you use the configurable Lightning component available in the extension package to search for similar records.

For more information about searching for similar records using the Lightning component, see Enhancing the data onboarding experience in Salesforce.

Guided assistance for installing Customer 360 Extension for Salesforce

Effective in the April 2026 release, the guided assistance for installing Customer 360 Extension for Salesforce is deprecated. Informatica intends to drop support for the guidance assistance in a future release.

Session-based authentication

Effective in the October 2025 release, session-based authentication is deprecated. Informatica intends to drop support for session-based authentication in the October 2026 release.

Informatica plans to replace session IDs used for user authentication with JSON Web Tokens (JWT). Organization administrators have the option to use either session-based authentication or JWT-based authentication on the Settings page in Administrator. When JWT authentication is enabled, browser-based user interface communications seamlessly use JWT behind the scenes.

For REST API calls, session IDs must still be included in request headers. However, now the session value carries a JWT with a fixed expiry time configured on the Settings page. As a result, REST API scripts must be updated to handle automatic re-authentication before or after the token expires. For more information, see the JWT Support Knowledge article.

Session-based authentication is the default authentication type. Sometime after the July 2026 release, JWT will be the default authentication method. By October 2026, session-based authentication will no longer be available.