Kofax Getting Started with Ascent Xtrata Pro - Manual (Page 244)

Set Up Validation
Ascent Xtrata Pro User's Guide 225
Sequence of Validation Rules
First, all single-field validation rules are processed (including rules that are inherited
from the parent document class). Then, all table validation rules for the table are
processed row by row. Finally, all multi-field validation rules are processed.
A validation rule is ignored if the dependent field formatter or a previously
processed rule has failed.
Validation rules can be inherited from parent classes or passed on to derived classes.
An inherited validation rule can be changed in derived classes.
Validation Sequence
The following figure shows the validation process sequence, which is the order in
which the validation checks occur. After extraction, the field formatter and then the
validation rules are processed for each field as defined.
The arrows in the figure show how the field state may change during validation
checks. For example, a field formatter can either keep the current state of the field or
change a “valid” field state to “invalid,” but it cannot change an invalid field state to
valid. A validation rule can only change a field’s state from invalid to valid, when the
check box “Make uncertain results valid” is selected.
Figure 5-8. Validation Sequence and Possible Field State Changes
Validation Forms
Validation forms can be defined for every class. Derived classes inherit the form from
their parent. The Project panel can be customized to include a column for showing
whether a validation form is defined for a given class. (Select