A logical statement can be added to workflow connectors in the Condition field, enabling you to specify which workflow task will be triggered. #REDIRECT [[Workflows_Overview#Workflow_Condition]]
'''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 not configurable it is important that the conditions are mutually exclusive. For example, if you have 3 connectors for different paths based on a particular value the conditions could be::* '''"@Selection@"="Yes"''':* '''"@Selection@"="No"''':* '''"@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 the Condition:* '''date_format(now(),"%d")="01"'''::* This condition will be true only on the 1st of the month. This can be used with a '''Recurring''' workflow that loops daily. For example, if you wish to send out a summary e-mail on the 1st of every month. Would be used in association with another workflow connector with a condition of '''date_format(now(),"%d")!="01"''' connecting to a 1-day delay. Note: Other than values that are always numeric, all variables should be enclosed in double quotes. [[Category:Workflows]]{{DeprecatedPage}}
