“Store” and “Queue to” Properties of a Task Definition in Datacap Taskmaster

“Store” and “Queue to” Properties of a Task Definition 

in Data cap Taskmaster

Abstract

The Store and Queue to properties of a Task Definition determine which operators and workstations 
can process individual batches. (Chapter 5 reviews the impact of these settings.) 
The Store property looks forward; the Queue to property looks backwards. 
In the Workflow tab of the Taskmaster Administrator, the Queue to and Store fields are drop-down lists 
that display their values when you click once on the field. The following table lists and explains these options. 

Store…	Queueueue…	Explanation
“None” or “Station ID and User ID”	Anywhere, Anytime	The Anywhere, Anytime value allows any operator and Station ID to process batches in the task’s queue – and thus overrides the Station ID and User value assigned to an earlier task’s Store property.
“Station ID” or “Station ID and User ID”	“by Station”	The task can process only those batches previously processed from the same workstation ID.
“UserID” or “Station ID and User ID”	“by User”	The task can process only those batches previously processed by the same operator.

“Station ID” or “Station ID and User ID”	“by Other Station”	The task can process only those batches previously processed from a different workstation ID.
“Station ID and User ID”	“by Station and User”	The task can process only those batches previously processed by the same operator, from the same workstation ID.
“Station ID and User ID”	“by Station and other User”	The task can process only those batches previously processed by a different operator, from the same workstation ID.
“Station ID and User ID”	“by User and Other Station ”	The task can process only those batches previously processed by the same operator, from a different workstation ID.
“Station ID and User ID”	“by other Station and other User ID”	The task can process only those batches previously processed by a different operator, from a different workstation ID.

Standard Processing Actions

A Task Definition that includes a processing condition must specify the action the task is to take when it encounters the condition.

The actions include:

None. This is the default, temporary setting you can use as you assemble the task’s response: it makes certain that there is no impact on the processing of a batch.

Branch. This action diverts the batch that the task is processing from the parent job to the task(s) of a child job. When the child job is finished, the batch returns to the parent job. Alert! A workflow can contain a child job hierarchy in which a task in a child job branches to a child job on a lower tier. In this situation, the first child job becomes the parent to the second child job.

�� Most conditions lead to the Branch action.

Jump. This action is a processing shortcut that skips one or more tasks in the workflow, and places the batch in a more advanced position, or in an earlier position. The jump action uses a value in the Steps property to indicate the next task, and does not involve the use of a child job.

Split: The Split action splits one or more documents from the current batch. The task in the parent job creates a sub-batch, adds the document(s) to it and sends the sub-batch to a child job for special processing. While the child job takes care of the sub-batch, the parent job processes the remaining documents in the batch. The child job does not return the sub-batch to the parent job when processing is complete.

Stop: This action terminates Taskmaster’s processing of the batch.

Hub: The Hub action combines features of the Branch and Split actions. Hub splits documents from the batch, adds them to sub-batches, and delivers the sub-batches to various child jobs. When the child jobs have processed the sub-batches, they return to the parent jobs.