The April 2026 release of Business 360 Console includes the following important notices.
Preview initiated
Effective in the April 2026 release, the following functionalities are available for preview:
•You can now run the reprocess master data job to apply the latest data enrichment and validation configuration, survivorship configuration and search configuration 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.
•When you ingress records, you can now update only fields that contain values without overwriting other fields with null values.
•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 record 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.
•You can now create and design workflows in Business 360 Console. You can then use these workflows that are native to Business 360 Console 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.
Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in production environments or any environment that you plan to push to production. Informatica intends to include the preview functionality in an upcoming release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.
Upcoming changes
We want to let you know that by October 2026 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 manually migrate your basic, advanced, and DaaS rule associations before the October 2026 release. You can migrate your existing rule associations by running the migrate rule associations job from the Home page.
Informatica intends to include this functionality in October 2026 or later but might choose not to in accordance with changing market or technical circumstances.
Deprecated support
Effective in the April 2026 release, the following functionalities are deprecated:
•Searching for similar records using Cloud 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.
•The guided assistance for installing Customer 360 Extension for Salesforce is deprecated. Informatica intends to drop support for this installation approach in a future release.
•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.
Deprecated functionality is supported, but Informatica intends to drop support in a future release. Informatica requests that you transition to different functionality before the functionality is dropped.
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.
Deprecated functionality is supported, but Informatica intends to drop support in a future release. Informatica requests that you transition to different functionality before the functionality is dropped.