7.1
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
Configuration Details for the vRealize Orchestrator Action Custom Property
Definitions
You create custom property denitions that run vRealize Orchestrator actions to retrieve key value pairs
from external les or from vRealize Automation conguration information. You add the custom properties
to blueprints so that they appear in the catalog request forms.
The service catalog user requesting the item can select a value to include in the deployment. When the user
clicks the drop-down menu to select a value, the vRealize Orchestrator action runs, retrieving the data that
is displayed in the menu for the user to select.
The conguration workows for each vRealize Orchestrator actions property denition are similar, but
some of the details vary. For example, there are dierences in prerequisites and limitations, and where you
apply the custom property in the blueprint might vary.
n
Network Custom Property Denition on page 98
You add a custom property to retrieve network names from the vRealize Automation database when
you want users to select the network in the request form. The network selector custom property uses a
vRealize Orchestrator action to retrieve the values.
n
Reservation Policy Custom Property Denition on page 99
You add a custom property denition to retrieve reservation policy names that are applicable to the
requesting users when they select the policy in the request form. The reservation policy selector
custom property denition uses a vRealize Orchestrator action to retrieve the values.
n
PowerShell Script Custom Property Denition on page 100
You add a custom property to run a PowerShell script when you want to use a script to retrieve data to
populate the custom property in the request form. The PowerShell script custom property uses a
vRealize Orchestrator action to run the script and retrieve the values.
n
Database Query Custom Property Denition on page 101
You add a custom property to query a database when you want to retrieve values from that database
to populate the custom property on the request form. The database custom property uses a
vRealize Orchestrator action to run the query and retrieve the values.
n
Custom Action Custom Property Denition on page 102
You add a custom property to retrieve data from a source using a custom vRealize Orchestrator action
when you want users to select the retrieved values in the request form.
Network Custom Property Definition
You add a custom property to retrieve network names from the vRealize Automation database when you
want users to select the network in the request form. The network selector custom property uses a
vRealize Orchestrator action to retrieve the values.
Limitations
Plan for the following limitations when you use the network selector custom property.
n
The name of the custom property must be VirtualMachine.network0.Name. This name is required. You
cannot create multiple property denitions for the network selector.
n
The action retrieves all the network names for the requesting user without validating that it applies to
the target vCenter Server instance. A service catalog user might select a network that is not applicable to
the selected target. If the wrong network is selected, the catalog request fails.
n
The action retrieves network names for the requesting user only. If you submit a request on behalf of
other users, the networks are for you. For example, Network A and Network C are associated with
Business Group 1, so the BG 1 users see only Network A and C, not B.
Custom Properties Reference
98 VMware, Inc.