What's New > July 2025 > Changed behavior

Changed behavior

The July 2025 release includes the following changed behavior.

Match process

Now, only updates to match fields cause patch records to be assigned the MATCH DIRTY status. During the generate tokens step in jobs such as generate search indexes or match keys, match keys are generated only for patch records that have the MATCH DIRTY status. The reduction in the number of records with the MATCH DIRTY status enhances the performance of the match process.

Previously, updates to any field caused patch records to be assigned the MATCH DIRTY status, which resulted in the generation of match keys for all patch records.

For more information about match statuses, see Match and merge statuses.

Enrichment and Validation Orchestrator

The enrichment and validation feature includes the following changes:

•When you map input fields in a rule association, you can't map system fields. They now appear grayed out.

When you update a rule association that uses system fields as input fields, the system fields are removed from the rule association.

For more information about enrichment and validations, see Orchestrating data enrichment and validations.

•After a user submits a record in business applications, MDM SaaS runs rule associations and applies the results of the rule associations to the record. The user can now view the results immediately after the record is submitted and saved. Previously, rule associations ran after a record was saved to MDM SaaS. As a result, the user needed to refresh the page to view the results of rule associations.
•When you send an API request to create or update a record, MDM SaaS runs rule associations and applies the results to the record before the record is saved. The API waits before it returns a response. Previously, APIs didn't wait for the results to be applied.

Search enhancements

The searchable and auto-suggest properties include the following updates:

•To enable system fields as searchable, you must set at least one basic or smart field in a business entity as searchable.

Previously, you could set system fields as searchable without enabling other fields as searchable.

•To enable fields for auto-suggestions, you must set the field as searchable. If existing fields in business entities are enabled for auto-suggestions, ensure that you also set them as searchable.

Previously, auto-suggestions appeared on business applications even if you didn't set the fields as searchable.

For more information about enabling fields as searchable and for auto-suggestions, see Configuring search and report properties for a field.

Master records count

In Operational Insights, the business applications statistics now include the deleted master records in the master record count.

Previously, the master record count didn't include the deleted master records.

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

REST APIs

An object within the records array of the Search API response is renamed from vader to ruleAssociation.

For more information about the Search REST API, see Search API.

Dynamic fields

You can now preview images for URL fields configured for preview purposes when added as root dynamic fields.

Previously, URL fields configured for preview purposes didn't display images when added as root dynamic fields.

For more information about URL fields, see URL fields.

Digital assets

When business users specify a URL to download digital assets or open digital assets in the source service, the URLs appear as hyperlinks.

Previously, the URLs appeared as text.

For more information about URL fields, see URL fields.

Search API

You can filter the search results based on validation statuses using the Search API even when the error remediation property is disabled for a business entity.

Previously, you couldn’t filter the search results based on validation statuses when the error remediation property was disabled for a business entity.

For more information about the Search REST API, see Search API.

Advanced rule associations

If you don't specify a value for a Boolean field that has an advanced rule association configured, MDM SaaS considers the field value as null. The advanced rule association uses null as the input value in the rule logic and returns expected results.

Previously, if you didn't specify a value for a Boolean field that had an advanced rule association configured, MDM SaaS considered the field value as false. The advanced rule association used false as the input value in the rule logic and didn't return expected results.

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