Smartstaff, administrator
4,478
edits
Changes
→Workflow Condition Examples
There are two rules that must be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements:
'''1. Collectively, the conditions on each task must accommodate every possible permutation'''
*Example of Incorrect Configuration''':
** Three [[types]] exist in a given [[UTA|application]], with [[Determining the typeid|typeIDs]] of 12345, 45678 and 67890.
:** ''"@typeid@"="45678"'', respectively
* If the workflow is fired against a record associated with typeID 67890, the workflow will never progress to the next task.
** As above, three [[types]] 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:
'''2. Each condition must be mutually exclusive from every other'''*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 exist in the same application, with [[Determining the statusid|statusIDs]] of 888 and 999.
** The workflow process will not "know" which task to connect to. The workflow will progress, but not necessarily to the next intended workflow task. In other words, the wrong email may be sent.
** The types and statuses exist as above, and the system administrator wishes to configure the same branching logic.
** Two connectors should be set up on a workflow task with the following conditions:
