Changed behavior

To efficiently use resources, MDM SaaS restricts you from publishing draft data access rules for a business entity if an existing job is in progress for the business entity. When you review and publish draft data access rules, the business entity appears disabled, and you can't select and publish the draft data access rules for the business entity.

Additionally, if the publish data access rules job that ran earlier for a business entity fails, the business entity appears disabled.

To review and publish draft data access rules for the business entity, wait until the current job completes or restart the failed publish data access rules job from the My Jobs page.

Previously, no business entities were disabled, and you were able to select and publish the draft data access rules for any business entity.

For more information about the reviewing and publishing data access rules, see Reviewing and publishing data access rules job.

In Operational Insights, to view an updated count of source records, master records, and users, you can refresh MDM SaaS usage metrics only once per week.

For existing users, when you refresh MDM SaaS usage metrics for the first time, the source and master record counts change to 0 until the Refresh MDM SaaS Usage Metrics job runs successfully.

Previously, you could refresh MDM SaaS usage metrics multiple times per week.

For more information about the usage statistics for MDM SaaS, see Monitor usage statistics for MDM SaaS.

When you ingress records with business IDs through ingress jobs, the business event payload includes fewer events compared to previous releases. For example, when you ingress two source records with the same business ID, only one master record is created for both source records. The event payload includes one MASTER_UPDATED event and one MASTER_CREATED event.

Previously, a master record was created for each source record, resulting in two inactive and one active master record. The event payload included one MASTER_MERGED, one MASTER_CREATED, and two MASTER_UPDATED events.

For more information about business event payloads, see Defining publishing events.

When you configure an advanced rule association and map an output field to a picklist field, if the rule statement output returns null or empty values, MDM SaaS removes the existing value of the picklist field.

Previously, when the rule statement output returned null or empty values, MDM SaaS didn't remove the existing value of the picklist field.

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

When you create a mapping with Business 360 FEP Connector to ingress or egress hierarchies, the field names in the source or target transformation now contain _parent and _child keywords based on the field type.

The following sample field names contain _parent and _child keywords:

Previously, the field names in the source or target transformation had the _from and _to keywords.

If you have any existing mappings with Business 360 FEP Connector to ingress or egress hierarchies, you must synchronize the input or output fields.

For more information about synchronizing the fields, see Synchronize fields in a mapping.