DOCUMENTS API Help contains at least one link to this topic and mentions this topic by name.
Production task specifications tell the program how to process documents for a particular solution. Production tasks can contain one or more activities that perform only a part of the total process, or they can contain all of the activities needed to perform the entire process.
How you set up production tasks depends on your requirements and workflow. Production tasks can be performed automatically, manually, or both. The collective result of all production tasks determines the flow of documents through the system.
Although it is possible to use one production task to completely process documents from input through to output, you will most likely want and need to employ multiple production tasks.
:
The following setup is a general recommendation for larger productions systems:
|
Run on all scanning workstations. |
|
|
Run together on a server as Windows Services. |
|
|
Run on all workstations where operators will inspect documents. |
|
|
Run on a server as a Windows Service. |
|
|
Run on all workstations where operators will verify documents. |
|
|
Run on a server as a Windows Service. |
The total number of production tasks depends on how many operators carry out more than one production activity.
A production task is used to scan, enhance, and sort the documents (normally done by a scan operator). Scanning is done manually, and sorting is automatic.
Another production task is used to verify the documents (normally done by a verifier operator).
If the same person does the scanning and the verifying, the two activities can be included in one production task. Then the production task must also include the Inspect and Extract activities.
Production as a service: Overview