You can create rule associations to validate field values. You can also perform cross-section validations.
For example, if a record includes a supplier name, you can check whether the record also contains the supplier contact details.
To set business logic for validations, you can create data enhancement rules with the validation plugins and use them in rule associations. A rule association configured with a validation plugin validates whether data matches the specified condition.
When you configure validations, you can choose to downgrade the trust scores of fields that fail validations by specifying the percentage of trust score to downgrade. To display validation errors in records, you can also configure error messages by specifying the error severity. For more information about how the error severity works with the option to reject records with validation errors, see Rejecting records with validation errors.
The following table lists the plugin that you can use for validations:
Plugin Name
Service that the plugin uses
Can connect to external data provider?
Application Integration-based Validation
Application Integration
Yes
Note: Validation plugins don't return any output fields. They return the results of the validation along with the names of the fields that fail validation.
Application Integration-based Validation plugin
To validate data using an external data provider, use the Application Integration-based Validation plugin.
This plugin uses an Application Integration process to orchestrate data validation. For more information about creating a process for Application Integration-based validation, see Payload formats for Application Integration-based validation.
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.