7.1

For example, your development team works on production and non-production systems. You also have ve
data centers. Three of the data centers are your development testing data centers and the other two are
where you provide services to your internal clients. To ensure that developers can deploy the same blueprint
to either environment, the testing or the internal clients data centers, you create and bind two custom
property denition. Using the rst custom property, the requesting user can select either the production or
non-production environment. Based the environment that the user selects in the request form, the second
custom property displays one the following values:
n
The list of three testing data centers for the non-production environments.
n
The two internal clients data centers as production environments.
The goal of this procedure is to create two custom properties that you bind in parent-child relationship.
With the binding, you can select the appropriate location based on the selected production state.
Prerequisites
n
For this example, create a vRealize Orchestrator action that provides data center names as location
information. Name the action datacenters_prod, add an input parameter named prod as a string type,
and use this sample script for the action script.
if(prod == null) {
return ['Empty1', 'Empty2'];
} else if (prod.equals('nonprod')) {
return ['WestDC for development testing', 'EastDC for QA automation testing', 'CentralDC
for scale testing'];
} else {
return ['NorthDC for AMEA clients', 'SouthDC for Asia Pacific clients'];
}
For information about developing workows, and about creating and using vRealize Orchestrator
script actions, see Developing with VMware vCenter Orchestrator .
n
Log in to the vRealize Automation console as a tenant administrator or fabric administrator.
Custom Properties Reference
92 VMware, Inc.