When creating an automation to perform actions based on specific behaviour or activity within your site, the automation must know "WHEN TO APPLY." This section of the automation is also referred to as the activation or activation statement and is one of three integral pieces of an automation. This article is an overview of the When statement and how to configure the first piece of your automations.
"WHEN TO APPLY" defines the specific action that will "activate" the automation. When the activation occurs, the automation will begin validating conditions within the automation. If the conditions have been met the specified actions will be performed in the order they are listed in the "DO" statement. An automation cannot be created or saved without an activation.
There are two mandatory selections in finalizing the automation's activation:
|Source||The source of the event.|
|Event||The event or action that will cause the automation to fire if the given rules have been met. The event prompts the automation to begin verifying if the given rules have been met at the time of the activation except when "applicant task" is the selected source.|
|Target (not always required)||Targets the specific task that will prompt the automation to fire.|
To set a target:
1. Select the drop-down menu
2. Select the Stage the task appears in the workflow from the left hand side of the drop-down
3. Select the task related to the event from the right hand side of the menu
This is only available when 'Applicant Task' is the selected source.
To set up the activation (WHEN TO APPLY) for an automation:
The build above depicts an activation statement after Set activation has been selected.
To edit an activation:
Certain actions and conditions are not available for particular activations. Because of this, if the source activation is cleared you will be presented with the following warning:
This will be displayed anytime an activation source is changed to notify you that all conditions and actions set for the automation will be REMOVED. This action cannot be undone.
If making extensive changes to an automation that would result in clearing the progress you've made, we would recommend proceeding as follows:
If the source of the activation is not being changed then this warning can be ignored.