Documentation Center

Steps that Appear in All Workflows

WorldServer contains predefined steps that have special meaning to any workflow:
  • Start step — Every workflow contains exactly one Start step. All workflows begin at the Start step, and the Start step must have exactly one transition out of it named Start.
  • Finish step — Every workflow contains exactly one Finish step. The Finish step must have at least one transition into it and can have no transitions out. All workflows end at the Finish step. A task that is moving through a workflow is complete when it reaches the Finish step.
  • Cancel step — Every workflow contains a Cancel step, which allows the workflow to run a specified automatic action in the event that a task is canceled by a user.

    By default, the Cancel step uses the None automatic action which does nothing. You can assign a different automatic action to the step. For example, if 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 the task is canceled.

    After the automatic action assigned to the Cancel step runs, the task goes directly to the Finish step. The Cancel step does not support explicit transitions; there cannot be any explicit transitions into or out of the Cancel step. Implicitly, there is a transition from the Cancel step to the Finish step and from every step in the system to the Cancel step (in the event of cancellation).

    Cancel step automatic actions that error out are put into the Auto Error state like errors from all other automatic actions. Administrators will receive notifications when Cancel automatic actions have encountered a problem, and they can redo the Cancel automatic action as many times as desired until the issues have been resolved and the automatic action has been successfully processed and the task has been canceled.