This package contains several examples that I use in Orchestrator training.
Import the package from the Packages-tab in the Orchestrator client.
What's in the package?
There are several workflows in this package that demonstrate the functionality of vRealize Orchestrator. Their purpose is to educate, comments are always welcome.
The listing below is just a subset of what is currently in the package. There are many more examples included in the latest version of the package.
Other workflows: read and write files on the VRO server, send an email, create snapshots for VMs in a folder etc.
Attribute and parameter demonstration
This workflow demonstrates how to work with input and output parameters and attributes. Run it with the debugger and evaluate the values of all variables at each breakpoint. Also read the comments in the scriptable elements to understand what's happening.
Input presentation demonstration
Various examples how to work with input presentation.
Get a counter from a REST host with a GET operation
This workflow accesses a HTTP-host with a REST GET operation to read a counter that is updated at that web page each time it is accessed.
Get a counter from a local file on a Windows Orchestrator server
This workflow reads and writes a counter in the local file system of a Windows Orchestrator server to allow for a persistent counter across workflows. To make it work on an Orchestrator Linux Appliance change the file path in the action to /var/run/vco which is a folder where the server has write permissions by default.
This is the code from the scriptable task:
var fw = new FileReader("c:/orchestrator/test.txt");
var line = fw.readLine();
counter = Number(line) + 1;
var fw = new FileWriter("c:/orchestrator/test.txt");
Find a user object in Active Directory and set a new password
This workflow uses an action to find a user and return a boolean, based on this the input presentation changes to show fields.
Get a dynamic list of Configuration Elements and their values
In this workflow a selection of Configuration Elements can be loaded into an input parameter with user input presentation and then the values from the selected Configuration Element can be loaded in a scriptable task to be used in the rest of the workflow. (based on this source)