Workflow Condition Examples

Revision as of 10:58, 16 July 2013 by Arthur Lathrop (talk | contribs) (Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.)

Revision as of 10:58, 16 July 2013 by Arthur Lathrop (talk | contribs) (Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.)

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:

  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

  • 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

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