User Guide > Objects > Alphabetical Listing > Workflow - Execution

Workflow - Execution

Object-Type-Specific Features

When a workflow is activated, all its objects are activated, including the objects of sub-workflows. The system checks whether object scripts should also be processed. The following applies to all objects in which the attribute "Generate at Runtime" is NOT activated: Scripts are processed at the activation time. In all other objects, scripts are processed as soon as the workflow reaches the object and starts it.

The impacts of scripting errors depend on their generation time:

Workflow generation is canceled if a generation error occurs in one of the involved objects that are also generated at this point in time.
If a generation error occurs in an object in which the option Generate at runtime is activated, the object itself is canceled; the workflow still continues.

Workflows can contain objects that should be generated at activation time as well as objects that should be generated at runtime. If the attribute "Generate at runtime" is set in most of the Workflow objects, the workflow is activated faster.

Monitoring or modifying a workflow

You can view the execution of a workflow in the monitor. Objects are displayed in different colors which indicate the status of the workflow and its individual tasks.

You can also modify a workflow via the monitor. All your modifications are valid for the ongoing execution. The general definitions in the Workflow object remains unchanged.

Stopping the Execution

An activated workflow can be stopped and restarted at any time.

Handling
Right-click in the Activity Window.	Select Stop or Go in the context menu.
Right-click in the monitor of a workflow.	Select Stop or Go in the context menu.

Note for executing workflows:

Theoretically, starting a workflow that includes itself results in an infinite nesting. Practically, a maximum nesting depth of workflows has been defined which prevents such an error.

Blocking condition

You can define particular dependencies and conditions in the properties of workflow tasks (such as an earliest or latest start, or the states of predecessors) so that the relevant task blocks if your definitions are not met. In this case, the task is only blocked within the workflow. The Activity Window displays the task's actual end status.

If a task blocks, the processing of the current branch does not continue as of this objects. Manual interference is required (for example, unblock task, cancel or start next task). The processing of other branches continues. If there are no other branches or if they have already been processed, the workflow obtains the status "Workflow is blocked."