Release Notes for Cloud Manager in Adobe Experience Manager as a Cloud Service 2020.6.0

Last update: October 31, 2024

CREATED FOR:

  • Admin

This page outlines the Release Notes for Cloud Manager in AEM as a Cloud Service 2020.6.0.

Release date

The Release date for Cloud Manager in AEM as a Cloud Service 2020.6.0 is June 04, 2020.

What’s new

  • A user with the Business Owner role in Cloud Manager can now delete a Sandbox Program directly from the landing page using the quick action button on the Program card. They can also delete it from within the program itself.

  • A Sandbox Program user in the Business Owner or Deployment Manager role in Cloud Manager is now able to delete their Production and Stage environment set via the Cloud Manager UI. The delete option is now available from both the Environment card on the Programs Overview page and the Environments page. Selecting the delete option on either Production or Stage also deletes the other in the set.

  • Coach marks on the landing page to inform and instruct the user about basic navigation.

  • Coach marks on the Program Overview page to inform and instruct the user about basic navigation inside Cloud Manager to get them started.

  • A LEARN page is now available in Cloud Manager, accessible via the top navigation. This page includes resources to help users learn about the most frequently used work-flows as relevant to their roles assigned in Cloud Manager.

  • A Sandbox badge now identifies Sandbox Programs, appearing on the program card on the landing page. It is also displayed next to the program name in the Program Overview page.

  • A user in the SysAdmin role now has one-click access to the location in the Admin Console from where user roles or permissions to Cloud Manager can be managed. A Manage Access button is now available on the landing page next to the Add Program button.

  • A user in the SysAdmin role now has one-click access to author instance directly from Cloud Manager.

  • The Build log now includes the list of discovered artifacts, including skipped content packages.

  • The Build step now validates that generated content packages include all mandatory properties – name, group and version.

  • The Build step now validates that the build produced at least one content package.