Difference between revisions of "Workflow Condition Examples"
From SmartWiki
(→Rule #1: Collectively, the conditions on each task should accommodate every possible permutation.) |
|||
| Line 1: | Line 1: | ||
| + | =Page Under Construction= | ||
| + | |||
There are two rules that should be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements: | There are two rules that should be followed when adding multiple connectors to a workflow task that incorporate conditional logic statements: | ||
# Collectively, the conditions on each task should accommodate every possible permutation. | # Collectively, the conditions on each task should accommodate every possible permutation. | ||
| Line 9: | Line 11: | ||
===Example of Incorrect Configuration=== | ===Example of Incorrect Configuration=== | ||
| − | Say for example that a given [[UTA]] contains seven different [[template]]s. One set of emails should be sent if a [[Level 1 Entity|Level 1]] record of one template is saved in a particular status, and another set of emails should be sent if a record is saved of a different template at the same status. If the record is of any of the other five templates, no email should be sent. | + | <!--Say for example that a given [[UTA]] contains seven different [[template]]s. One set of emails should be sent if a [[Level 1 Entity|Level 1]] record of one template is saved in a particular status, and another set of emails should be sent if a record is saved of a different template at the same status. If the record is of any of the other five templates, no email should be sent. |
| Line 34: | Line 36: | ||
You can also use MYSQL syntax to perform calculations within the Condition: | You can also use MYSQL syntax to perform calculations within the Condition: | ||
* '''date_format(now(),"%d")="01"''' | * '''date_format(now(),"%d")="01"''' | ||
| − | ::* This condition will be true only on the 1st of the month. This could be used with a '''[[Recurring Workflow]]''' that loops daily if you wish to send out a summary e-mail on the 1st of every month. See [[Recurring Workflow|here]] for further details. | + | ::* This condition will be true only on the 1st of the month. This could be used with a '''[[Recurring Workflow]]''' that loops daily if you wish to send out a summary e-mail on the 1st of every month. See [[Recurring Workflow|here]] for further details.--> |
=See Also= | =See Also= | ||
Revision as of 16:03, 19 March 2013
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:
- Collectively, the conditions on each task should accommodate every possible permutation.
- Each condition should be mutually exclusive from every other.
Let's discuss each of these rules.
