Configuring rule associations using objective groups
You can use Enrichment and Validation Orchestrator to configure data quality rule associations that are equivalent to the basic, advanced, and DaaS rule associations in an objective group through plugins.
The plugins are grouped into categories, such as Validation, Transformation, Enrichment, and Cleansing and Standardization. For example, to validate a date range and transform an input field value into upper case, you can use the Date Range validation plugin and the Uppercase transformation plugin.
MDM SaaS provides predefined data enhancement rules for creating rule associations that are equivalent to basic, advanced, and DaaS rule associations.
Note: Ensure that you don't edit or delete predefined data enhancement rules.
For example, your goal is to validate the first name field to check whether the value contains only the specified allowed characters. After validation, you want to transform the first name to uppercase and then verify and standardize the address values of records. To run all these steps sequentially, you can configure an objective group, add an objective, and include rule associations specific to your requirements in the desired order.
To achieve this goal, you can use the predefined data enhancement rules, such as Allowed Characters, Uppercase, and Address Verification. When MDM SaaS runs the objective, the rule associations are run in sequence.
Additionally, you can also configure objectives to trigger when you import records in bulk or add records in real time through business applications or REST APIs.
Consider the following differences in data quality rule associations between organizations created before and after the October 2025 release:
•MDM SaaS doesn't impact existing basic, advanced, and DaaS rule associations in organizations that were created before the October 2025 release. Additionally, you can also configure objective groups, objectives, and rule associations through plugins.
If you create rule associations using objective groups, MDM SaaS uses Enrichment and Validation Orchestrator to run rule associations.
•When you create basic, advanced, and DaaS rule associations in organizations created after the October 2025 release, MDM SaaS uses Enrichment and Validation Orchestrator to run rule associations. MDM SaaS creates a Predefined Objective Group for <BusinessEntity_Name> on save of the business entity. The predefined objective group contains objectives and rule associations that are equivalent to the basic, advanced, and DaaS rule associations.
The following image shows the predefined objective group for the Person business entity:
You can view the predefined objective group on the Explore page. You can't open, add, update, or delete the predefined objective group.
•You can't migrate assets between organizations that were created before the October 2025 release and those that are created after the October 2025 release.
If you use an organization created before the October 2025 release, MDM SaaS continues to run rule associations without any issues. However, if you want to use an organization after the October 2025 release and run rule associations that were created before the October 2025 release, you require a new organization. To request for a new organization, contact Informatica Global Customer Support.
•When you create basic and advanced rule associations in organizations created after the October 2025 release, MDM SaaS creates objectives and rule associations using Enrichment and Validation Orchestrator. To delete these basic and advanced rule associations, you must be assigned the Designer or MDM Designer user roles.
