Split Batch actions

Creates child batches from an existing batch.

The SplitBatch action library separates pages from an existing batch into one or more child batches.

A DCO variable is used to control which pages are split into a child batch. The value of the variable determines which pages are moved to the new child batches. Objects that have this variable will be split based on the value of the variable. Objects that have same variable value will be included in the same child batch. A child batch will be created for each unique value of the variable, if the page is eligible to be split into a child batch. Child batches have the same name as the parent batch with additional two character alpha-decimal suffix such as .01, .02, .0A, ..., up to .ZZ.

For example, if the variable has three unique values on pages that are eligible to be split, then three child batches will be created and named using this pattern:

˂BatchID>.01
˂BatchID>.02
˂BatchID>.03

This hexadecimal numbering for child batches is required by the Datacap Server. Datacap Server creates the batch and queue entries for the child batches after the task is finished, when the split condition is processed. There is a maximum of 1295 child batches.

The values of the specified variable that is used to split the batch are user defined. The action will group based on matching values of the variable, regardless of what they are. Matching is case sensitive.

Only documents objects and unbound pages (pages that are not within a document structure) are eligible to be split into a new batch. Pages that are already placed within in a document structure will not be processed individually, the pages will be as part of their document, not as a separate page. So if a document is configured to be split into a new batch, then all of the child pages for that document will be moved into the new batch.

If a file cannot be accessed while a batch is being split, such as the associated image file is missing or cannot be accessed due to permissions, the parent batch will abort. The batch will need to be reviewed when this condition occurs.