Changed behavior

You can now configure the real-time publishing of events from business applications to downstream systems.

Previously, you could only publish events from business applications to external targets in batches.

For more information about publishing business events in real time, see Publishing business events in real time.

To prevent excessive match pair generation, MDM SaaS now limits the number of match pairs a match job can generate for each record. If a match job exceeds this limit, it fails. To ensure success, you can either modify the declarative rules or enhance the quality of data to keep the number of match pairs below the limit.

Previously, there was no check on the number of match pairs being generated by match jobs.

For more information about the defining a match job, see Defining match and merge jobs.

Before users can match data from an input file with master data, generate match keys for master records by running a generate search indexes or match keys job. After you generate match keys for master records and run a publish business events job to publish events, the Meta section of event details display the Consolidation attribute value as MATCH_INDEXED for the master records.

Previously, you couldn't generate match keys for master records, and the Consolidation attribute value of Meta section in master records appeared as MATCH_DIRTY.

For more information about generating match keys, see Defining generate search indexes or match keys job.

When you add or update records in real-time or through ingress jobs or file import jobs, advanced rule associations consider the values that you set for the input fields in the Value column.

Previously, advanced rule associations didn't consider the values that you set for the inputs fields in the Value column.

For more information about configuring advanced rule associations, see Adding advanced rule associations.

When you add, import, or update data access rules, the rules change to the draft state. You can review and publish the drafts. When you delete a data access rule, MDM SaaS marks the rule for deletion and permanently deletes it after you publish the changes.

Previously, MDM SaaS allowed you to directly add, import, update, or delete data access rules without moving them to the draft state.

For more information about adding data access rules, see Managing data access rules.

You can now control the user roles that have access to download match output reports from the match and merge job details page. By default, no user roles have access to these reports.

To grant access to a user role, assign the Download Match Output Report privilege to the user role on the Security page.

For existing users who previously had access to these reports, ensure that their custom user roles are updated with the Download Match Output Report privilege to access these reports.

Previously, all users roles had the privilege to download match output reports from the match and merge job details page.

For more information about configuring privileges for downloading match output reports, see Configuring privileges for downloading match output reports.

An ingress job applies data quality rule associations that are added to the mapped fields even when these rule associations are set to run with no input values.

Previously, an ingress job applied data quality rule associations that were added to all fields. However, the job didn’t apply the data quality rule associations that were set to run with no input values.

For more information about defining an ingress job, see Ingress data.

In MDM SaaS, the Translations page is renamed to Localization. The Localization page contains the Translations and Searchable Languages tabs.

The following image shows the Localization page that contains the Translations and Searchable Languages tabs:

Previously, Business 360 Console used Translations as the page name.

Business event payloads don't include spaces between parameters. Additionally, the order of the parameters in the payload might vary each time business events are published.

Previously, business event payloads included spaces between parameters, and the order of the parameters was fixed.

For more information about business event payloads, see Business event payloads.

When you configure basic rule associations with external validation functions, MDM SaaS applies rule associations if you provide a value in any of the input fields.

Previously, MDM SaaS applied basic rule associations with external validation functions if values were provided for all the input fields.

For more information about configuring basic rule associations, Adding basic rule associations.

MDM SaaS extensions are renamed to align with the use cases they address.

The following table lists the name changes to MDM SaaS extensions: