The October 2026 release of Business 360 Console includes the following new features and enhancements.
Mapping fields
In modernization projects, you can now use an interactive user interface to review and map objects between the MDM Hub and MDM SaaS. You no longer need to generate mapping files to manually map fields.
You can continue to edit or modify manual mapping files for existing modernization projects that aren't completed.
Modernization project enhancements
The modernization projects now include the following enhancements:
•You can create a consolidated summary of modernization progress across selected modernization projects. The summary shows key metrics on a read-only page, such as the number of objects modernized, in progress, pending, and excluded from modernization.
•You can now archive modernization projects to accommodate more active projects. However, archived projects are read-only and you can't move them to the active state again.
Search
To enhance search accuracy, MDM SaaS now returns more relevant results. When you search for records, you might notice changes in your search results. For example, a search for a record with the first name Benjamin also returns records with the first names Ben and Benny.
Reset organization
You can request to reset your organization to its default, newly provisioned state. A reset permanently deletes all data, assets, configurations, jobs, and job schedules in MDM SaaS. Consider a reset when configurations or extensive customizations make a development or QA organization difficult to manage, and starting over is simpler than fixing it. To request a reset, contact Informatica Global Customer Support.
Ingress records
When you run an ingress job, you can update individual fields in a target record instead of replacing the entire record. The update applies only to the fields that are present in the source system and mapped to the target, while other fields remain unchanged. You can also control how the update handles empty values in mapped fields. When a mapped field has an empty value in the source system, you can overwrite the target value with null or leave it unchanged.
Default values
You can now configure default values for all business entity fields. When users create a record, MDM SaaS automatically populates the fields with their default values, which users can choose to edit. When you ingress, import records, or create records through REST APIs, fields without values are updated with their default values.
Enrichment and Validation Orchestrator
Enrichment and Validation Orchestrator includes the following new features and enhancements:
Configurations for the product experience agent
Users of business applications can now use the product experience agent to classify and enrich records with product data.
You can configure the following settings for the product experience agent:
- On Request. Determines whether CLAIRE can run objectives on request when users prompt CLAIRE Copilot to enrich records. You can now specify whether objectives run automatically or on request. Automatic objectives run when records are created or updated. The existing objectives are automatic objectives by default.
- CLAIRE as a trigger. Determines whether CLAIRE can run an objective.
- CLAIRE-Based Enrichment plugin. Classifies records with product data. When users prompt CLAIRE Copilot to classify records, MDM SaaS runs the data quality objectives that use the CLAIRE-Based Enrichment plugin and classifies the records.
Error messages in Application Integration-based plugins
The Application Integration-based plugins for validation and cleansing can now return error messages for the fields that fail validation. If you configure the rule associations to show these messages, those fields display the error messages. As a result, you can now show specific reasons for validation failures instead of a generic message.
Non-anonymous process authentication
If you enable a data enhancement rule to use a process with non-anonymous access, your organization can now use the session ID authentication type in addition to the JWT authentication type.
Draft records
If you configure objectives to reject records, MDM SaaS still allows users to save the drafts with validation errors. As a result, they can continue to work on the drafts with validation errors until they're ready to submit them.
Product experience agent
Users of business applications can now use the product experience agent to classify and enrich records with product data. You can enable or disable the product experience agent for individual business entities. When users prompt the product experience agent to enrich and classify records in business applications, the agent shares the metadata and data with external LLMs. These external LLMs don't use them to train their models. The data residency and retention policies that apply to CLAIRE GPT also apply to the product experience agent. When you enable the product experience agent, you give MDM SaaS your consent to share the information.
The product experience agent is designed to enrich and classify only product data. Before you enable the agent for a business entity that doesn't represent product data, assess whether sharing the data of the business entity with external LLMs meets your organization's requirements.
The following image shows the properties of Person business entity with the option to allow the product experience agent to share data with external LLMs:
REST API
Business 360 REST API includes the following new resource:
Hierarchy API
Use the hierarchy REST API to create, update, delete, and filter hierarchies. You can add, retrieve, and delete parent and child records. You can move records within a hierarchy or across hierarchies. You can also retrieve the exact location of a specific record in a hierarchy by returning all paths from the parent record to the child record and find a list of hierarchies that a record is part of based on its business ID.
For more information about the REST APIs to manage hierarchies, see Business 360 REST API Reference.
