Components of enrichment and validation configuration

Enrichment and validation configurations include components, such as plugins, data enhancement rules, rule associations, objectives, and objective groups.

The following image shows various components of data enrichment and validation configurations:

Before you configure data enrichment or validation, you need to determine the type of operation to perform. You can validate, cleanse, or enrich records. The cleansing operation performs validation first and then enriches the records with the cleansed data. To specify the type of operation to perform, configure a data enhancement rule.

In a data enhancement rule, you need to 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, such as Application Integration, which can send requests to an external enrichment and validation service, such as OpenAI. The external service then returns data for enrichment or validation results to Application Integration, which in turn sends the data to MDM SaaS.

After you create a data enhancement rule with its plugin configuration, you need to map the business entity attributes to the enrichment and validation service input fields. When data enrichment or validation is triggered, these input fields are sent to the service or function that you specify in the plugin configuration. To specify the fields that you want to enrich or cleanse, you also need to map the enrichment and validation service output fields to business entity attributes. To enrich or cleanse values of records, map the output fields to the business entity attributes. To classify records, map the output fields to the relationship nodes.

To map the business entity attributes to the enrichment and validation service input and output fields, you need to create a rule association. A rule association is an MDM SaaS asset that consists of a data enhancement rule and mappings of input and output fields. A data enhancement rule in a rule association determines the input and output fields of the enrichment and validation service that you can use for field mapping.

An objective is a data enhancement goal that you want to accomplish with one or more rule associations. You can use an objective to combine multiple rule associations and run them sequentially.

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, and the service returns enriched or validated data. If a field is part of multiple objectives, the objectives are triggered in parallel. However, the rule associations in an objective run sequentially.