The April 2025 release includes the following changed behavior.
Ingress job
You can no longer create ingress jobs that include taskflows associated with reference data assets in Business 360 Console. To import reference data assets into Reference 360, run a reference data import job in Reference 360.
If ingress jobs include taskflows associated with reference data assets, contact Informatica Global Customer Support.
Previously, you could create ingress jobs in Business 360 Console to import reference data assets into Reference 360. However, the imported assets weren't displayed in Reference 360.
You can now migrate custom assets after you set up at least one licensed business application in the target organization that matches the source organization. Additionally, at least one business application version in the target organization must match the version in the import file that you use for asset migration.
Previously, you had to set up all the licensed business applications in the target organization, and all the org versions in the target organization had to match the versions in the import file.
An updated record can participate in the match process only if you update one of the match fields. When you update business entity fields that aren’t configured as match fields in a master record, the match and merge status of the record doesn’t change to MATCH DIRTY. The decrease in the number of records in the MATCH DIRTY status optimizes the performance of the match and merge process.
Previously, when you updated business entity fields that weren't configured as match fields in a master record, the match and merge status of the record changed to MATCH DIRTY.
For more information about match fields, see Match fields.
Data enrichment
To keep field mappings in a rule association intact, MDM SaaS prevents you from changing the Application Integration process in a data enhancement rule after you save it.
Similarly, after you save a rule association, you can’t change the data enhancement rule and the target in the output mapping.
Previously, you could change the process in a data enhancement rule. You also could change the data enhancement rule and the target in a rule association.
The Application Integration - Recommendation-based Enrichment plugin is renamed to Application Integration-based Enrichment. Also, the plugin is now grouped based on the plugin type.
The following image shows a data enhancement rule setting with Enrichment as the plugin type and Application Integration-based Enrichment as the plugin name:
When you map the output fields in a rule association for data enrichment, it's now optional to specify a source system. If you don't specify a source system, MDM SaaS associates the Default or Informatica Customer 360 source system with the record that's enriched.
Previously, the source system was a required value.
To prevent incorrect field mappings in a rule association for data enrichment, MDM SaaS now validates the data types of the fields that you map. For example, you can't map a decimal field to an integer field now.
Previously, you could map incompatible fields. For example, you could map a decimal field to an integer field.
When you use the export types, such as standard export and export all, to export all records, an egress job now exports the records based on their creation date instead of their last updated date.
Previously, the egress job exported all the records based on their last updated date.
For more information about the export types, see Export job types.
Delete business events
After you delete a business event, you can't reuse the internal ID of the deleted business event.
Previously, you could reuse the internal ID of deleted business events.
