XaaS blueprints are migrated into two different types of VMware Cloud Templates depending on their details.

Before you can migrate a XaaS blueprint, the associated workflow must be migrated to 8 first. vRealize Automation 8 supports:
  • Request Form (Catalog item details and submitted request details are not supported)
  • Search field on Request form
  • Tree field on Request form
  • Conditional default values only support a single condition. If conditions are nested, the conditions are ignored during migration.
  • The read only, minimum length, and maximum length constraints value only supports constant values.
  • The field visiblity can be set both conditionally and externally using the form designer.

vRealize Automation 8 no longer includes or supports the Make Available as Component in Design Canvas functionality.

Before migrating, if the associated workflow is not compatible with vRealize Automation 8, save the XaaS blueprint as a draft to continue the migration assessment and migration without it.

XaaS Blueprints Without a Defined Provision Resource

vRealize Automation 7 XaaS blueprints without a defined provision resource are migrated to vRealize Automation 8 as XaaS Cloud Templates with the associated workflow and original request form fields. You might need to reorder the fields, as the fields' order is not preserved post migration.

XaaS Blueprints with a Defined Provision Resource

vRealize Automation 7 XaaS blueprints with a defined provision resource are migrated to vRealize Automation 8 as VMware Cloud Templates along with the associated workflow and original request form. They are no longer listed as an XaaS blueprint. vRealize Automation 8 requires these XaaS blueprints to have an assigned update workflow and destroy workflow. If the XaaS blueprint does not contain one, vRealize Automation 8 assigns a dummy id to these workflow fields. You must replace the dummy id and assign an update and destroy workflow post migration.
Note: The component lifecycle scalable functionality is not supported in vRealize Automation 8 and is flagged during the migration assessment.