Using various job descriptions, you can adjust how you want to work. You can work with different groups of form definitions during different parts of the production process, as shown in the example below.
Note that even though each job description file includes instructions for all four production modules, it is not necessary to use one job description for all production modules. To illustrate this, the scenario described below has Job description file "A" being used only for Scan and Transfer data. For Interpret and Verify, FormDef1 is processed using the instructions saved in job description files "D" and "E".
|
Scan job "A.job" |
Scan job "B.job" |
Scan job "C.job" |
The form definitions are divided up because (for example) the forms are presorted before scanning or because the form definitions are based on incompatible scanner settings.
|
Interpret job "D.job" |
All of the form definitions are included in one job description because no user intervention is required during interpretation.
|
Verify job "E.job" |
Verify job "B.job" |
Verify job "F.job" |
Form definitions are grouped according to specific similarities that make them appropriate to process together.
|
Transfer job "A.job" |
Transfer job "B.job" |
Transfer job "C.job" |
This is the same configuration as the one used for scanning. Putting only one form definition in each Transfer job description results in a separate output file for each type of form.
Managing production through job descriptions
Job lists: lists of jobs that run automatically
Interpret job description settings