In this is the first of a series of quick videos/posts about how one could use the elements available in vRealize Automation Custom Forms.
This is by no way the only way and would be great to get peoples feed back and experiences on these.
Elements available to use are:
- Value Picker
- Data Grid
- Multi Select
- Drop Down
- Text Field
- Text Area
- Radio Group
- Date Time
Today we are looking at Value picker, Below is a video that I prepared earlier.
There is number of ways you can use value picker. I personally do not think it’s fully featured yet as there are some elements to it I believe should work better. I will not be going into every setting as there are many like visibility, read only custom help etc which are shared across all. I will have a separate post on general use.
The idea of value picker is that you can display, search and select object types different from the primitive types like sting, integer, bool etc. When you select the value picker on the the form you will notice the reference type field. This is where you can type a vRealize Orchestrator (vRO) object type. As you can see form the below image I have chosen AD:User.
This means if we choose to have an action for external values it will need to return an array of AD:User but what this also does well is it will automatically grab all your AD users from the vRO AD plugin to select for a default user.
This is where I think it falls short, because it can see and search all AD:User objects returning their name, wouldnt it be good if thats all we needed to do. If we were to save this and test the form I would have assumed it could search just like it could for selecting a default value. but unfortunatly thats not the case.
So now onto giving it some values to work with. I like to use external values, so I create one to return all my AD users. The value picker will only look for actions that have an output matching the reference type that was selected.
var adHost = System.getModule("virtualiseme.activeDirectory").getAdHost(domain);
var users = ActiveDirectory.search("User","",adHost);
Now if we are to test out the form again, we notice all of the ad users are displayed in the value picker. There is a small downside, the search functionality does not appear to work using it this way, and it is not as clean as how you can select a default value which tells it shouldn’t need an external value to work should just work like it does when selecting a default value but doesnt appear to be the case atm.
If you now provision a machine with a selected value it will pass the vRO reference for that object to the machine as a custom property and can be used in any EBS workflow or software component, This is fine and there are many ways to use this. But using a string and a standard drop down would be just as efficient.
I did try and be smart and have another field that would take the input of value picker, which it picks up that value picker field in this instance is AD:User and I could select that as an input of another field, the form would error saying it could not make the conversion of the object. Unfortunately the forms can not pass of handle complex objects just yet.
If you have any further input or advice for everyone please post below.