Conditions determine whether a task should be activated or be skipped based on criteria that you define.
Examples of Use
Conditions could be used to define workflow like these examples:
- If a vacation request is approved, then notify the requestor and add a meeting to the team calendar
- If the item cost is over $10,000, then assign a task to a manager to review the expense
- If the email contains the word "refund," then start a refund process
When adding task conditions, keep in mind that the task will activate if the condition criteria evaluate to true and will be skipped if the condition criteria evaluate to false.
- In your process template, select a task and select Conditions
- Select or type the first value of the condition to add
- Select an operator
- Select or type the second value, if needed
- To add another condition:
- Select the + button
- Change And to Or if you would like the condition to evaluate to true if either condition is true
- Select Save
- See Condition Options for guidance for constructing conditions.
- Use conditions for a single task, or create branches in your process that each include multiple tasks. If the first task of a branch is skipped due to its dependency, any task that is dependent on that task being completed will also be skipped.
- Conditions are assessed after dependencies. Dependencies determine when a task is ready to run--when all preceding steps are completed. Then the condition is assessed to determine if the task should run or be skipped.
- Conditions are assessed both before any timing delay is initiated, and after the delay has occurred.