5.5

5 On the General tab of the workflow editor, click the version number digits to increment the version
number.
For the initial creation of the workflow, set the version to 0.0.1.
6 Click the Server restart behavior value to set whether the workflow resumes after a server restart.
7 In the Description text box, type a description of what the workflow does.
8 Click Save at the bottom of the General tab.
You created the Take a Snapshot of All Virtual Machines in a Resource Pool workflow.
What to do next
You must create a custom action.
Create a Custom Action for the Complex Workflow Example
The Check VM scriptable element calls on an action that does not exist in the Orchestrator API. You must
create the getVMDiskModes action.
For more detail about creating actions, see Chapter 3, “Developing Actions,” on page 139.
Prerequisites
Create the Take a Snapshot of All Virtual Machines in a Resource Pool workflow. See “Create the Complex
Workflow Example,” on page 103.
Procedure
1 Close the workflow editor by clicking Save and Close.
2 Click the Actions view in the Orchestrator client.
3 Right-click the root of the actions hierarchical list and select New Module.
4 Name the new module com.vmware.example.
5 Right-click the com.vmware.example module and select Add Action.
6 Create an action called getVMDiskModes.
7 Right-click getVMDiskModes and select Edit.
8 Increment the version number in the General tab in the actions editor by clicking the version digits.
9 Add the following description of the action in the General tab.
This action returns an array containing the disk modes of all disks on a VM.
The elements in the array each have one of the following string values:
- persistent
- independent-persistent
- nonpersistent
- independent-nonpersistent
Legacy values:
- undoable
- append
10 Click the Scripting tab.
11 Right-click in the top pane of the Scripting tab and select Add Parameter to create the following input
parameter.
n
Name: vm
Developing with VMware vCenter Orchestrator
104 VMware, Inc.