Changes

Workflows Overview

105 bytes added, 17:30, 23 April 2020
Workflow Condition Examples
''<u>Example of Correct Configuration</u>'':
Three level one [[Level 2 Types|Level_2_Typestypes]] 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:
* ''"@@level2levelone.typeid@"="12345"'',* ''"@@level2levelone.typeid@"="45678"'' and* ''"@@level2levelone.typeid@"="67890"'', respectively
* ''"@levelone.typeid@"="12345"''* ''"@levelone.typeid@"!="12345"'' (not equal to "12345"), and* ''"@levelone.typeid@" NOT IN ("12345","45678")'', respectively
''<u>Example of Incorrect Configuration</u>'':
Three [[Level_2_Types|level 2 types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeIDs]] of 12345, 45678 and 67890.
Two level 2 [[status]]es exist 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:
* ''"@level2.typeid@" in ("12345","45678") AND "@level2.statusid@" in ("888","999")'' and* ''"@level2.statusid@" in ("888","999")''
Two connectors should be set up on a workflow task with the following conditions:
* ''"@level2.typeid@" in ("12345","45678") AND "@level2.statusid@" in ("888","999")'' and* ''"@level2.typeid@" not in ("12345","45678") AND "@level2.statusid@" in ("888","999")''
This configuration satisfies Rule #2, in that the conditions are now mutually exclusive. However, a third connector must be included, with the following condition, which connects to the "Complete" task, in order to satisfy Rule #1 above:
* ''"@level2.statusid@" not in ("888","999")''
Smartstaff, administrator
4,478
edits