How we can implement the property relation in VMware vRealize Automation 7, which most of the customers might be looking for. In vRA7 the removal of property relationships and XML has made the approach little composite, which was much easier during vCAC 6.x by using a simple XML relation file.
This information may helpful for everyone who are looking for the property relation options to customize the request form in VMware vRealize Automation 7. However the developers will find this tactic much interesting. Here in this basic example we can achieve a simple property relation as described in given flowchart.
Now we will login to VMware vRealize Orchestrator client with admin privilege to create the Actions. We can use Actions in Workflows. The workflow will have all the ‘in’ and ‘out’ option and also on right pane we can see the presentation about it. Under Design section we can create a new Action. Here I named the folder as Custom_Property_Relationship_Test and also created two actions as OStypes and Templates. Set the appropriate values in General tab and Change the Return Type to Array/String in Scripting tab.
In Action “OStypes” we can write this script: return ["Windows","Linux","Others"]
In Action “Templates” we can write this script:
//Sample Script For Custom_Property_Relationship_Test
return ["Invalid OS Type Selected"];
Now let’s create the Property Definitions under Administration tab in vRA. The first property definition must be for the OS type so choose an appropriate name. The Label is the text which will display in catalog request page so keep this in mind. Choose the Order Index as 1, Data Type as String, Choose Yes for Required field, Choose Drop Down for Display Advice and Values must be External Values.
Now we can go for second Property Definition which will be used for the selection of templates. The Label is the text which will display in catalog request page so keep this in mind. Choose the Order Index as 2, Data Type as String, Choose Yes for Required field, Choose Drop Down for Display Advice and Values must be External Values. Browse to the newly created Action for OS types and click OK.
Tick Bind check box and close the error. Select the dependency Value which we have created earlier.
Now we must create a Property Group and add both of the Property Definitions to this.
Finally we can edit the required Blueprint to add the Property Group in Blueprint Properties section.
Once we did all the above step, then we can go to Catalog tab in vRA self-service portal and create a new request by using the specific catalog which was used by above Blueprint. Now you can see the custom relation options in request form as shown in below image.