Validation rules in Document Automation

With validation rules, you can ensure the accuracy of extracted data across multiple fields in your documents.

You can define various conditions, such as pattern matching or equality checks. When those conditions are met, you can effortlessly take action to flag errors or warnings, clean up or replace values, or set new values.

Enhanced validation rules can be applied on two levels:

Field Rules
Document Rules

Field rules

Field-level rules are designed to create rules specifically for individual fields. These rules contain a condition that is followed by a set of actions to be performed if the condition is met and is implicitly associated with the highlighted field.

Field level validation rules

These rules are processed before document-level validation rules.

Document Rules

A document level rule is associated with a field but can have conditions and actions that are dependent on values of other fields. With these rules, you can build complex structure of conditions that can include several fields and encompass extensive actions. Document level validation rules

Note:

You can select one or more fields where these actions can be applied.
The document rules can be structured with dependencies between fields, and their execution order is crucial. It is important to maintain the sequence.

In the following video, you can observe how validation rules are utilized within documents to enhance the process of data extraction.

<span>Video demonstrates using field-level and document-level rules for validation.</span>

Available conditions and actions


Condition	Action
A condition is expressed as a logical rule that evaluates the state or values of certain fields that must be met for an action to occur. Below is the list of all the available conditions:	An action is associated with an operation that is performed when certain conditions are met. Below is the list of all the available actions:

Automation 360

Validation rules in Document Automation