This article is based on using the HTML-based user interface that was introduced with vRealize Orchestrator version 7.5 and which is the only available client in version 8. If you are running an older version and would like to use the instructions for the older Java-based client then you can find those instruction here.
Original location: Get to know VMware's vRealize Suite Lifecycle Manager
vRealize Orchestrator allows you to configure permissions for users in your authentication domain to access your vRO deployment with different types of access. While you might want administrators to access your workflows from the vSphere Web Client sometimes there will still be users that need access with the vRO client. One example is a group of developers that you only want to allow access to one or just a few folders in your vRO environment.
Original location: Comparing and contrasting vSphere PowerCLI and vRealize Orchestrator
With vRealize Automation 7 an Approval Policy can be linked to an event subscription that in turn can trigger a vRealize Orchestator workflow to perform an external approval process. In this article I describe how to setup the Workflow, the Approval Policy and the Event Subscription.
This simple workflow can be used to demonstrate the failover behavior in case of a vRealize Orchestrator node failure. It creates the number of VMs that your specify. I suggest 30. During the execution of the workflow power off one node of the cluster and you will be able to demonstrate that the execution continues on another node.
The workflow is available as a downloadable package:
This example workflow shows how you can use a ResourceElement containing a list of virtual machine names and execute a workflow for each of the VMs in the list. The workflows and actions are available as a package here: com.vmwarebits.vmlistExample.zip.
To use the workflow yoi create a ResourceElement and import a text file that contains the virtual machine names, such as in the next image.