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
Using the Property Dictionary 4
You can use the property dictionary to dene new custom property denitions and property groups.
You dene a property to support a specic data type and a display control style within that data type. You
can also create reusable property groups to simplify adding multiple properties.
This chapter includes the following topics:
n
“Using Property Denitions,” on page 87
n
“Using Property Groups,” on page 106
Using Property Definitions
Many custom properties are supplied with vRealize Automation. You can also dene new properties to
create unique custom properties and provide greater control for provisioning machines.
When you add a property to a blueprint or reservation, you can determine if a user must be prompted for a
property value and if the property value must be encrypted.
You can specify how a property is rendered, for example if should display as a checkbox or as a drop-down
menu with values obtained from a custom vRealize Orchestrator workow.
You can also use properties to control how your custom workows function. For information about using
vRealize Automation Designer to dene and work with custom workows, see Life Cycle Extensibility.
Best Practices for Naming Property Definitions
To avoid naming conicts with supplied vRealize Automation custom properties, use a standard and
meaningful prex for all property names that you create. Use a prex such as a company or feature name
followed by a dot for all new property names. VMware reserves all property names that do not contain a dot
(.). Property names that do not follow this recommendation may conict with vRealize Automation custom
properties. In that event, the vRealize Automation custom property takes precedence over property
denitions that you create.
Limitations
If you create a property denition where Type equals String, Display as equals Dropdown, and you use a
vRealize Orchestrator action that returns properties that populate the drop-down list, the list is in random
order. You cannot specify the order.
VMware, Inc.
87