Configuring rule associations for data enrichment and validations

1To group related objectives, create an objective group.
2Add an objective to the objective group.
3To map input and output fields of data providers, add rule associations to the objective.
1. aTo specify the data provider, add or create a data enhancement rule.
2. bTo specify the fields or relationships to enrich, map input and output fields.

Step 1. Creating an objective group

1Open the business entity that you want to enrich, and click Data Quality > Objective Groups.
2Click Add Objective Group.
3In the Objective Group dialog box, enter a name and internal ID for the objective group, select a folder, and save the objective group.

Step 2. Adding objectives to an objective group

1On the business entity page, click Data Quality > Objective Groups.
2Open the objective group that you want to add objectives to.
3To create an objective, click Add Objective.
4In the Properties panel, specify properties such as name and description.
The Properties panel also displays settings, such as Record Types and Triggers. These settings determine the types of records to which you want to apply an objective and when to apply it.
5Enable the objective.
6To specify the types of records, click Edit in the Advanced Settings section, and perform the following steps:
1. aClick the Records Types tab.
2. bTo apply the objective to master records, select Master Records.
3. cTo apply the objective to source records, select Source Records, and specify a source system.
By default, the objective is triggered for all records. If you specify a source system, the objective is triggered only when the source record belongs to the specified source system.
7To enable data dependency between rule associations, turn on the Enable data dependency between rule associations toggle.
8To trigger the objective when records are submitted in business applications, click the Triggers tab in the Advanced Settings dialog box, and perform the following steps:
1. aIn the Business Applications section, turn on the Enable the objective for business applications toggle.
2. bTo prevent users from submitting records that fail validations, select Prevent submission of records that fail validation.
Note: When you configure an objective to apply only to master records, you can't reject records with validation errors. For more information about the rejecting records with validation errors, see Rejecting records with validation errors.
3. cConfigure one of the following trigger conditions:
• ▪ On submission. Triggers the objective when a record is submitted.
• ▪ On field focus change and submission. Triggers the objective when the field focus changes in a record and when the record is submitted.
• ▪ On section save and submission. Triggers the objective when a section is saved and when the record is submitted.
Note: Rule associations that use Application Integration-based plugins don't run when field focus changes. When field focus changes or a user applies changes to a section, rule associations that assign records to hierarchies don't run. You can use the On field focus change and submission and On section save and submission trigger conditions to allow users to preview validation and enrichment results. The results of validation and enrichment are saved only when users submit records. For more information about triggers and trigger conditions, see Objective triggers.
9To trigger the objective when a record is created or updated through REST APIs, click the Triggers tab in the Advanced Settings dialog box, and perform the following steps:
1. aIn the REST APIs section, turn on the Enable the objective for REST APIs toggle.
2. bTo reject records that fail validations, select Reject records that fail validation.
10Add rule associations that you created.
1. aClick Add Rule Association.
A row with the asset picker appears in the Rule Association section.
2. bSelect a rule association, and click the tick mark icon to add the rule association.
3. cTo add more rule associations, repeat steps 11.a to 11.b.
4. dTo change the order of rule associations, click the Action menu and choose Move up or Move down.
11To remove a rule association from the objective, click the Action menu for the rule association and choose Delete.
12Save the changes.

Step 3. Creating rule associations

1On the objective group page, select an objective for which you want to add a rule association.
2In the Properties panel, click Create Rule Association.
3In the Create Rule Association dialog box, enter the details for the rule association, and click OK.
4On the Select Rule Association page, select or create a data enhancement rule.
Note: After you save the rule association, you can't change the data enhancement rule.
For more information about creating a data enhancement rule, see Creating a data enhancement rule.
5Click Next.
6On the Map Fields page, click the Input Mapping tab.
7To specify the fields on which the rule association must run, map the business entity fields to the data provider fields.
Note: To map a source field with a target field, select fields from the source and target panels, and click Map Selected. You can also assign a static value instead of mapping a field.
8Click the Output Mapping tab, and select a source system.
Note: When you map output fields in a rule association without specifying a source system, MDM SaaS associates the Default or Informatica Customer 360 source system with the patch record that's created or updated as a result of data enrichment.
9Map output fields to accomplish one of the enrichment use cases.
• - To enrich fields of records, select a business entity as the target and map the data provider fields to the business entity fields or assign a static value.
• - To classify records, select a hierarchy model as the target and map the data provider fields to the relationship nodes in the hierarchy model.
Note: After you save the rule association, you can't change the target. For example, if you select a hierarchy model as the target, you can't change the target to another hierarchy model or a business entity after you save the rule association.
10If you choose a data enhancement rule that uses a validation or cleansing plugin, configure validation on the Configure Validation tab.
1. aFrom the Error Status list, select one of the following options to define the severity of the validation failure:
• ▪ Information. For minor data quality issues. Users can save the data.
• ▪ Warning. For less severe data quality issues. Users can save the data.
• ▪ Error. For severe data quality issues. Users can't save the data.
11Configure the percentage by which you want to downgrade the trust score for fields that fail validation.
1. aAdd a field to downgrade the trust score.
2. bEnter the percentage of trust score to downgrade when the validation fails.
12Save the rule association.
13Add the rule association to an objective.

Creating a data enhancement rule

1On the rule association page, click Add Data Enhancement Rule.
2In the Add Data Enhancement Rule dialog box, enter the details of the rule, and click OK.
3On the Data Enhancement Rule Settings page, select a plugin from the plugin list.
For more information about the type of operations and the available plugins, see Configuring validations, Configuring data enrichment, and Configuring cleansing and standardization.
4Specify the plugin parameters.
5Save the data enhancement rule.

Guidelines for configuring data enrichment

• •Ensure that you create custom Application Integration processes based on the guidelines for creating processes.
• •To track enriched records, define a custom source system. When you map output fields in a rule association without specifying a source system, MDM SaaS associates the Default or Informatica Customer 360 source system with the patch record that's created or updated as a result of data enrichment.
• •If you configure data enrichment to display recommendations for classifying records, ensure that you add the Hierarchy component to your custom page of the view edit type. Without the Hierarchy component, CLAIRE panel doesn't display recommendations in business applications.
• •If you update the data types of fields in a process or add new fields to a process, the changes don't reflect in the data enhancement rule and rule association that use the process. To update the field mappings in the rule association, create and configure a new data enhancement rule and a rule association.
• •Ensure that you map the compatible fields. For more information about compatible fields, see Guidelines for field mappings.
• •When you create a data enhancement rule, ensure that you use a published process with valid input and output payload formats. If an existing data enhancement rule doesn't work, verify and correct the input and output formats of the process that the rule uses. For more information about valid input and output formats, see Creating a process for data enrichment.
• •After you configure or migrate a data enhancement rule that uses an Application Integration process, ensure that the value in the Process Name property matches the API name of the process.
• •Ensure that you create unique data enhancement rules. You can't create multiple data enhancement rules with the same configurations.
• •When you configure an objective with the On field focus change and submission trigger condition, ensure that the rule associations within the objective use compatible plugins. You can't use the Application Integration plugins with the On field focus change and submission trigger condition.
• •When you create objective groups, rule associations, and data enhancement rules, specify unique names for them. You can't create multiple assets with the same display name in the same location.
• •When you configure an objective for source records, don't add a rule association that assigns records to a hierarchy. You can't assign source records to a hierarchy.
• •When you configure an objective with the Section save and submission trigger condition, don't add a rule association that assigns records to a hierarchy. Rule associations that assigns records to a hierarchy don't run when a user applies changes to a section in a record.
• •When you specify a value to downgrade trust scores of fields that fail validation, specify a value between 0 and 100.