VMware Aria Automation 8 includes these custom resource considerations.
When migrating XaaS Custom Resources, only the original fields are migrated. Any user added fields or tabs are not migrated and must be added post migration. Any vRealize Automation 7 plugins used in your custom resources must also exist in VMware Aria Automation 8. If the custom resource contains a plugin that is not supported in VMware Aria Automation 8, you must unpublish the associated XaaS blueprint to exclude it from migration.
These plugins, fields, and views are not supported in VMware Aria Automation 8:
- VCAC/VCACCAFE plugin
- Resource List view
- Submitted Action details
