Difference between revisions of "Workflow Condition Examples"

From SmartWiki
Jump to: navigation, search
(Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.)
(Rule #2: Collectively, the conditions on each task should accommodate every possible permutation.)
Line 13: Line 13:
 
===Example of Correct Configuration===
 
===Example of Correct Configuration===
  
==Rule #2: Collectively, the conditions on each task should accommodate every possible permutation.==
+
==Rule #2: Each condition should be mutually exclusive from every other.==
  
 
===Example of Incorrect Configuration===
 
===Example of Incorrect Configuration===

Revision as of 16:04, 19 March 2013

Page Under Construction

There are two rules that should be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements:

  1. Collectively, the conditions on each task should accommodate every possible permutation.
  2. 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

Example of Correct Configuration

Rule #2: Each condition should be mutually exclusive from every other.

Example of Incorrect Configuration

Example of Correct Configuration

See Also