Migration creates a single, default policy in the target vRealize Automation system that is configured to require only the approval of the business group manager. The migration process adds the approval policy to each catalog item entitlement for each blueprint that had an approval configured in the source system.

Blueprint approval settings such as machine resource settings for CPU, memory, and storage are not migrated. However, approval information is captured in the pre-migration report. Reference the pre-migration report when you recreate approvals in the target vRealize Automation system.

You can recreate approval policies after pre-migration and before migration by using information in the pre-migration report. Otherwise, you can recreate approval policies after migration. For more information, see Recreating Approval Policies.

The following approval policy considerations apply to migration:

  • The pre-migration tasks creates the default approval policy.

  • The default approval policy name is Default Approval Policy for Migration.

  • The default approval policy is entitled.

  • Policy is defined separately from blueprints in the target system.

  • Approval policies are linked to entitlements.

  • The default policy that is created during migration is linked to each blueprint for which a policy was defined in the source vCloud Automation Center 5.2 system.

  • You cannot edit activated approval policies.

  • You can deactivate approval policies, but you cannot delete them.

The default approval policy that is created during migration contains the following field entries:

  • Name: Default Approval Policy for Migration

  • Description: Default Policy one level of business group manager

  • Status: Active

  • Levels: 1 approval level

For information about how to create and use approvals and approval policies in the target system, see Tenant Administration in the vRealize Automation documentation.