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

A user in the Business Owner role in Cloud Manager is now able to delete a Sandbox Program from the landing page (via quick action button on Program card) or from within the program.

See Deleting a Sandbox Program for more details.

A Sandbox Program user in 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.

See Deleting a Sandbox Program for more details.

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.

Sandbox Programs are now identified by means of a Sandbox badge that is displayed on the program card on the landing page and 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 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.

See SysAdmin Tasks for more details.

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

See Managing Access to Author Instance for more details.

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.

In certain situations, the icons in the Create Program dialog were misaligned.

The AEM release identifier was not consistently displayed on the Programs Overview page.

When configuring the production pipeline, the Scheduled Deployment option was not visible for some customers.

Environments within a Sandbox program are hibernated when no activity is detected for a certain duration. This status is not observed in Cloud Manager. The status can, however, be observed by way of Developer Console. This ability will be addressed in an upcoming release.

The link to the Developer Console directly from Cloud Manager will not display the option to de-hibernate/hibernate a Sandbox Program’s environment. To address this, once at the Developer Console, add the pattern #release-cm-p1234-e5678 to the end of the url, where 1234 is the Program ID and 5678 is the Environment ID. This ability will be addressed in an upcoming release.