Common workflow steps

A list of workflow steps that you will encounter in every WorldServer workflow that you work with.

Step name	Description
Start	Every workflow contains one Start step—this is usually the first step in the workflow. The Start step can only have one transition to another step.
Finish	Every workflow contains one Finish step—this is usually the last step in the workflow. The Finish step needs to have at least one transition into it and no transitions out of it. Tasks are complete when they reach the Finish step.
Cancel	Every workflow contains one Cancel step, which allows the workflow to run an automatic action of your choice if a user cancels a task. By default, the Cancel step runs the None automatic action, which does nothing, but you can assign it a different automatic action. For example, if the assets are locked in a version control system at the beginning of the translation process, you can set up the Cancel step to run an automatic action that unlocks the assets if someone cancels the task. After the automatic action assigned to the Cancel step runs, the task goes directly to the Finish step. The Cancel step does not support transitions; you cannot create any transitions into it or out of it. As with errors that occur during other automatic actions, the Cancel step automatic actions that lead to errors go to the Auto Error step. Administrators receive notifications when Cancel automatic actions encounter issues and they can redo these automatic actions as many times as needed until the issues are resolved.

Step name

Description

Start

Every workflow contains one Start step—this is usually the first step in the workflow. The Start step can only have one transition to another step.

Finish

Every workflow contains one Finish step—this is usually the last step in the workflow. The Finish step needs to have at least one transition into it and no transitions out of it. Tasks are complete when they reach the Finish step.

Cancel

Every workflow contains one Cancel step, which allows the workflow to run an automatic action of your choice if a user cancels a task.

By default, the Cancel step runs the None automatic action, which does nothing, but you can assign it a different automatic action. For example, if the assets are locked in a version control system at the beginning of the translation process, you can set up the Cancel step to run an automatic action that unlocks the assets if someone cancels the task.

After the automatic action assigned to the Cancel step runs, the task goes directly to the Finish step. The Cancel step does not support transitions; you cannot create any transitions into it or out of it.

As with errors that occur during other automatic actions, the Cancel step automatic actions that lead to errors go to the Auto Error step. Administrators receive notifications when Cancel automatic actions encounter issues and they can redo these automatic actions as many times as needed until the issues are resolved.