The April 2025 release of Business 360 Console includes the following new features and enhancements.
Watch the What's New video to learn about the new features and enhancements in the April 2025 release.
Retention period for historical data
Some customers might see the History Retention tab where they can configure the retention period for historical data.
You can configure the retention period for the history of master data to comply with data retention policies. The retention period can be up to seven years. Historical data that's older than the retention period is permanently deleted and can't be restored.
You can allow business users to manage digital assets by adding URL fields to business entities. You can configure survivorship for URL fields, and ingress and egress URL fields included in records.
For more information about URL fields, see URL fields.
Delete custom assets
You can now delete custom assets, such as business entities, hierarchies, and relationships, after removing any associated dependencies. For example, if a custom page is based on a business entity, you must delete the custom page first before deleting the business entity.
When you delete custom reference data assets in Business 360 Console, the status of the reference data assets changes to unpublished and the reference data assets are removed from the Explore page. When you use an unpublished reference data asset in a picklist, the reference data set is automatically published and then it shows up on the Explore page. To permanently delete the reference data assets, delete them from Reference 360.
Note:
This functionality will be available within seven days after your POD is upgraded to the April release.
Use the Related Entities API to retrieve hierarchical and non-hierarchical relationships along with related records of a master record based on its business ID.
The objective properties now include advanced settings to specify the types of records to which you want to apply an objective and when to apply it. For example, you can apply the objective when a record is created or updated through business applications and REST APIs. By default, master records are enriched when a record is created or updated through business application and REST APIs. Currently, you can't edit these settings.
When you configure data enrichment, MDM SaaS now displays improved validation messages for invalid configurations. Objective groups, objectives, rule associations, and data enhancement rules are validated when you save them. If the existing rule associations fail at run time, contact Informatica Global Customer Support.
Informatica intends to include this functionality in May 2025 or later but might choose not to in accordance with changing market or technical circumstances.
Enhanced reference data identification
When you create a reference data asset, you can now specify a unique internal ID for the reference data asset.
For more information about creating reference data assets, see Create reference data.
Business event payloads
In unmerge events, the following parameters and objects include the following updates:
•The changedFields parameter now has a list of business entity fields that are updated.
•The dataDiff object now contains the business entity fields that are updated, their values, and the type of update.
•The affectedXrefs object now contains details about the source records that the event affects for the RELATIONSHIP asset type.
Business users can now match external data with source records and then import selected records or all records.
This functionality requires the latest MDMExternalMatch process. For more information about downloading the latest MDMExternalMatch process, see Post-upgrade tasks for the April 2025 release.