When to Use Dependent Task and Activation Criteria in Journey Tasks

This table describes the different conditions where you can use dependent task and activation criteria.

Condition	Dependent Task	Activation Criteria
When to use?	When one or more tasks needs to be performed after a preceding task is in terminal status in the same journey.	When one or more tasks needs to be triggered based on the response to another task in the same journey.
Triggering Factor	Preceding task's terminal status.	Preceding task's terminal status and Activation Criteria based on the preceding task's data.
Sample Use Cases	If you want to verify the data provided in a preceding task, you can create a dependent journey task. For example, create a dependent task with HR Representative or Line Manager as task performer to verify data provided by a new hire as part of their onboarding. If the HR Representative or Line Manager doesn't find the data as per requirement, then they can reopen the original journey task for the new hire to update the data. If you want to acknowledge that the new hire has reviewed organization policy documents during their onboarding, you can create one journey task of the type Document and attach all your policy documents to that task. Then, create another journey task of type Questionnaire that’s dependent on the previous document task. In this task, you can ask all those questions if the user agrees to the various policies. You can even have one field in that Questionnaire asking the user to enter their full name and maybe date, as a means of soft acknowledgement.	You have a task where employees need to respond with a Yes or No for their vaccination certificate. If they answer Yes, you can use the activation criteria to check for this response and trigger a dependent task where they can upload their vaccination certificate. If they answer No, you can use the activation criteria to check and trigger a dependent task where they respond to a Wellness check questionnaire.