Difference between revisions of "Workflow Condition Examples"
From SmartWiki
(→See Also) |
(→Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.) |
||
| Line 10: | Line 10: | ||
===Example of Incorrect Configuration=== | ===Example of Incorrect Configuration=== | ||
| + | * Three [[types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeids]] of 12345, 45678 and 67890. | ||
| + | * Two connectors are set up on a workflow task with conditions of: | ||
| + | :* ''"@typeid@"="12345"'' and | ||
| + | :* ''"@typeid@"="45678"'', respectively | ||
| + | * If the workflow is fired against a | ||
===Example of Correct Configuration=== | ===Example of Correct Configuration=== | ||
Revision as of 10:58, 16 July 2013
Contents
Page Under Construction
There are two rules that should be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements:
- Collectively, the conditions on each task should accommodate every possible permutation.
- Each condition should be mutually exclusive from every other.
Let's discuss each of these rules.
Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.
Example of Incorrect Configuration
- Three types exist in a given application, with typeids of 12345, 45678 and 67890.
- Two connectors are set up on a workflow task with conditions of:
- "@typeid@"="12345" and
- "@typeid@"="45678", respectively
- If the workflow is fired against a
