DaaS rule association for real-time processing

Guidelines for real-time address verification

• •You can’t create a DaaS rule association or edit the predefined DaaS rule association for the predefined postal address field group.
• •You can add one DaaS rule association at each level within nested custom field groups.
• •Before you create a DaaS rule association, ensure that you save any changes to fields of the business entity.
• •Ensure that you map a business entity field to the Country field of the Address Verification DaaS provider.
Note: If you don't map any of the business entity fields to the Country field, the rule can't validate or enrich the values of the address fields in real time.
• •Unlike email and phone validation, if users add an incorrect address in the business application, real-time address verification doesn't display the validation error during record creation. The validation error appears after the user submits the record.
• •When you add a DaaS rule association for real-time address verification to a field group, ensure that block survivorship is enabled for the field group.
• •After users enter address values and submit the record in business applications, DaaS rule associations for real-time address verification are run asynchronously.
• •When you map the input and output fields of a dependent picklist to the data provider fields in the Additional Fields section, ensure that you map fields that belong to the same data type. If data types of the mapped fields don't match, DaaS rule associations might fail.
• • When a DaaS rule association for real-time address verification returns an invalid address with status codes, such as I0, I1, I2, I3, I4, I5, and I6, MDM SaaS downgrades the trust score to 70%.
The status codes indicate that the Address Verification DaaS data provider can't suggest a valid address, returns a partial address, or can't correct an address due to a single match.

Adding a DaaS rule association

1 On the business entity page, select a postal address field group or any custom field group that stores postal addresses.
2For a predefined postal address field group, perform the following steps:
1. aIn the Properties section, click Data Quality > DaaS Real-time.
You can view the predefined <Business_Entity> Postal Address DaaS Rule.
2. bTo view the details of the DaaS rule, click the <Business_Entity> Postal Address DaaS Rule mapping name.
3. cIn the Field Mapping section, view the mapping name and internal ID.
4. dIn the Rule Properties section, enable the rule.
By default, the rule is disabled.
5. eIn the Enrichment Management Options section, choose how to store enriched address values of source records when records are created or updated through REST APIs.
You can choose from the following enrichment management options:
• ▪ Create a patch record for the address values. Creates or updates existing patch records with enriched address values. By default, MDM SaaS uses this option for existing DaaS rule associations.
• ▪ Save the address values in the source record. Updates source records with enriched address values. By default, MDM SaaS uses this option for new DaaS rule associations.
When you modify the enrichment management option for existing DaaS rule associations, MDM SaaS applies the change to records that you add and doesn't affect existing records. When you update address values of existing records through the user interface, MDM SaaS uses the Create a patch record for the address values enrichment management option. However, when you update address values of existing records through REST APIs, MDM SaaS uses the updated enrichment management option.
6. fView a predefined rule that contains a default input and output field mapping.
For more information about the predefined input and output field mapping, see Predefined mapping of input and output fields.
3For a custom field group that stores postal addresses, perform the following steps:
1. aIn the Properties section, click Data Quality > DaaS.
Note: Before you add a rule, ensure that you save the business entity.
2. bClick Add Rule.
A form appears.
3. cOn the Select Data Provider tab, enter a unique name for the rule association.
The predefined rule type is DaaS.
4. dTo enable the rule, select Enable Rule.
5. eIn the Enrichment Management Options section, choose how to store enriched address values of source records when records are created or updated through REST APIs.
You can choose from the following enrichment management options:
• ▪ Create a patch record for the address values. Creates or updates existing patch records with enriched address values. By default, MDM SaaS uses this option for existing DaaS rule associations.
• ▪ Save the address values in the source record. Updates source records with enriched address values. By default, MDM SaaS uses this option for new DaaS rule associations.
When you modify the enrichment management option for existing DaaS rule associations, MDM SaaS applies the change to records that you add and doesn't affect existing records. When you update address values of existing records through the user interface, MDM SaaS uses the Create a patch record for the address values enrichment management option. However, when you update address values of existing records through REST APIs, MDM SaaS uses the updated enrichment management option.
6. fSelect a data provider to enrich the address values.
The supported data provider is Address Verification DaaS.
7. gIn the Input and Output Fields of the Data Provider section, view the input and output fields of the data provider.
8. hClick Next.
9. iOn the Map Input and Output Fieldstab, enter a unique name for the field mapping.
10. jIn the Input Field Mapping section, to map fields, drag the business entity fields to the data provider fields.
11. kIn the Output Field Mapping section, to map fields, drag the data provider fields to the business entity fields.
12. lClick Save.

Predefined mapping of input and output fields