1.2.0

Callback workflows that contain an in = out element perform the following tasks:
n
Clone the properties of the LCM workflow that calls the callback workflow.
n
Optionally perform processing on the cloned properties in the callback workflow to modify them.
n
Pass the modified properties as the outCloneProperties output parameter to the next element in the LCM
workflow, thus changing the result of the request.
The in = out element contains the following scripting code:
outCloneProperties= cloneProperties;
If you do not modify the callback workflow, the value of the outCloneProperties output parameter it returns
is identical to the cloneProperties input parameter it received. However, you can modify the callback
workflow so that it results in a outCloneProperties output parameter with a value different from the initial
cloneProperties value.
By modifying the properties of the LCM workflow that calls the callback workflow, the callback workflow
changes the result of the LCM request.
Callback Workflow Categories
LCM installs five default callback workflow categories.
Table 4-1 lists the default callback workflow categories and the type of workflows that they contain.
Table 4-1. Default Callback Workflow Categories
Category Content
Create Virtual machine creation events
Decommission Virtual machine decommissioning events
End date range Virtual machine request extension events
Provision Virtual machine provisioning events
Shaping change Virtual machine customization change events
Find Related Workflows
You can search for standard workflows that use callback workflows as a part of their execution procedure.
Procedure
1 Log in to the Orchestrator client as an administrator.
2 Click the Workflows view.
3 Expand the hierarchichal tree to Applications > Lifecycle manager > Callback.
4 Expand a workflow category.
5 Right-click a callback workflow and select References > Find Elements that Use this Element.
Lifecycle Manager Administration Guide
44 VMware, Inc.