7.4
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for 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 and Security
- Custom Properties and Property Groups for Containers
- Custom Properties for PXE Provisioning
- Custom Properties for OVF Import
- 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 (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
Option Description
Description Describe the intent of the property definition and any other helpful information
about the property.
Display order The number that you enter controls where the property name appears on the
request form. The following ordering rules apply:
n
The display order applies only to properties that are configured with Prompt
User or Show in Request Form settings.
n
All properties with a display order appear before properties with no order
index.
n
Properties with a display order are sorted from lowest to highest value. You
can use negative numbers.
n
All properties are ordered alphabetically, with all display order properties
appearing before non-display order properties.
n
If two properties have the same display order value, they are sorted
alphabetically.
4 Consult the configuration details to determine what you must provide for the values.
The following values are provided in the configuration details:
n
Data type
n
Display as
n
Values
n
Action folder
n
Script action
n
Input parameters
5 Click OK.
The custom property definition is added to the list and it is available to add to a blueprint.
What to do next
Add the custom property to a blueprint. Whether you add it as a machine or as a network property
depends on the property. See Add a Custom Property to a Blueprint.
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 definition 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 definition.
n
The child custom property definition 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.
Custom Properties Reference
VMware, Inc. 107