The Embedded Directive Manager component has the ability to scan multiple routing sheets at one time. This is known as batch scanning.
Multiple documents, separated by routing sheets, are submitted as one scan job during batch scanning. The server will separate the job into its multiple routing components. The Batch Job and the optional Job Count are validated by the server.
Validating a batch job
The batch job will fail if any of the following conditions occur.
-
The first page of the scanned document is not a routing sheet.
-
There is an invalid job count.
- There is an invalid Routing Sheet or a missing embedded directive.
- The Routing sheet is not accompanied by attachments at all times.
-
Consecutive Routing Sheets are not allowed. There must be at least one document in between each routing sheet.
-
The last page of a batch cannot be a Routing Sheet.
Validating a job count
Validating the job count, although optional, is an extremely important measure of quality control. It is the only way to ensure that each individual in the batch receives the correct, intended documents.
To ensure proper separation of batch jobs, the job count is determined by counting the number of Routing Sheets in a valid batch job. You can also enter the number of jobs in the batch when you initiate the scan. That information will be sent to the Message server along with the scanned job. If you specify a job count, the Embedded Directive Manager will verify that the number of routing sheets in the batch match the job count you entered. If they don't match, the batch job will fail.
To validate the job count, specify how many jobs are in a batch by setting the
Using batch scanning with Filescan
Create a control file that contains the following keywords.
-
To enable batch scanning: BATCH TRUE or FALSE
-
To enable batch count verification: BATCH_COUNT number of items in the scan (optional)
About Embedded Directive Manager Component