6.1

Making the Workflows Available in
vSphere Web Client and
vRealize Automation 4
Administrators can expose the Horizon workflows in the vRealize Automation self-service catalog or in the
vSphere Web Client. For some workflows that delegated administrators run within vSphere Web Client,
you must specify which pod or pools the workflows act on.
This chapter includes the following topics:
n
“Exposing VMware Horizon vRealize Orchestrator Plug-In Workflows in vSphere Web Client,” on
page 39
n
“Exposing Horizon vRealize Orchestrator Plug-In Workflows in vRealize Automation,” on page 41
Exposing VMware Horizon vRealize Orchestrator Plug-In Workflows in
vSphere Web Client
Administrators can configure Horizon workflows so that delegated administrators can run them from
within vSphere Web Client. The delegated administrator can search for the name of the workflow and run
and schedule vRealize Orchestrator workflows.
Bind vSphereWebClient Workflows to Specific Pods and Pools in
vRealize Orchestrator
When a delegated administrator's access must be restricted to particular pools or pods, you can bind a
workflow to a specific pool or pod. Administrators can duplicate workflows and bind them to different
pools as needed.
After an administrator binds a workflow to a pod, the delegated administrator sees a drop-down list of the
pools that belong to that pod in vSphere Web Client. You can, however, also bind the workflow to a specific
pool and disable the drop-down list of pools. Drop-down lists of pools are supported for most workflows
regardless of whether the workflows are localized.
IMPORTANT For the following workflows, if you plan to localize the workflow, you must bind the workflow
to a specific pool and disable the drop-down list of pools:
n
Application Entitlement
n
Assign User
n
Desktop Assignment
n
Desktop Entitlement
n
Unassign User
VMware, Inc.
39