The enrichment and validation process uses objective groups, objectives, and rule associations to determine when and how records are validated, cleansed, or enriched.
Before you configure data enrichment or validation, determine the type of operations, such as validation, cleansing, or enrichment of records, that you want to perform.
You can validate, cleanse, or enrich records. The cleansing operation validates field values, cleanses the values, and enriches records with the cleansed data.
After you determine your data quality goal, you can create an objective group that represents the data quality goal. To the objective group, you can add actionable objectives that accomplish the data quality goal. You can use an objective group to keep all related objectives together. You can also use the objective group to conveniently migrate the objectives between organizations.
An objective represents a data quality requirement within an objective group. You can add multiple rule associations to an objective to run them sequentially to accomplish the data quality requirement. Additionally, you can enable data dependency between rule associations. Use an objective to determine when to trigger enrichment and validations. Also, an objective specifies the types of records to which enrichment and validations must apply. Objectives in an objective group run in parallel.
After you create an objective, you can add one or more rule associations to it. Use a rule association to map the business entity fields to the input fields of an enrichment and validation service or function. When data enrichment or validation is triggered, these input fields are sent to the specified service or function. To specify the fields that you want to enrich or cleanse, you also need to map the output fields of the enrichment and validation service or function to business entity fields. To assign records to a hierarchy, map the output fields to the relationship nodes.
To specify the type of operation to perform, configure and add a data enhancement rule to a rule association. In a data enhancement rule, specify a function or service that connects to an enrichment and validation service as a plugin. MDM SaaS runs a data enhancement rule through a plugin, which can send requests to an enrichment and validation service or function.
When the values of the input fields mapped in rule associations are updated, the associated objectives are triggered. The updated field values are sent to the specified enrichment and validation service or function that returns enriched or validated data. When the service or function returns enrichment or validation results, MDM SaaS updates the output fields with the results.
Note: When a user creates a record, if the user adds a value to a root field and submits a record, all objectives configured for all root fields are triggered. Also, when a user adds a field group entry and saves the section, all objectives configured for the fields of the field group are triggered. This approach allows you to add default values for certain fields in a section or check completeness of the section if those fields are empty.