Changes for page Bedingung (Wert prüfen)

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.gru
	1	+XWiki.awa

Content

...	...	@@ -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.
...	...	@@ -37,7 +37,7 @@
37	37
38	38	=== Adding another condition ===
39	39
40		-Under each last condition there is a button //{{ficon name="plus-circle" /}} Add condition//. After the first click on this button, a field is also visible under the first configured condition, in which the [[Link>>|anchor="HLinkingconditions"]] of the conditions can be configured.
	51	+Under each last condition there is a button //{{ficon name="plus-circle" /}} Add condition//. After the first click on this button, a field is also visible under the first configured condition, in which the [[link>>||anchor="HLinkingconditions"]] of the conditions can be configured.
41	41
42	42	=== Deleting conditions ===
43	43
...	...	@@ -75,8 +75,8 @@
75	75	::
76	76	:; false, true
77	77	:: These two constants represent the logical values //false// and //true//.
78		-:; xor, nand, nor, implies, impliedby, equiv und unequiv
79		-:: Represents, in this order, the logical operators [[Kontravalenz>>url:https://de.wikipedia.org/wiki/Kontravalenz]], [[Alternative Verneinung>>url:https://de.wikipedia.org/wiki/NAND-Gatter]], [[Gemeinsame Verneinung>>url:https://de.wikipedia.org/wiki/NOR-Gatter]], [[Materiale Implikation>>url:https://de.wikipedia.org/wiki/Implikation]], [[Gegenläufige Implikation>>url:https://en.wikipedia.org/wiki/Converse_(logic)]], [[Materiale Äquivalenz>>url:https://de.wikipedia.org/wiki/Bikonditional]] und Nicht-Äquivalenz.
	89	+:; xor, nand, nor, implies, impliedby, equiv, unequiv
	90	+:: Represents, in this order, the logical operators [[Exclusive or>>url:https://en.wikipedia.org/wiki/Exclusive_or]], [[Alternative negation>>url:https://en.wikipedia.org/wiki/NAND_gate]], [[Joint negation>>url:https://en.wikipedia.org/wiki/NOR_gate]], [[Logical consequence>>url:https://en.wikipedia.org/wiki/Logical_consequence]], [[Converse>>url:https://en.wikipedia.org/wiki/Converse_(logic)]], [[Material biconditional>>url:https://en.wikipedia.org/wiki/Logical_biconditional]] and non-equivalence.
80	80
81	81	The evaluation of the conditions takes place by default from left to right. By using parentheses, the order of evaluation can also be influenced. This could look like the following example:
82	82