Yes/no tasks can be used to collect data during a job, which can then be used later in the job to decide when other tasks kick off, or whether tasks should even be included in the job.
TABLE OF CONTENTS
- Creating a yes/no task
- Use the yes/no task as a filter on another task
- Setting up a task dependency using yes/no tasks
Creating a yes/no task
First you need to add the yes/no task type in to the job template.
Go to Settings > Jobs.
Pick any job or create a new one, then click on Add task.
Select Type of task - Yes/no.
Next, select the Yes/no tab and add the task question.
Use the yes/no task as a filter on another task
Filters dictate whether a task will appear in a job or not.
Click on Add new task to add the task that will be filtered depending on the answer to our yes/no task.
Select the Type of task, for example - Send email.
Go to the Filters tab and click on Add filter. Select the relevant field from the Choose a field list.
Click OK and then select either Yes or No and click OK to confirm the selection.
The task in the example above will only display in a job if the answer to the previous question is "yes".
Setting up a task dependency using yes/no tasks
A dependency means that a task will only start, once a previous task has been completed. In this case, we only want to call the client once we have answered the question about whether they want to receive a newsletter.
Select the task that you would like to make dependent on the yes/no task, and go to the Depends upon tab.
Click on Add dependency.
Select the yes/no task you have created, and click OK.
The task will show that it is now dependent upon task 1, whether the answer is yes or no.
Important note: The advanced section of this dependency shouldn't be used, except in very specific scenarios.
If you want this task to depend on the yes/no task being "yes" for example, then a dependency isn't the right choice - instead, you should add this as a filter (see above section on using a yes/no task as a filter).
If you tick either "yes" or "no" in the advanced section when adding the dependency, this task will always be blocked.
It is important to leave both "yes" and "no" boxes ticked if you are going to use the Advanced feature at all. If the answer to task 1 is "yes", but you set task 2 to only be dependent on the answer "no", then the task will always be blocked and will never become ready.