7.4

Issue Resolution
After you migrate from vRealize Automation 6.2.x to the latest
version, catalog items that use these property definitions appear
in the service catalog but are not available to request.
n
Control types: Check box or link.
n
Attributes: Relationship, regular expressions, or property
layouts.
In vRealize Automation 7.x, 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. For more
information, see Catalog Items Appear in the Service Catalog
After Migration But Are Not Available to Request.
Regular expressions used to define the parent-child
relationships in a vRealize Automation 6.2.x drop-down menu
are not supported in 7.x. In 6.2.x, you can use regular
expressions to define one or more child menu items that are
only available for a certain parent menu item. Only those child
menu items appear when you select the parent menu item.
After migration to 7.x , all the available menu items appear in the
child drop-down menu regardless of what you choose in the
parent drop-down menu. To show that previously defined
dynamic values no longer work, the first menu item in the child
drop-down menu reads "Warning! Use vRO workflows to define
dynamic values."
After migration, you must recreate the property definition to
restore the previous dynamic values. For information about
creating a parent-child relationship between the parent drop-
down menu and the child drop-down menu, see How to use
dynamic property definitions in vRA 7.2.
Migrating vRealize Automation to 7.4
VMware, Inc. 6