===Example of Correct Configuration===
* 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:
:* ''"@typeid@" in ("12345","45678") AND "@statusid@" in ("888","999")'' and
:* ''"@typeid@" not in ("12345","45678") AND "@statusid@" in ("888","999")''
* This configuration satisfies Rule #2, in that the conditions are now mutually exclusive.
* '''HOWEVER''', a third connector should be included, which connects to the "Complete" task, in order to satisfy Rule #1 above:
:* ''"@statusid@" not in ("888","999")''
<!--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* With these three connectors configured, 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. A logical statement can be added to workflow connectors in the Condition field, enabling you to specify which workflow task will be triggered. :'''Example'''Branching Logic can be implemented to send an approval message to Senior Management when the request is over $100,000, while requests under $100,000 will take a different path when the workflow is triggered. [[Image:newconnector.jpg]] In general the Workflow Condition is used with several different connectors attached to a task. Collectively the conditions on each task should accommodate every possibility. *'''Note''': because the sequence in which the system accesses each connector is never not configurable '''it is important that the conditions are mutually exclusive'''. For example, if you have 3 connectors for different paths based instructions on a particular value the conditions could be::* '''"@Selection@"="Yes"''':* '''"@Selection@"="No"whether''':* '''"@Selection@"!="Yes" and "@Selection@"!="No"''' :::* The last statement could also be represented as '''"@Selection@" not in ("Yes","No")''' ==Sample Conditions==* '''@Request Amount.value@>100000'''* '''"@date(fullstartdate)@">"2013-01-01"'''* '''"@date(currentdate)@">"@system.submission deadline@"''' You can also use MYSQL syntax to perform calculations within trigger the Condition:* '''date_format(nownext workflow task (Rule #1),"%d")="01"'''and::* This condition will be true only always have clear instructions on the 1st of the month. This could be used with a ''which'[[Recurring Workflow]]''' that loops daily if you wish task to send out trigger given a summary e-mail on the 1st certain set of every month. See [[Recurring Workflow|here]] for further detailsconditions (Rule #2).-->
=See Also=
