7.2
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Index
Bind Custom Properties to Create a Parent-Child Relationship
To create a parent-child relationship between custom properties, you bind the parent to the child. When you
add the parent and child custom properties to a blueprint, the requesting user selects a value for the parent
property. The selected parent value determines the possible values for the child property.
n
The parent custom property denition can be a static list or an external value that is determined by an
vRealize Orchestrator action. It provides possible input parameters to a child property denition.
n
The child custom property denition must call a vRealize Orchestrator action. In the child custom
property, you bind the parent custom property so that it provides an input parameter value.
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 denition. 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.
Custom Properties Reference
94 VMware, Inc.