|
|
| (18 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | 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'''
| + | {{DeprecatedPage}} |
| − | 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(currentdate)@">"2013-01-01"
| |
| − | * "@date(currentdate)@">"@system.submission deadline@"
| |
| − | | |
| − | | |
| − | [[Category:Workflows]]
| |
This article is deprecated and the information contained within may no longer be correct.
