To enrich records with additional data from data providers or to transform data in records, configure rule associations that use enrichment or transformation plugins.
You can enrich records by transforming the data within them.
To perform advanced data enrichment, you can also connect to external data providers and enrich records with the data that they return. For example, you can connect to OpenAI ChatGPT to translate the product description in an Item record.
Note:
Enrichment is triggered and applied to a record even users don't have access to certain fields involved in the enrichment process.
The following table lists the plugin that you can use to configure data enrichment:
Plugin Name
Type
Service that the plugin uses
Application Integration-based Enrichment
Enrichment
Application Integration
Data Quality-based Transformation
Transformation
Data Quality
Title Case
Transformation
MDM SaaS
Concatenate
Transformation
MDM SaaS
Concatenate with Spaces
Transformation
MDM SaaS
Left Trim
Transformation
MDM SaaS
Lowercase
Transformation
MDM SaaS
Replace
Transformation
MDM SaaS
Right Trim
Transformation
MDM SaaS
Uppercase
Transformation
MDM SaaS
Note:
You can't create rule associations that use MDM SaaS transformation plugins. However, you can only use predefined data enhancement rules to create rule associations. If you want to run rule associations even if all input fields are empty, you can create rule associations with transformation plugins.
Application Integration-based Enrichment plugin
To enrich records with data from external data providers, use the Application Integration-based Enrichment plugin and configure data enrichment.
When a rule association with a data enhancement rule that uses this plugin is triggered, the input fields are sent to an Application Integration process, which connects to an external data provider. When the data provider returns data for enrichment, you can automatically enrich or assign records to a hierarchy. You can also display the enrichment data as recommendations in business applications.
When you configure data enrichment, you can choose to enrich specific fields of records. For example, you can send a product description to an external data provider and extract the brand name from the description.
You can also add records to hierarchies based on the data from an external data provider. For example, to assign product records to a hierarchy, you can send a product description to an AI-powered external data provider to get relevant product categories. Based on the product categories that the data provider returns and the existing category records, you can either directly assign the records to a hierarchy or present the category records as recommendations to users.
The following table lists the properties of the plugin:
Property
Description
CAI Process Identifier
Identifier of the Application Integration process that the plugin uses.
CAI Process Name
The API name of the process that's specified in the CAI Process Identifier property.
Allow process with non-anonymous access
Indicates whether you can use a process that requires authentication. By default, only processes with anonymous access are allowed. When this property is enabled, you must specify a process that's configured with non-anonymous access. The property set for the selected process must match the property set in the data enhancement rule. For example, when this property is disabled, you can't save the data enhancement rule with a process configured for non-anonymous access. To use Application Integration processes that require authentication, the organization must use JWT authentication type. For more information, see Authentication Properties in the Administrator help.
Run as User
User name under which the Application Integration process runs. You can specify only one user. If the user you specify doesn't have access to the process, the rule association fails with the Exception status. If you don't specify a user, the process uses the credentials of the user who creates or updates a record through the user interface or REST API.
You can't specify a user group in this property. If you configure the process with an allowed user group in Application Integration, you can leave this property blank. If the user who creates or updates records in a business application belongs to the group, the rule association runs.
Accept Threshold
The confidence score above which data from the data provider is automatically accepted and applied. To enable rule associations to enrich records automatically, enter 0 in the Accept Threshold and Reject Threshold fields. To display the information from the data provider as CLAIRE recommendations, specify the accept and reject thresholds with a value greater than 0.
The name of the field that contains the confidence scores from the data provider. To display the confidence scores along with the recommendations in business applications, specify the name of the field. You can get the field name from the Output Fields tab. If you don't specify the name of the field that contains the confidence scores, CLAIRE displays all recommendations without applying the accept and reject thresholds.
Include only new or updated field group entries
Determines whether the input payload includes only new or updated field group entries. To send all entries of a field group to the Application Integration process, disable the property. For example, if you want to ensure that a record has at least one address entry, disable this property so that the validation service can count the entries in the Address section.
Note:
When you enable the option to include only new or updated field group entries in the payload, the associated rule association runs only if users add or update entries for the mapped field groups. It doesn’t run even if users add or update a value only in an input root field without adding or updating the field group entries.
Run the selected process even when all input fields are empty
Indicates whether to run the Application Integration process when all input fields are empty. By default, when all input fields are empty, the status of the rule association is automatically set to successful without running the Application Integration process.
Determining the data enrichment type
You can configure rule associations to automatically enrich records or display enrichment data as recommendations.
When you configure rule associations for Application Integration-based enrichment, choose one of the following enrichment types:
•Automatic enrichment. MDM SaaS applies enrichment data to records without user intervention.
•CLAIRE recommendations. CLAIRE displays enrichment data as suggestions that users can accept or reject based on confidence scores from data providers.
Note:
You can use rule associations that are configured to display CLAIRE recommendations only in objectives for master records. MDM SaaS doesn't display CLAIRE recommendations for source records.
Accept and reject thresholds behavior
To control how CLAIRE handles recommendations from data providers, you can set accept and reject thresholds in a data enhancement rule during data enrichment configuration.
For example, you send a product description to an AI-powered data provider and request brand name suggestions. You set the accept threshold to 90 and the reject threshold to 40. The data provider returns three brand name suggestions with confidence scores of 95, 65, and 20. CLAIRE accepts the suggestion with a score of 95, displays the suggestion with a score of 65 as a recommendation for users to accept or reject, and rejects the suggestion with a score of 20.
The following image shows how the accept and reject thresholds impact the recommendations from a data provider:
The following table describes threshold conditions and their impact on recommendations:
Threshold
Threshold Impact
Accept and reject thresholds are both set to zero
CLAIRE accepts and applies data is automatically.
Confidence score is above the accept threshold
CLAIRE accepts and applies data is automatically.
Confidence score is between the accept and reject thresholds
CLAIRE displays recommendations for users to accept or reject, sorted by confidence score in descending order.
Accept threshold is greater than zero and the provider returns no confidence scores
CLAIRE displays all recommendations.
Rules for recommended enrichment data
Consider the following rules and guidelines when you configure rule associations to recommend enrichment data:
•If a rule association returns one recommendation and it exactly matches the current field value, CLAIRE doesn't display it. The Data Quality Status page in business applications shows the success status for the rule association. For example, you accept CLAIRE recommendations in two records, then merge the records. If the accepted value survives to the master record and the associated rule association returns a matching recommendation, CLAIRE suppresses it.
•If you configure the same field as both input and output fields in a rule association, and the rule association returns the same value as output, CLAIRE displays no recommendation. Also, the Data Quality Status page shows a success status.
•If a rule association returns multiple recommendations and one exactly matches the existing field value, CLAIRE displays only the non-matching recommendations. The Data Quality Status page shows the recommendation made status for the rule associations until the user accepts or rejects one of the remaining recommendations.
•If the response from the data provider contains multiple recommendations for a field group, each recommendation is added to the record as a separate field group entry. However, if the recommendations are for a root field, the value from the last recommendation survives.
•If the data for hierarchy assignment contains multiple recommendations, multiple relationships are created based on the recommendations.
CLAIRE-Based Enrichment plugin
To automatically classify records by assigning them to relevant hierarchies, use the CLAIRE-Based Enrichment plugin.
You can configure the plugin with details, such as the business entity to classify, the hierarchy to use for classification, and the relationship type. When you save the objective, CLAIRE indexes the hierarchy associated with the objective.
When users prompt CLAIRE Copilot to classify records in business applications, the objectives configured with this plugin are triggered. The product experience agent in CLAIRE Copilot recommends the hierarchy nodes to which the record can be assigned with confidence scores. If the confidence score in a recommendation matches the accept threshold specified in the data enhancement rule, the record is automatically assigned to the recommended hierarchy node.
Note:
If a user prompts CLAIRE Copilot to classify records before CLAIRE indexes the hierarchy, the agent can't classify the record. Also, the product experience agent can run only those objectives with hierarchies that are processed by a process hierarchies job.
The following table lists the properties of the CLAIRE-Based Enrichment plugin:
Property
Description
Hierarchy Model
Internal ID of the hierarchy model associated with the hierarchy to which you want to assign records.
Hierarchy model must have the searchable property enabled. The hierarchy model must not contain cyclic relationships.
Hierarchy
Business ID of the hierarchy to which you want to assign records.
Note:
To get the business ID of a hierarchy, open the hierarchy in a business application, expand System Fields, and copy its business ID.
Business Entity to Classify
Business entity of records that you want to assign to a hierarchy.
The specified business entity must be the business entity for which you configure the corresponding rule association. It must also be the business entity from which the relationship that you specify begins. For example, if you want to assign Item records to Category records in a hierarchy, specify Item as the business entity to classify.
Relationship Type
Relationship type in which the business entity to classify participates.
The relationship type must belong to the hierarchy model that you specify. For example, specify p360_item_to_p360_category if you want to add the Item records to Category records in a hierarchy.
Accept Threshold
Confidence score above which a classification recommendation is automatically accepted and applied.
If the agent recommends multiple hierarchy nodes with confidence scores above the accept threshold, the record is assigned to all those nodes.
To apply uppercase to the first letter followed by lowercase, use the Title Case plugin.
MDM SaaS includes the Title Case predefined data enhancement rule. Instead of creating a new data enhancement rule with the Title Case plugin, you can use the predefined rule data enhancement rule that contains an input and output field.
You can map the input and output fields to the required business entity fields.
For example, you can transform the product name business entity field value to title case format. To transform the field value to title case, create a rule association by using the Title Case predefined data enhancement rule. You can map the input field of the data enhancement rule to the product name business entity field and the output field of the data enhancement rule to the product name business entity field. When you enter the value of the product name business entity field as oneplus, MDM SaaS transforms the input value to Oneplus.
If you want to run the rule association even if all input fields are empty, you must create a data enhancement rule that uses the Title Case plugin.
The following table describes the properties of the Title Case plugin:
Property
Description
Run rule associations even if all input fields are empty
Indicates whether to run the rule association even if none of the input fields contain any value.
Concatenate
To concatenate two or more strings without spaces, use the Concatenate plugin.
You can select the predefined Concatenate without Spaces data enhancement rule to concatenate values from two input field without spaces between them. The predefined Concatenate without Spaces data enhancement rule contains two input fields, such as Field 1 and Field 2 of text data type. You can map the corresponding business entity fields to the input and output business entity fields.
By default, the predefined Concatenate without Spaces data enhancement rule contains one output field. MDM SaaS concatenates the data in the two business entity input fields and returns the output to the mapped business entity field.
For example, to concatenate the first name and last name fields and return the output to the username field, map the two business entity fields to the input fields. You can map the output field to the username business entity field.
If you want to run the rule association even if all input fields are empty, you must create a data enhancement rule with the Concatenate without Spaces plugin.
The following table describes the properties of the Concatenate without Spaces plugin:
Property
Description
Run rule associations even if all input fields are empty
Indicates whether to run the rule association even if none of the input fields contain any value.
Number of Input fields
Total number of input field values that you want to concatenate without spaces.
When you configure a basic rule association with the Concatenate without Spaces function, MDM SaaS creates an equivalent data enhancement rule. If you update the rule association or configure another rule association with similar configuration, MDM SaaS overwrites the existing data enhancement rule.
If you delete the data enhancement rule, MDM SaaS doesn't restore the data enhancement rule and you can no longer create another rule association with the same configuration.
Concatenate with Spaces
To concatenate two or more strings with spaces between them, use the Concatenate with Spaces plugin.
MDM SaaS includes two predefined data enhancement rules, such as Concatenate with Spaces and Concatenate Three Values with Spaces. The Concatenate with Spaces rule association concatenates values from two input fields with spaces between them. However, the Concatenate Three Values with Spaces rule association concatenates values from three input fields with spaces between them.
The predefined Concatenate Three Values with Spaces data enhancement rule contains the following iput fields of the text data type:
•Field1
•Field2
•Field3
For example, to concatenate values of the first name, middle name, and last name fields and return the output to the full name field, map the input fields to the first name, middle name, and last name business entity fields. You can then map the output field of the data enhancement rule to the full name business entity field.
If you want to run the rule association even if all input fields are empty, create a data enhancement rule with the Concatenate with Spaces plugin.
The following table describes the properties of the Concatenate with Spaces plugin:
Property
Description
Run rule associations even if all input fields are empty
Indicates whether to run the rule association even if none of the input fields contain any value.
Number of Input fields
Total number of input field values that you want to concatenate with spaces.
You can use the Concatenate with Spaces plugin and create data enhancement rules based on the number of input fields.
When you configure a basic rule association with the Concatenate with Spaces function, MDM SaaS creates an equivalent data enhancement rule. If you update the rule association or configure another rule association with similar configuration, MDM SaaS overwrites the existing data enhancement rule. You can view the predefined data enhancement rule on the Explore page.
If you delete the data enhancement rule, MDM SaaS doesn't restore the data enhancement rule and you can no longer create another rule association with the same configuration.
Data Quality - Transformation
To use the rule specification from Data Quality for transforming input data, use the Data Quality - Transformation plugin.
Based on the rule logic configured in the rule specification in Data Quality, MDM SaaS transforms the data.
The following table describes the properties of the Data Quality - Transformation plugin:
Property
Description
Rule Specification
Rule specification configured in Data Quality.
Run rule associations even if all input fields are empty
Indicates whether to run the rule association even if none of the input fields contain any value.
You can view input fields that are defined in rule specifications in Data Quality and map the business entity fields to it. The predefined output field is the primary rule set that displays the output of the rule association.
Left Trim
To remove spaces from the beginning of a string, use the Left Trim plugin.
MDM SaaS includes the Left Trim predefined data enhancement rule. The predefined Left Trim data enhancement rule uses an input field and an output field. You can map the corresponding business entity fields to the input and output fields.
For example, to remove the leading space in the first name " John", map the first name business entity field to the input field. You can map the output field to the first name business entity field. When the rule association runs, it removes the leading space from the value and returns the output as "John".
If you want to run the rule association even if all input fields are empty, you must create a data enhancement rule with the Left Trim plugin.
The following table describes the properties of the Left Trim plugin:
Property
Description
Run rule associations even if all input fields are empty.
Indicates whether to run the rule association even if none of the input fields contain any value.
Lowercase
To convert uppercase string to lowercase, use the Lowercase plugin.
MDM SaaS includes the Lowercase predefined data enhancement rule. The predefined Lowercase data enhancement rule uses an input and an output field. You can map the corresponding business entity fields to the input and output fields.
For example, to convert the last name business entity field value to lowercase, map the last name business entity field to the input field. You can map the output field to the last name business entity field. When the rule associations runs, it transforms the last name to lowercase and returns the output.
If you want to run the rule association even if all input fields are empty, you must create a data enhancement rule with the Lowercase plugin.
The following table describes the properties of the Lowercase plugin:
Property
Description
Run rule associations even if all input fields are empty.
Indicates whether to run the rule association even if none of the input fields contain any value.
Replace
To replace a character set in a string with another character set, use the Replace plugin.
MDM SaaS includes the Replace predefined data enhancement rule.
The predefined Replace data enhancement rule contains the following input fields of the text data type:
•Input
•Old String
•New String
You can map the corresponding business entity fields to the input and output fields.
If you want to run the rule association even if all input fields are empty, you must create a data enhancement rule with the Replace plugin.
The following table describes the properties of the Replace plugin:
Property
Description
Run rule associations even if all input fields are empty.
Indicates whether to run the rule association even if none of the input fields contain any value.
Case sensitive
Specifies whether to consider case sensitivity when validating input values.
Right Trim
To remove spaces at the end of a string, use the Right Trim plugin.
MDM SaaS includes the Right Trim predefined data enhancement rule. The predefined Right Trim data enhancement rule uses an input and an output field of the text data type. You can map the corresponding business entity fields to the input and output fields.
For example, to remove trailing spaces from the employee ID business entity field, map the employee ID business entity field to the input field. You can map the output field to the employee ID business entity field. When the rule associations runs, it removes the trailing spaces from the employee ID business entity field.
If you want to run the rule associations even if all input fields are empty, create a data enhancement rule with the Right Trim plugin.
The following table describes the properties of the Right Trim plugin:
Property
Description
Run rule associations even if all input fields are empty.
Indicates whether to run the rule association even if none of the input fields contain any value.
Uppercase
To convert lowercase string to uppercase, use the Uppercase plugin.
MDM SaaS includes the Uppercase predefined data enhancement rule. The predefined Uppercase data enhancement rule uses an input and an output field of the text data type. You can map the corresponding business entity fields to the input and output fields.
For example, to transform the value of the first name business entity field to uppercase, map the first name business entity field to the input field. You can map the output field to the first name business entity field. When the rule associations runs, it transforms the value of the first name business entity field to uppercase.
If you want to run the rule association even if all input fields are empty, create a data enhancement rule with the Uppercase plugin.
The following table describes the properties of the Uppercase plugin:
Property
Description
Run rule associations even if all input fields are empty.
Indicates whether to run the rule association even if none of the input fields contain any value.
