About Parallel Workflow

Parallel workflow is an option of Task Sequence documents that requires several users to perform the same task simultaneously.

Typically, a parallel workflow is used to assign a group of users to review a document. However, this option is not restricted to a review.

Parallel workflow is specified in the Task Sequence document. Each Job Transition has a check box, Parallel Workflow. If the check box is selected, the transition starts a parallel workflow. The transition must also specify the Job to Start as Job_ReviewParallel.

When a workflow transitions to a parallel workflow step, multiple job tickets are created, with one ticket assigned to each member of the role specified in the Task Audience field. In addition, a parallel workflow container job ticket is created and assigned to the user specified in the Task Owner field. This job ticket allows the Task Owner to monitor the progress of the individual parallel workflow tickets. See Monitoring Parallel Workflow. The Task Audience and Task Owner receive email notification of their tickets.

Before the status of the object can change again, all of the parallel jobs must be completed. Users in the Task Audience can complete their parallel jobs in any of these ways:

Issuing the Process Job command on the job ticket.
Issuing the Change Status command on the object.
From the Astoria Reviewer interface, while viewing the object, select the Complete Review check box, then click Change Status.

Any of these methods displays a dialog allowing the user to provide a job note. When executed, an email is sent to the Task Owner indicating the job ticket was completed.

Once all parallel job tickets are disposed, the Task Owner can issue the Change Status command on the object. If this command is invoked and there are still outstanding parallel tickets, the object's status cannot be changed.