You can map custom and user-defined workflows to actions. Repeat the task to add one workflow to more than one resource. You can perform this task for multiple workflows simultaneously within a package by running the same action on a package resource.


You must discover user-defined workflows them before you can add them as an action to a resource.
Note: You can only map workflows to the supported target resources.


  1. In the menu, select Administration and click Inventory in the left pane.
  2. Select Adapter Instances and then vRealize Orchestrator Adapter Instance from the list of adapter instances.
  3. Select the vRealize Orchestrator adapter instance that contains the workflow that you want to run.
    A list of all the workflows are displayed on the right pane.
    Note: This action is present at the Adapter instance level, package level, and workflow level. The most recommended is the package and workflow level.
  4. From the right pane, select the workflow that you want to add to a resource.
  5. Click the Action icon and then Create/Modify Workflow Action on vCenter Resources.
    Note: Ensure that there is at least one input parameter in the workflow, otherwise the action fails when it is run.
  6. Configure the following properties
    Property Option
    Workflow Select a workflow from the drop-down menu.
    Note: Do not modify out-of-the-box workflows.
    Available on Resource Type If the workflow is already configured as an action in a resource type, it is displayed here.
    Action Target Type If the workflow is already configured as an action in the target resource type, it is displayed here.
    Resource Type Select a resource type from the drop-down menu.
    Target Resource Type Select a resource type. The resource type and the target resource type should be the same.
    Operation Choose to add or remove the workflow as an action. Options are Add and Remove.

    With the Management Pack for vRealize Orchestrator 3.1, you can map any custom workflow to the parent resource. The parent object is the Resource Type and the Target Type is the actual vCenter object that the workflow is targeted for. The workflow accepts the target object as its input parameter. For example, if you want to map a workflow “Change Ram” to a host system and run the same workflow on multiple virtual machines under it, then select the Resource Type as Host System and the Target Type as Virtual Machine.

  7. Click Begin Action.
    A task is added to the task list.


You can verify that the action is available by clicking the Action icon after you select the resource with the required Adapter Type and Object Type in the right pane. From the list displayed under the Action icon, verify that the workflow that you added to the resource is available as an action in the list. You must wait one collection cycle before you can verify. You can monitor the task list to see the status of the task.