You can use vCloud Automation Center Designer activities to call vCenter Orchestrator workflows either synchronously or asynchronously.

The InvokeVcoWorkflow activity calls a vCenter Orchestrator workflow and blocks further execution of its parent IaaS workflow until the vCenter Orchestrator workflow completes. The activity returns the output parameters for the vCenter Orchestrator workflow.

The InvokeVcoWorkflowAsync activity is a “fire and forget” activity that calls a vCenter Orchestrator workflow and continues to execute activities in the IaaS workflow without waiting for the vCenter Orchestrator workflow to complete.

The activity returns either a unique workflow execution token that can be used to monitor the workflow or an error if the REST API call to the vCenter Orchestrator server failed (for example, if the server could not be reached).

Two additional activities are available for use with this activity:

GetVcoWorkflowExecutionStatus enables you to poll the vCenter Orchestrator workflow for its status.

WaitForVcoWorkflowCompletion enables you to block further execution of the IaaS workflow until the vCenter Orchestrator workflow has completed or timed out. You can use this activity to retrieve the results of a vCenter Orchestrator workflow that you execute asynchronously.