Workflow Designer
General Structure of a Workflow
In the Workflow Designer, workflows (see general explanation there) are represented as flowcharts.
Such a flowchart must have exactly one start state (simply the first state, the entry point), at least one transition (to a subsequent state) and at least one end state (no outgoing transition).
Thus, any number of states, transitions, and end states are allowed, but only exactly one start state.
Inserting States
A newly created workflow already contains a start state (1).
Further states can be inserted via the context menu. Note: As long as a state (apart from the start state) has no outgoing transition, it automatically becomes an end state (see next screenshot). Once an outgoing transition is present, the end state automatically becomes a normal state (see screenshot after next).
The different types of states (to create automated, interactive and hybrid workflows) are described in section State. You will also find a description of how to insert forms.
Note: The selection of elements in the Workflow Designer is only possible by left-clicking.
Inserting Transitions
Add another state.
A transition (see details there) can be inserted by dragging the blue marker (2) of a state to another state. Alternatively, you can use the context menu of a state for this purpose.
You can insert at most one transition from one state to a certain other state, however, transitions to any number of subsequent states are allowed.
A state cannot have a transition to itself. However, a subsequent state can have a transition back to this state. Transitions back to the start state can also be inserted.
Inserting Actions
For your workflow to actually do something, actions must be defined.
These actions (profiles, other workflows, ASM entries, ETL entries) can be executed either in transitions (4), in states (5) as (local) final actions after an exceeded waiting time, or as (global) final actions after any end state has been reached (6).
Sequence of a Workflow Job
|
Job start |
If a workflow job is started, it is initially in the start state. |
|
State change/actions |
If a workflow job changes to a state (when the workflow job is started or after a successfully executed transition of a predecessor state), it remains in this state until a triggered transition check finds a valid transition. The workflow job then changes to the subsequent state connected with this transition. In addition, actions may be executed. |
|
Job end |
A workflow job is terminated when an end state has been reached or when the set waiting time in a state has been exceeded. In addition, a workflow job can also be cancelled prematurely. |
|
(External) |
Workflow jobs can also be controlled from outside the actual workflow environment via the Control Center, with workflow functions and via REST (HTTP). |