Configuring the Dependencies of a Task in a Workflow

Usually, tasks in Workflows start as soon as their predecessors have finished. However, you can define multiple parameters in their properties that affect the task sequence in the Workflow. In the Dependencies properties tab you define the following parameters that determine whether a task will actually execute:

• Status that the predecessor task must have
• Status conditions that must be met for the task to start
• WHat should happen in case of deviations

To Define Dependency Settings

1. In the Workflow editor, right-click the task, select Properties and open the Dependencies tab.

2. In the Predecessor Tasks section you specify the status that the predecessor task must have so that this task can start executing.

   The table in this section provides the list of predecessors of the selected task and gives an overview of their most important attributes. Not all attributes are displayed, though. If necessary, click the arrow at the right end of the table caption to show additional columns. This screenshot illustrates it:

   (Click to expand)

   

   Tip: You can change the status here, or you can define a Client-wide default status for all tasks in Workflows. You do this in your user settings; This status is then set by default in this table. If you leave the default task status empty on the Settings dialog, it is also empty here. For more information, see Defining the Default Task Status for Workflow Dependencies .

   If the predecessor is an external dependency, the Status column refers to the status of the external dependency and not to the external task. For this reason, only the following status are available:

   • ENDED_OK

   • ENDED_CANCEL

   • ENDED_ESCALATED

   Note: You cannot add to or remove tasks from the table.

3. In the Conditions section you specify when the task will start executing

   • all statuses match, that is, if all the predecessor tasks in the previous table have reached the specified statuses

   • at least one status matches, that is, at least one predecessor ends with the status you specify on the table.

4. In the Status & Latest Time Deviations section you specify what will happen if the status conditions defined here or the latest start/end time conditions specified on the Time tab are not met. These are your options:

   • Skip

     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

     The Workflow blocks at the predecessor task.

     If you have previously selected at least one condition matches and none of the conditions is satisfied, the successor task (not the predecessor!) will block the Workflow. The reason is that there is no specific task that is responsible for the mismatch.

     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

     The task and the Workflow itself are canceled.

5. Optionally, in Execute select an alternative object. If the conditions you have defined sare not met, this object is executed instead.