Default Task Status for Workflow Dependencies

When you design a Workflow, you set properties to its tasks. One of them is the status with which a task must end so that the next task in the Workflow can start. You define this status in the Time & Dependencies task tab in the Workflow Editor. To save time when creating Workflows you can specify that your tasks must have always a specific status before the next task in the Workflow can start. You define this default task status on the Settings dialog. This status is then set by default in the Time & Dependencies tab of the Workflow task and you do not have to select it manually.

By default, the dropdown lists to select the default status on the Settings dialog are empty. This means that if you leave the default task status empty on the Settings dialog, it is also empty in the task Time & Dependencies tab in the Workflow.

To Define the Default Task Status in Workflow Dependencies

  1. Open the dropdown menu at the top right corner of the menu bar and select Settings.
  2. On the Settings dialog open the Process Assembly tab.
  3. In the Dependencies section, select the status you want to set as default for internal and externals tasks.
  4. In the ELSE section, specify what happens if the status conditions are not met.

    • Skip task

      The task is skipped but its Postconditions are executed.

      The final status of the task in this case is 1930 - "ENDED_SKIPPED - Skipped because of WHEN clause."

    • Block task

      The Workflow blocks at the predecessor task.

      Important! Tasks that run in parallel within the Workflow continue processing. The Workflow as a whole is not blocked until all tasks have been executed.

    • Block and send abort signal to parent

      The task is blocked. If there is a superordinate Workflow (parent), a signal is sent that indicates the abnormal end. If this option is set in a Workflow dependency, the parent Workflow remains blocked even after the child task has been unblocked.

    • Abort task

      The task and the Workflow itself are canceled.

  5. In Execute, select a follow-up object. If the conditions are not met, this object is executed instead.

See also: