In the two group boxes on the Verify tab, you select which form statuses, field statuses and/or field categories you want to verify in a job. In most cases, this is a fairly straightforward process, and it is sufficient if you understand field statuses.
If you leave all the default statuses selected, all of the usual verification work for your forms is included in the job description.
If you work with high volumes or have more than one workstation, you might want to divide the verification tasks into different stages by defining different jobs for the same forms.
For example, you can process interpretation errors first, then process validation errors in another step and type form/field complements (which have the status Incomplete) in still another. If your organization has more than one Verify module, you can assign different verify processes to different workers, with high quality and efficiency as a result.
If you do this, use the status list under Field to choose which individual statuses you want to process, and do not deselect any statuses under Form.
If you divide your verification tasks among two or more jobs, process lower statuses before higher statuses – that is, worse errors before less serious ones. This is because a field or form with a low status can also contain errors of a higher status.
Example:
Field1 has the status Validation error but also fits the criteria for Incomplete. After you correct the validation error, Field1 receives the new, higher status Incomplete. If you process a Verify job containing Incomplete status before another with Validation error, then your process would miss the Field1, because Field1 would not receive the Incomplete status until after the Validation error was corrected.
The more jobs you divide your verification work into, the more important it becomes that you understand what each status means when applied to a field and to a form. Be sure you have a clear understanding of:
Statuses – read the Overview
Enable buffering in the Verify job description
Use FORMS’ Verify view designer
Change the verification order of the fields in the form definition
Use queues to branch specific forms, sets, or batches off from the main production flow