Difference between revisions of "Workflow Condition Examples"
From SmartWiki
(→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=== | ||
| + | |||
| + | ===Example of Correct Configuration=== | ||
| + | |||
| + | ==Rule #2: Collectively, the conditions on each task should accommodate every possible permutation.== | ||
| + | |||
| + | ===Example of Incorrect Configuration=== | ||
| + | |||
| + | ===Example of Correct Configuration=== | ||
| + | |||
| + | |||
<!--Say for example that a given [[UTA]] contains seven different [[template]]s. One set of emails should be sent if a [[Level 1 Entity|Level 1]] record of one template is saved in a particular status, and another set of emails should be sent if a record is saved of a different template at the same status. If the record is of any of the other five templates, no email should be sent. | <!--Say for example that a given [[UTA]] contains seven different [[template]]s. One set of emails should be sent if a [[Level 1 Entity|Level 1]] record of one template is saved in a particular status, and another set of emails should be sent if a record is saved of a different template at the same status. If the record is of any of the other five templates, no email should be sent. | ||
Revision as of 16:04, 19 March 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.
