The October 2024 release includes the following changed behaviors.
Basic rule associations
When you configure basic rule associations with functions, such as maximum length, minimum length, maximum precision, and maximum decimal scale, MDM SaaS doesn't apply basic rule associations if fields contain null or negative values. Additionally, MDM SaaS doesn't apply basic rule associations with functions, such as maximum value, minimum value, data range, regular match, if input fields associated with the rule condition are null.
Previously, MDM SaaS applied basic rule associations with these functions even if fields contained null or negative values or input fields were null.
A match and merge job now excludes reverse match pairs to prevent the export of a large number of match pairs. For example, if records A and B form a match pair and records B and A form another match pair, the job excludes the pair with the lower score.
Previously, a match and merge job included all match pairs that were generated.
Create Match and Merge Job Instance API
The Create Match and Merge Job Instance API now retrieves the business entity details directly from the job definition, eliminating the need for the businessEntity parameter in the request body. If you include the parameter in the request body, the API ignores the parameter and processes the request.
Previously, you had to specify the businessEntity parameter in the request body.
You can now view the latest build and organization versions of all licensed business applications in the user interface.
Previously, you could view only the latest build and organization versions of Customer 360 SaaS even though you had licenses to other business applications.
Workflow approval task
When a custom user role with approver privileges is denied access to certain records based on a data access rule condition, users who are assigned this custom user role can't view approval tasks. If users create, update, delete, merge, or unmerge records and submit them for approval in business applications, the approvers can't view approval tasks in the workflow inbox in business applications.
Previously, approvers could view approval tasks even if their user role was restricted from accessing records based on a data access rule condition.
You can import MDM SaaS assets only if the org versions in the import file and the target organization match. Before you migrate MDM SaaS assets, ensure that both source and target organizations are upgraded to the October 2024 build version. If you use any extensions, migrate the extension assets between organizations that are upgraded to the October 2024 build version.
Note: If the source and target organizations are on different PODs, ensure that you migrate assets after both the PODs are upgraded to the October 2024 build version.
Previously, Informatica recommended migrating assets between organizations with the same org version as a best practice. However, there were no restrictions on importing assets from the source and target organizations that have different org versions.
For more information about importing assets, see Importing assets.
Record and field privileges
Record and field privileges include the following changes:
•The merge option now appears on the search results and record details pages if users have the merge privilege.
Previously, users required create and merge permissions for the merge option to appear on record details and search results pages.
•The unmerge option now appears on the search results and record details pages if users have the unmerge privilege.
Previously, users required read, merge, and unmerge permissions for the unmerge option to appear on the record details page.
•Users now require the merge, unmerge, delete, or restore privilege for the corresponding options to appear on the record details page.
Previously, users didn't require these privileges for the options to appear on the record details page. However, error messages appeared when users performed those actions.
•Users with custom user roles can add or update field values even without having the read privilege for those fields.
Previously, users with custom user roles required the read privilege to add or update field values.
•If you don't have the read privilege for a field, you can view the field but not its value.
Previously, without the read privilege you couldn't view the field or its value.
To align with the data enrichment functionality, the asset types related to DaaS rule associations for real-time address verification are renamed in MDM SaaS.
The following table lists the current and previous names of the asset types: