| ... |
... |
@@ -1,3 +1,14 @@ |
|
1 |
+{{figure image="condition-workflow_de.png" clear="h1" width="400"}} |
|
2 |
+ The condtion lets you add a branch to your workflow. Depending on the result of the condition, different actions are performed. You can also add a label to each branch of the condition to improve the recognizability of your workflow configuration. |
|
3 |
+{{/figure}} |
|
4 |
+ |
|
5 |
+{{figure image="condition-settings-simple_de.png" clear="h1" width="400"}} |
|
6 |
+ A simple configuration for a condition. A value is compared against another value. |
|
7 |
+{{/figure}} |
|
8 |
+ |
|
9 |
+{{figure image="condition-settings-advanced_de.png" clear="h1" width="400"}} |
|
10 |
+ You can also make use of more complex conditions. In this case, two individual conitions were defined, named //c1// and //c2//. These two conditions are then joined with a custom connection: //c1 or not c2//. |
|
11 |
+{{/figure}} |
| 1 |
1 |
{{content/}} |
| 2 |
2 |
|
| 3 |
3 |
Control elements of type //Condition (Check value)// can be used to influence the flow of processing depending on form values and other content by using [[Variables>>doc:Formcycle.UserInterface.Variables]]. These elements allow the workflow to be split into two paths depending on whether a configured condition turns out to be true or false. By using multiple conditions in one condition element and nesting conditions, it is possible to implement even complicated workflows. |
