When to Use Action Conditions
Example 1: Branching Workflows
Let’s say a form starts with a student and then needs to go to either the school or the student’s parent.
Student
/ \
School Parent
Add an Action Condition to the first action in each path where the workflow branches. You do not need to add conditions to every action that follows. Once the workflow enters a path, it continues along that path until it reaches another split or condition.
If your workflow branches into multiple paths, each path should have its own Action Condition. If none of the conditions are true, the workflow defaults to the leftmost path.
Student
/ \
School Parent
| |
Dean HS Counselor
Alternative: If each path contains only one participant, you can place both participants in the same action and use Participant Conditions instead. This creates one straight workflow rather than two separate paths.
Example 2: Stopping a Workflow
Action Conditions can also prevent a form from moving forward when a participant does not approve it.
Let’s say your workflow follows this sequence:
Student
|
Advisor 1
|
Advisor 2
|
Dean
If each person must approve the form before it moves to the next person, you would add an Action Condition to both the Advisor 2 action and the Dean action.
-
Advisor 2 Action
Add the following condition: IF Advisor1Dropdown is Equal to “Approve”
If True: The workflow continues to Advisor 2
If False: Advisor 2 and the Dean are skipped, and the form moves to the Pending queue
-
Dean Action
Add the following condition: IF Advisor2Dropdown is Equal to “Approve”
If True: The workflow continues to the Dean
If False: The Dean is skipped, and the form moves to the Pending queue
This ensures that each participant only receives the form if the previous participant approved it. The condition on the Advisor 2 action checks Advisor 1’s decision, while the condition on the Dean action checks Advisor 2’s decision.
Adding an Action Condition
- Select the action you want to add a condition to and select Add condition to this workflow action