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 the workflows to different pools as needed.
After an administrator binds a workflow to a pod, the delegated administrator sees a drop-down menu of the pools that belong to that pod in vSphere Web Client. You can also bind the workflow to a specific pool and deactivate the drop-down menu of pools. Drop-down menus of pools are supported for most workflows, regardless of whether the workflows are localized.
For the following workflows, if you plan to localize the workflow, you must bind the workflow to a specific pool and deactivate the drop-down menu of pools:
- Application Entitlement
- Assign User
- Desktop Assignment
- Desktop Entitlement
- Unassign User
Prerequisites
- Verify that you have administrator credentials for the vRealize Orchestrator server. The account must be a member of the vRealize Orchestrator Admin group configured to authenticate through vCenter Single Sign-On.
- Verify that a connection has been made to the pod by running the Add View Pod in the Configuration workflow. See Configure the Connection to a Pod in VMware Horizon 8.
- Verify that you have assigned the correct delegated administrators to the pools that you plan to expose through vSphere Web Client. See Assign Delegated Administrators to Pools.
Procedure
Results
When this workflow starts, the pod name and pool ID are already populated and cannot be changed.
What to do next
Create versions of the workflow in other languages.