*Warning before we begin, in this post I am making the assumption that you are not using vCD as an endpoint. If you are then I recommend skipping this tutorial all together.
Today we’re going to focus on the included vCAC Plugin in vCO, and more specifically how we can start to take the default “Workflow template” and make it usable as the wrapper that will be called to execute any number of automation tasks based on properties from vCAC.
If you would rather just download a workflow template and move on to the next session feel free to do so here.
In the vCO client navigate to the “Workflow template”. The path should be Library->vCloud Automation Center->Extensibility->Workflow template. Now right click and select Duplicate workflow.
Name your workflow and select what folder you would like it to be placed into.
Edit the new workflow.
Select the vCloudVApp and hit the red X to remove it from Input tab.
Go to the Schema tab and edit the script
Select the vCloudVApp and hit the red X to remove from the In tab.
Now highlight and delete the script references to vCD. This should be lines 3-8 in the script.
Alter the “Got vCloud VM ” line to read “Got vCenter VM ” (this isn’t required but something I like to do to keep consistency).
This is how I like the final script to look, I added the vmName as variable for potential future use cases. Then click Close.
Now Save and Close, the validation will detect unused entities. This is normal so you can click Continue anyway.
I always Increase the version to manage version control.
Your template workflow is now ready to be duplicated and used to execute any logic based on the vCAC properties that are collected!