The October 2025 release of Business 360 Console includes the following important notices.
Preview initiated
Effective in the October 2025 release, the following functionalities are available for technical preview:
•You can use a business entity record field to map an output field in a rule association.
•You can modernize by migrating the on-premises configuration from the MDM Hub to MDM SaaS. You can modernize objects, such as lookup tables, business entities, user roles, users, match rule sets, survivorship configurations, source systems, hierarchies, and relationships. Migrate to MDM SaaS to take advantage of the scalability, flexibility, and continuous updates that it provides.
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 April 2026 or later, you can migrate your existing basic, advanced, and DaaS rule associations to Enrichment and Validation Orchestrator. During migration, MDM SaaS automatically generates a predefined objective group for each business entity and then creates objectives and equivalent rule associations within those objectives.
During the load step of an ingress or import job, all objectives run in parallel and rule associations within each objective run sequentially. However, the existing basic, advanced, and DaaS rule associations run during the transform step. After you migrate the existing rule associations, Enrichment and Validation Orchestrator runs them during the load step.
Because objectives run in parallel, rule associations across objectives might also run in parallel. To prepare for the change, avoid creating rule associations in Enrichment and Validation Orchestrator that depend on the results of the basic, advanced, and DaaS rule associations until you migrate them.
For example, your organization contains a basic rule association that concatenates first name, middle name, and last name and uses the concatenated value as full name. Additionally, you have a rule association in Enrichment and Validation Orchestrator that validates the length of full name. After you migrate the basic rule association, both rule associations might run in parallel because they are part of two different objectives. If the rule association that validates the length of full name runs before the rule association that concatenates the first, middle, and last names, you might not get the expected results. For more information about rule association migration, contact Informatica Global Customer Support.
Informatica intends to include these functionalities in April 2026 or later but might choose not to in accordance with changing market or technical circumstances.
Deprecated support
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). Starting on November 3, 2025, you have the option to switch from session-based to JWT-based authentication on the Organization page in Administrator. Once 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 as usual. However, now the session value carries a JWT with a fixed expiry time configured on the Organization page. As a result, REST API scripts need to be updated to handle automatic re-authentication before or after the token expires. For more information, see the JWT Support Knowledge article.
In the October 2025 release, session-based authentication will remain the default. Starting in April 2026, JWT will become the default authentication method. By October 2026, session-based authentication will no longer be available.