An automation template is a reusable template that contains a list of steps that can be executed in the future. Let’s say you want to execute a data backup whenever you deploy a data template, you can configure an automation template to run a data backup and reuse it every time you do a data migration.
An automation template can be executed as part of an Apex class and from an external source using a Copado webhook, but also as part of a connection behavior if you are working with Copado Continuous Delivery. You can configure the template directly in a connection behavior or in a deployment step.
Now, what kind of actions or steps can be included in an automation template? Currently, three steps are supported:
- Salesforce Flow
- External CI
Now that you have an idea of what an automation template is, let’s go on to describe the different sections and fields you can find in a template and see how it actually looks like.
Tabs and Fields
An automation template contains three main tabs, Details, Steps and Execution History.
In the Details tab, you can provide a name for your template and a description. The Active checkbox lets users know the template is ready to be used. Once you have finished configuring your template and are happy with the changes, you can select this checkbox:
The Steps tab is where you can configure the different steps you want to execute as part of the automation template. Give your step a name and select a step type from the drop-down menu:
A screen to configure the selected step will be displayed. In the example below, you can see the Salesforce Flow step configuration screen:
Finally, in the Execution History tab you will find a record for each time the template has been executed, and you can navigate to the deployment that triggered the execution:
Now that you know what an automation template is and how you can build one, navigate to the Executing an Automation Template article to learn how to run an automation template as part of your DevOps process.