The Workflow tab defines workflows,
jobs, and tasks for the application. Tasks on the Workflow tab are
linked to task profiles (that are created in Datacap Studio).
New
Click New to
create a task, job, or workflow:
- To create a task, select the parent job and click New.
- To create a job, select the parent workflow and click New.
- To create a workflow, ensure that no items are selected and click New.
After creating the item, specify the details in the Selected
task/job/workflow details pane.
Copy
Makes a copy of the selected item and
names it Copy of <item>.
You can change the name and details in the Selected task/job/workflow
details pane.
^ (up arrow)
Moves the selected item up
the list.
v (down arrow)
Moves
the selected item down the list.
Remove
Removes the selected item.
Work list
Displays all workflows, jobs,
tasks, and conditions that are defined for the current application.
To change the settings for an item, select the item to open the Selected
task/job/workflow/condition details pane in which you
can make the changes.
Selected task details
Select a task to open
the Selected task details pane and change the settings for the selected
task. Click Apply after making changes.
- Name
- Displays the task name.
- Description
- Displays the task description.
- Mode
- Each task must be linked to a mode. The mode specifies the behavior
of the task. The drop-down menu displays the modes that are available
for selection and includes:
- Queue by
- Determines which combination of user ID and station ID can open
a batch queued for this task. Options are:
- None: Any user on any station can open
the batch (default setting).
- Station: Only the station that stored the
batch can open the batch.
- User: Only the user that stored the batch
can open the batch.
- Other Station: The station that stored
the batch cannot open the batch.
- Other User: The user that stored the batch
cannot open the batch.
- Station and User: Only the station and
user that stored the batch can open the batch.
- Station and Other User: Only a different
user on the station that stored the batch can open the batch.
- User and Other Station: Only the same user
on a different station can open the batch.
- Other Station and Other User: Only a different
user on a different station can open the batch.
Important: Changing the Queue by setting
does not affect batches that are already queued.
- Store
- Determines which combination of station ID and user ID is stored
with the batch upon completion of this task. Options are:
- None: No user ID or station ID is stored
(default setting).
- Station ID: Stores the station ID with
the batch.
- User ID: Stores the user ID with the batch.
- Station ID and User ID: Stores the station
ID and the user ID with the batch.
Parameters
The Parameters section for a
selected task allows you to specify the program to use with the task.
Click Apply after making changes. These are
the programs that you can choose from the Program drop-down
menu:
- Multiple
- Select this program if the task can be run in the background by
Rulerunner, in the Taskmaster Web client,
or in an application client (such as DotScan, Fastdoc, or DotEdit).
- DotScan
- Select this program if the task is run exclusively in Taskmaster DotScan.
- Scancl.aspx
- Select this program for a scan task that is run from Taskmaster Web.
- VScancl.aspx
- Select this program for a virtual scan task (file import) that
is run from Taskmaster Web.
- UplBFcl.aspx
- Select this program for an Upload task that is required after
remote scanning in Taskmaster Web.
- Click Setup (or, if this is a new task,
click Create Setup and then Setup)
to open the task.set.xml Webpage dialog to modify
options, including:
- Upload pause: Determines the time delay
between uploading of images.
- Maximum upload size: Determines the maximum
size of an upload.
- Pickup.aspx
- Select this program for a batch creation task in Taskmaster Web that involves different
types of documents, such as graphics, bar codes, text, and forms.
- Click Setup (or, if this is a new task,
click Create Setup and then Setup)
to open the task.set.xml Webpage dialog to modify
options, including:
- Thumbnail scale
- Files per batch
- ProtoID.aspx
- Select this program for a manual page identification task in Taskmaster Web that includes reordering
images, inserting new images, flagging, image review, image rotation,
and application of document integrity rules and RRS rules.
- Click Setup (or, if this is a new task,
click Create Setup and then Setup)
to open the task.set.xml Webpage dialog to modify
options, including:
- Validation Statuses
- Task profile
- Page ID: This includes the types of pages
to highlight, special variable values, thumbnail scale, enabling document
integrity rules, and the type of page to use when inserting a new
page.
- Restruct.aspx
- Select this program for a manual document assembly task in Taskmaster Web. Document assembly
is usually an automatic process that runs in the background. However,
in some cases, the automatic assembly task does not correctly identify
page types. For these occasions of misidentification during document
assembly, you can use Restruct.aspx to force manual identification
of page types.
- To configure a task to use Restruct.aspx:
- Select the task and click Setup (or, if
this is a new task, click Create Setup and
then Setup) to open the task.set.xml
Webpage dialog
- Scroll down to the DCO Tree View section.
- Under Display Variables, enter 1,setup for
the Props for var TYPE value.
(The default is 0,setup.)
- Click Save.
Tip: The fields in the task.set.xml
Webpage dialog include tool tips that provide guidance about acceptable
values that you can enter.
- aIndex.aspx
- Select this program for a manual document assembly task in Taskmaster Web, that includes page
identification, document creation, indexing, data validation, anchor
setting, image reordering and rotation, document integrity validation,
and double-blind or multi-pass data entry.
- Click Setup (or, if this is a new task,
click Create Setup and then Setup)
to open the task.set.xml Webpage dialog to modify
options, including:
- Page Statuses
- Document startup: Specify whether to load
all data files and image files when the tasks begins processing.
- Field Statuses
- Alternative or blind texts: These include
alternative text index, blind confirmation index, and displaying other
alternative texts.
- Task profile and alternate task profiles
- Index: These include read-only field statuses,
enabling local processing when there is no firewall between Taskmaster Web and Taskmaster, hiding document
types, and specifying a template folder.
Tip: The fields in the task.set.xml
Webpage dialog include tool tips that provide guidance about acceptable
values that you can enter.
- Rulerunner
- Select this program for background tasks that are run exclusively
by Rulerunner.
- DotEdit
- Select this program for tasks that are exclusively completed in Taskmaster DotEdit.
- FastDoc
- Select this program for tasks that are exclusively completed in FastDoc.
- aVerify.aspx
- Select this program for data validation and verification tasks
that are completed in Taskmaster Web.
- Click Setup (or, if this is a new task,
click Create Setup and then Setup)
to open the task.set.xml Webpage dialog to modify
options, including:
- Page Statuses
- Document startup: Specify whether to load
all data files and image files when the tasks begins processing.
- Field Statuses
- Task profile and alternate task profiles
Tip: The fields in the task.set.xml
Webpage dialog include tool tips that provide guidance about acceptable
values that you can enter.
- ImgEnter.aspx
- Select this program for formless data verification tasks that
are completed in Taskmaster Web.
- Verifine.aspx
- Select this program for data verification tasks that use custom
forms and are completed in Taskmaster Web.
See the topic Creating and using custom web pages in the IBM® Datacap
Taskmaster Capture information center
for details about using Verifine.aspx.
Selected job details
Use the Selected
job details pane to change the settings for the selected
job. Click Save after making changes.
- Name
- Displays the job name.
- Description
- Displays the job description.
- Priority
- Determines the priority of batches created using this job (1 is
the highest priority and 10 is the lowest priority). If two batches
of different priority are pending for the same task, Taskmaster processes
the batch with the highest priority first. Changing this setting does
not affect batches that are already queued.
Selected workflow details
Use [Selected
workflow details] to change the settings for the selected workflow.
Click Save after making changes.
- Name
- Displays the workflow name.
- Description
- Displays the workflow description.
- Program Name
- Always TDCO.Batch.
Selected condition
details
When you select Router as
the Mode for a task, Taskmaster automatically inserts
a Return Conditions key under the Parameters section.
Conditions are used to implement branching and splitting. For example:
- Branching: If a batch fails document integrity
checking, you can route it to a special FixUp task so that an operator
can address the issue and then return the batch to the main workflow.
- Splitting: If a batch contains pages that
meet certain exception criteria, you can split those pages from the
batch and route them to an administrator for special handling.
Applications can raise conditions by using the Task_RaiseCondition
action or the SplitBatch action. (See the action help in Datacap Studio
for details.) For more information and examples, see Developing IBM Datacap
Taskmaster Capture Applications in
the IBM Datacap
Taskmaster Capture information
center.
- Name
- Displays the condition name. The condition name is stored in the task.set.xml file
for the related task. You cannot change the condition name here.
- Spawn Type
- Determines the action taken when the condition is raised:
- not set: Does nothing.
- Branch: Sends the current batch to the
specified job, then returns the batch to the main job.
- Jump: Skips the next <steps> tasks
in the current job workflow.
- Split: Used with the SplitBatch action
to send specific pages from the current batch to another job.
- Stop: Stops processing the batch (status
= "batch stopped").
Important: The action does not actually occur until
the current task completes.
- Child Job
- Specifies the job to which the batch or split portion of the batch
is sent when the condition is raised.
- Parent Status
- Specifies the status assigned to the batch in the main job when
the child job completes (Pending is the default setting).
- Child Status
- Specifies the status assigned to the batch in the child job (Pending
is the default setting).
- Steps
- The purpose of this field varies depending on the Spawn
Type field:
- When used with Jump: The number of workflow
tasks to jump.
- When used with Branch: The return point
after branching (0 = same task, 1 =
next task, and so on).