As soon as the workflow starts, all job items from a content group are available to the first user of the workflow.

Example:

In this example, 'Ringo Recipe' will see a job in his 'Jobs' tab containing all 23 items that are involved in this translation job.

No other user will, at this point, see a job in their jobs queue. This is because none of the other workflow steps contain any active content yet.

Individual job items can be marked as 'Done' (or 'Accepted' in a review step) and moved independently to the next workflow step. It is not necessary for all items to be marked as 'Done' (or 'Accepted') for the following workflow step to be started.

Each individual job item is only 'active' in one workflow step at a time. An item can only be edited by a user if the item is 'active' in that user's workflow step.

The entire document is always rendered. Therefore users can view content that is not 'active' in their step, but they cannot edit that content.

Example:

In the example above, Ringo Recipe has translated and committed 58 items to the 'Internal Review' step. Therefore, the 'Internal Review' workflow step contains 58 'active' items for George Recipe to edit/review. While Ringo Recipe can still see those 58 items as rendered in the document, he can no longer edit those items as they are no longer 'active' in the 'Edit' step. Similarly, George Recipe can see but cannot edit the 37 items that are still 'active' in the 'Edit' workflow step.

NOTE:

In the above example, a workflow action in the 'Start' field for the 'Internal Review' workflow step would have been executed. However, a workflow action in the 'Finished' field of the 'Edit' workflow step would not yet have been executed, as that step is only 61% complete.

NOTE:

A workflow may consist of one 'Edit/Translation' workflow step and as many 'Review' workflow steps as required. If no user is assigned to a workflow step, that step is ignored.

The percentage completion of each individual workflow step is calculated using the number of 'active' job items at that workflow step.

Because the 'Internal Review' step is now at 100% completion, a workflow action in the 'Finished' field of that step would be executed. It does not matter that 37 job items have yet to be committed from the 'Edit' workflow step.

In the example above:

1. All 58 'active' items at the 'Internal Review' workflow step are marked as accepted and committed to the 'External Review' workflow step. Because this workflow step contains no more 'active' items, the job associated with it will disappear from the 'Jobs' tab of George Recipe.
2. The 58 job items are now in the 'External Review' step. This means that the 'External Review' step is now active, and Paul Recipe will see the job associated with it in his 'Jobs' tab.

Job items can be rejected back to a previous workflow step. The rejected job items are switched back to 'New' in that target workflow step.

In this example above:

1. Initially, all 95 job items (100% of all job items) are at the 'External Review' workflow step. Paul Recipe then starts to review the content, accepting and rejecting items as follows.
2. 20 items are accepted and committed to the 'Final Approval' step. Therefore, the 'Final Approval' step has been started for John Recipe, and contains 20 'active' items to review.
3. 10 items are rejected back to the 'Internal Review' step. Therefore, the 'Internal Review' step has been reactivated with 10 'active' items. George Recipe must work on these items and commit them to the 'External Review' step once again.
4. 10 items are rejected back to the 'Edit Step' for retranslation. Therefore, the 'Edit Step' has been reactivated with 10 'active' items. Ringo Recipe must retranslate these items and commit them to the 'Internal Review' step, where George Recipe will need to review them again.
5. 55 items have not yet been worked on by Paul Recipe. Therefore, these items remain 'active' in the 'External Review' workflow step.

NOTE:

When workflow steps are reactivated, a workflow action in the 'Start' field will be executed again (e.g. an email notification).

NOTE:

Job items cannot skip steps on their way forwards through a workflow. Therefore, any rejected job items must pass through all the following steps in the workflow once more.

By default, any rejected item will be sent back to the 'Edit/Translation Step'. The user can manually choose another target workflow step, if desired.

Depending on the user privileges, notes can be added to clarify the reason for rejection of the job item.

1. If multiple previous workflow steps exist within a workflow, the reviewer can reject an item back to any previous step using this drop-down menu (the default is the 'Edit/Translation' step).
2. A reason for the rejection of the job item can be entered in the 'Reason for Rejection' field. This reason will be added as a note in the document.

The overall progress of the entire job is shown in the 'Steps Completion' workflow step progress bar. The progress shown here is the same as the overall progress shown for the job in the 'Projects' tab.

NOTE:

Any action that should only be executed when the entire job has been completed (e.g. 'commit translations') should be added to the 'Steps Completion' step (i.e. not the 'Finished' field of the final workflow step).