Conditions are used in transitions, (local) final actions after exceeded waiting time of states and in (global) final actions after reaching a final state.

The conditions are considered to be fulfilled if the specified function chain evaluates to true. Note: If necessary, see the notes on implicit type conversion for data type Boolean in section Data Types.

If no functions are specified in the conditions, the conditions are considered to be fulfilled .

images/download/attachments/85267900/cc5.png

(1) The created function chain (as you already know it from profiles).

(2) Here you can display a diagram of the function chain.

(3) The specified function chain (1) can be tested (to true or false). If variables are used in function parameters, only workflow variables can be selected there. You can set any values for these under (4), which will then not only apply to the test but will also be adopted in the Variables area.

Best Practice

Even though you can do a lot with the functions available here, we recommend that you use them for queries only. Executing functions should be limited to actions, if possible. This increases the readability of workflow diagrams (especially larger ones) and makes workflow logs more comprehensible.

Workflow functions should also not be used here. An exception would be the functions log workflow message(a) and workflow exists(a).