8,849
edits
Changes
no edit summary
Let's discuss each of these rules.
==Rule #1: Collectively, the conditions on each task should must accommodate every possible permutation.==
===Example of Incorrect Configuration===
* Three [[types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeidstypeIDs]] 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 record associated with typeID 67890, the workflow will never progress to the next task.
===Example Examples of Correct Configuration===* As above, three [[types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeIDs]] of 12345, 45678 and 67890.* Three connectors are set up on a workflow task with conditions of::* ''"@typeid@"="12345"'', :* ''"@typeid@"="45678"'' and :* ''"@typeid@"="67890"'', respectively* '''Alternatively''', two connectors with the following conditions could be set up::* ''"@typeid@"="12345"'' and:* ''"@typeid@"!="12345"'' (not equal to "12345"), respectively * In all cases, when using logical conditions on connectors, the conditions must encompass all possible logical scenarios.
==Rule #2: Each condition should be mutually exclusive from every other.==
