The July 2026 release of Business 360 Console includes the following important notices:
Preview initiated
Effective in the July 2026 release, the following functionalities are available for preview:
Business events based on native workflows
You can use native workflows that you design in Business 360 Console to define business events for business entity records, relationships, and hierarchies. Configure these business events for create, update, and delete actions on data through business applications, file import, ingress, and REST API. You can also configure business events for changes to all field types in a business entity, including dynamic fields.
When you configure business events for create and update actions on record data, you can choose to skip workflows for data that rule associations have successfully validated or enriched.
Stakeholders can view, act on, and add comments to related tasks in the task inbox of business applications. In the ticket manager, they can also view the tickets for workflows to which they're assigned. When a workflow is triggered, MDM SaaS automatically creates a ticket with details, such as task statuses and comments.
Disabling and enabling business events
You can disable a business event to prioritize another one or to save it for future use. You can enable disabled business events when you want to use them. If multiple business events apply to a change, the most recently updated business event takes precedence.
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.
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 about the following upcoming changes:
Adaptive AI match training
You need to use curated sample data sets to train Adaptive AI match models for improving prediction accuracy.
To prepare for this change, create sample data sets specifically for training Adaptive AI match models and import them into the MDM SaaS data store.
Match explainability metrics
A new process type will be available within a match and merge job for updating match explainability metrics. Run a match and merge job exclusively to update the metrics. Alternatively, trigger the new process type as part of match and merge job.
To prepare for this change, import the new process type into your organization and update existing match and merge jobs to include the new process type. To import the new process type, contact Informatica Global Customer Support.
Informatica intends to include this functionality in October 2026 or later but might choose not to in accordance with changing market or technical circumstances.
Migration of rule associations
Informatica plans to automatically migrate 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, run the migrate rule associations job from the Home page.
After migration, you can continue to create basic, advanced, and DaaS rule associations in your organization.
Informatica intends to include this functionality in a future release but might choose not to in accordance with changing market or technical circumstances.
Validation and cleansing response parameter
In the October 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 October 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 October 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 October 2026 or later but might choose not to in accordance with changing market or technical circumstances.
Dropped support
Effective in the July 2026 release, Informatica dropped support for the following functionalities:
Search using Application Integration through Customer 360 Extension for Salesforce
Support is dropped for searching for similar records using Application Integration through the Customer 360 Extension for Salesforce package.
If you deploy Customer 360 Extension for Salesforce, use the configurable Lightning component available in the extension package to search for similar records.