7.3

Table 6‑3. Target vRealize Automation Infrastructure Nodes
Log Location
Migration log
C:\Program Files (x86)\VMware\vCAC\InstallLogs-
YYYYMMDDHHMMXX\Migrate.log
Validation log
C:\Program Files (x86)\VMware\vCAC\InstallLogs-
YYYYMMDDHHMMXX\Validate.log
Catalog Items Appear in the Service Catalog After
Migration But Are Not Available to Request
Catalog items that use certain property definitions from prior versions appear in the service catalog but
are not available to request after migrating to the latest version of vRealize Automation.
Problem
If you migrated from a 6.2.x or earlier version and you had property definitions with these control types or
attributes, these elements are missing from the property definitions and any catalog items that use the
definitions do not function as they did before you performed the migration.
n
Control types. Check box or link.
n
Attributes. Relationship, regular expressions, or property layouts.
Cause
In vRealize Automation 7.0 and later, the property definitions no longer use these elements. You must
recreate the property definition or configure the property definition to use a vRealize Orchestrator script
action rather than the embedded control types or attributes.
Migrate the control type or attributes to vRealize Automation 7.x using a script action.
Solution
1 In vRealize Orchestrator, create a script action that returns the property values. The action must
return a simple type. For example, return strings, integers, or other supported types. The action can
take the other properties on which it depends as an input parameter.
2 In vRealize Automation console, configure the product definition.
a Select Administration > Property Dictionary > Property Definitions.
b Select the property definition and click Edit.
c From the Display advice drop-down menu, select Dropdown.
d From the Values drop-down menu, select External Values.
e Select the script action.
f Click OK.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 63