The April 2026 release of Business 360 Console includes the following new features and enhancements.
Lineage of records
You can now display record lineage as an interactive event timeline by adding the Lineage component to a page. A business user can then visually explore the create, merge, and unmerge events in the timeline to gain insight into how a master record evolved over time.
You can now purge code values of code lists along with their relationships and historical data. You can purge code values of custom code lists that aren't picklist values of business entities in business applications, such as Customer 360 SaaS.
For more information about purging reference data assets, see Purging data.
Migrate existing data quality rule associations
To optimize performance and ensure faster validation and enrichment, you can now migrate your existing basic, advanced, and DaaS rule associations to use Enrichment and Validation Orchestrator. When you choose to migrate existing rule associations, MDM SaaS runs the migrate rule associations job. The job automatically creates a predefined objective group for each business entity, objectives, and equivalent rule associations within those objectives.
Rule association migration is applicable to organizations that were created before the October 2025 release.
Note:
Informatica recommends that you first migrate your existing rule associations to use Enrichment and Validation Orchestrator in development and QA environments. After you complete testing the migrated rule associations, run the migrate rule associations job in production environments.
For more information about migrating existing data quality rule associations, see Migrate rule associations.
REST API
Business 360 REST API includes the following new resources and additional parameters within existing resources:
Create Master Record and Update Source Record APIs
You can use the optional _population parameter in the Create Master Record and Update Source Record APIs to assign a population to a record. Match keys are generated for the record based on the assigned population instead of the match model populations to improve match accuracy.
Permissions for data access rules
To provide better access control and enhance data security, you can now set create, update, and delete permissions in record-level and attribute-level data access rules. You can edit an existing data access rule to set create, read, update, and delete permissions. By default, all existing data access rules include the read permission.
Note:
You can't set create permissions in data access rules that you configure with conditions on relationship assets.
The training process of the Adaptive AI match model now includes the following enhancements:
•You can continue training an Adaptive AI match model to enhance its accuracy and precision even after you publish the match model.
•You can retrain an Adaptive AI match model as a new version if the training fails to produce the desired results after you publish the match model.
•You can reset the training of an Adaptive AI match model during or after training if the training fails to produce the desired results.
•You can now use the conclusive label named Requires Manual Review to send record pairs to a data steward for manual review when you train an Adaptive AI match model.
•You can now use the inconclusive label named Skip to skip labeling record pairs when you train an Adaptive AI match model. The record pairs with the Skip label don’t appear for labeling again within the same batch during the training process.
You can now configure rules for field groups to identify URL values in multiple field group entries and display them as preview images in search results, page headers, summary, and related records components.
For example, consider a phone product record containing a field group with URLs for preview images of the front and back of a phone, you can configure a rule to identify the URL of the front side for the search results layout component.
For more information about configuring user interface components, see Configuring components.
Modernize on-premises objects
You can now modernize on-premises objects by migrating them 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. Modernize the objects to take advantage of the scalability, flexibility, and continuous updates that MDM SaaS provides.
You can also modernize objects from third-party MDM providers, such as IBM and Semarchy, through REST APIs.
Enrichment and Validation Orchestrator includes the following new features and enhancements:
•You can configure an objective to run when users create records, update records, or perform both actions.
The following image shows the create and update actions enabled in the advanced settings of an objective:
•You can now use Application Integration processes that require authentication in data enhancement rules. You can also specify the user under whose credentials the Application Integration process will run.
The following image shows a data enhancement rule with the Application Integration-based Enrichment plugin selected:
•You can now configure an objective to run when all input fields of its associated rule associations are empty. When you disable this property, an objective runs only if any of its input fields are updated with a value. When you enable this property, the objective runs if all its input fields are empty or if a value is added to or updated in one of its input fields.
•When configuring an objective for master records with business applications as a trigger, you can now choose to reject master records that fail validation, similar to how source records can be rejected.
•To avoid creating new assets because of changes in a process or a rule specification, you can now refresh data enhancement rules that use the process or rule specification.
•In rule associations, you can map output fields to business entity record fields.
Ingress and file import
You can now view the details for each rule association by downloading the rule association-based report from the load step. You can also continue to view the existing record-based report.
Also, the ingress or file import job metrics in the load step now include enrichment and validation metrics.
Export search results job
When you export search results in a business application, MDM SaaS now creates a job to export the search results asynchronously.
You can view the export search results job and its metrics on the My Jobs page. After you export the search results, download the exported data from the job details page in the MDM SaaS business application.
Merge jobs now include a preliminary step to identify groups of record pairs that are potential candidates for automated merges. The additional step enhances the overall performance of merge jobs.
You can now enable dynamic fields to be searchable and facetable in a dynamic pool. After you enable them, you can search for records based on dynamic field values and filter search results by using dynamic fields in business applications. You can enable up to 50 searchable and 50 facetable dynamic fields in an organization.
You can now configure a text field in a business entity to store values in rich text format. Use the rich text format to style and enhance text by applying formatting options, such as bold, italics, underline, fonts, colors, bullet points, and hyperlinks. Users can enter HTML tags and attributes directly when they enter text values or use the rich text editor to format text values.
You can now use predefined mapplets to integrate securities data from market data providers, such as Bloomberg and London Stock Exchange Group (LSEG), into Securities 360. Use mapplets to normalize complex data formats into a standard market data format and then transform the normalized data into data model attributes of Securities 360.
For more information about the integration assets for market data provider, see Securities 360.
