4.2.1

The action elements' input and output parameters are bound to the appropriate parameter types and values.
What to do next
Bind the scriptable task elements and define their functions.
Simple Workflow Example Action Element Bindings
Bindings define how the simple workflow example's action elements process input and output parameters.
When defining bindings, Orchestrator presents parameters you have already defined in the workflow as
candidates for binding. If you have not defined the required parameter in the workflow yet, the only parameter
choice is NULL. Click Create parameter/attribute in workflow to create a new parameter.
vim3WaitTaskEnd Action
The vim3WaitTaskEnd action element declares constants to track the progress of a task and a polling rate. The
following table shows the input and output parameter bindings that the vim3WaitTaskEnd action requires.
Table 1-8. Binding Values of the vim3WaitTaskEnd Action
Parameter Name Binding Type
Bind to Existing or
Create Parameter? Binding Values
task
IN Bind
n
Local Parameter: powerOnTask
n
Source parameter:
task[attribute]
n
Type: VC:Task
n
Description:
Contains the result of
powering on a VM.
progress
IN Create
n
Local Parameter: progress
n
Source parameter:
progress[attribute]
n
Type: Boolean
n
Value: No (false)
n
Description:
Log progress while waiting
for the vCenter Server task
to complete.
pollRate
IN Create
n
Local Parameter: pollRate
n
Source parameter:
pollRate[attribute]
n
Type: number
n
Value: 2
n
Description:
Polling rate in seconds at
which vim3WaitTaskEnd
checks the advancement of
the vCenter Server task.
actionResult
OUT Create
n
Local Parameter:
actionResult[attribute]
n
Source parameter:
returnedManagedObject[attri
bute]
n
Type: Any
n
Description:
The returned managed object
from the waitTaskEnd
action.
Developing with VMware vCenter Orchestrator
74 VMware, Inc.