vRealize Orchestrator

When using a User Interaction element in your workflow you might want to have it timeout after a certain amount of time. A user interaction accepts an input parameter of the Date-type that contains the date and time when the user interaction should timeout if it is not answered.

 

In the image below you see a workflow that contains a Scriptable task used to create the date_time variable to be used in the user interaction.

An updated version of this article can be found here: https://vmwarebits.com/moid

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.

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.

Workflow as downloadable package

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:

com.vmwarebits.clustertest.zip