3. Triggering Workflows with vCloud Notifications : 3.6 Triggered Workflow Examples : 3.6.1 Example of a Workflow Approval: Approve vApp (Simple) : 3.6.1.1. Workflow Steps
   
3.6.1.1. Workflow Steps
1. Change the blocking task timeout to the one set in the configuration (to avoid timeout of the blocking task before it can be handled).
2. Get as much information as possible on the vApp and its child virtual machines. Because the vApp does not exist yet its object may not contain all of the expected information. This information is compiled in a content attribute.
3. Set an email subject to "vApp Request [vAppName] has been requested by user [username]".
4. Check if this organization was set for auto approval. If so, resume the blocking task.
5. If the organization is not set for auto approval, set the approvers (either a single email or set to use the organization administrators, and get their email addresses).
6. Send a notification email for the approval. The approval can be done from the vCenter Orchestrator client or from the vSphere Web Client.
7. Generate a user interaction waiting for approval.
8. Send a last notice email if the user interaction times out. Fail the blocking task if the last notice email was previously sent.
9. If the user interaction is approved then resume the blocking task. Otherwise fail the blocking task.
The other approval workflows are built on the same base.