Changes

Jump to: navigation, search

Workflow Condition Examples

721 bytes added, 16:23, 16 July 2013
no edit summary
=Page Under Construction= There are two rules that should must be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements:# Collectively, the conditions on each task should must accommodate every possible permutation.# Each condition should must be mutually exclusive from every other.
Let's discuss each of these rules.
===Example of Incorrect Configuration===
* Three [[types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeIDs]] of 12345, 45678 and 67890.
* Two [[status]]es exists in the same application, with [[Determining the statusid|statusIDs]] of 888 and 999.
* The system administrator wishes to send emails via workflow if the record is in one of the above statuses. One email should be sent out if the type is 12345 or 45678 and a different email should be sent out if a different type has been used.
* Two connectors are set up on a workflow task with conditions of:
:* ''"@typeid@" in ("12345","45678") AND "@statusid@" in ("888","999")'' and
:* ''"@parent.statusid@" in ("888","999")''
* The issue here is that both statements [[Boolean Operators|evaluate]] as '''true'''
 
 
===Example of Correct Configuration===
8,849
edits

Navigation menu