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

This page outlines the general release notes for Experience Manager as a Cloud Service 2020.4.0.

Release Date release-date

The release date for Experience Manager as a Cloud Service 2020.4.0 is April 9, 2020.

What’s New in Assets assets

Know about new features, enhancements, and bug fixes for Experience Manager Assets and Dynamic Media in the current release.

  • Brand Portal supports the asset distribution use cases for Experience Manager Assets. Brand Portal aids organizations to meet their marketing needs by securely distributing approved brand and product assets to external agencies, partners, internal teams, and resellers for download.

    • Brand Portal configuration is completed through Adobe I/O console. See configure Brand Portal.
    • Asset sourcing in Brand Portal is not yet supported with Experience Manager as a Cloud Service.
  • Adobe Asset Link v2.0 works with Experience Manager as a Cloud Service. Adobe Asset Link streamlines collaboration between creatives and marketers in the content creation process by connecting Experience Manager Assets with Creative Cloud desktop apps Adobe Photoshop, Adobe Illustrator, and Adobe InDesign via in-app Asset Link panel.

    • Experience Manager is pre-configured for Adobe Asset Link, which results in easy configuration and faster roll-out to creative professionals.
    • Asset Link now supports an Experience Manager environment switcher that allows creative users to easily connect to a different Experience Manager environment. An example where this functionality is useful is, for agency designers who work with multiple clients using different Experience Manager Assets deployments.
  • Users can configure post-processing workflows to auto-start in the folder Properties user interface for the specific folder hierarchies.

    • The folder Properties user interface is simplified, with new Asset Processing tab containing metadata profile, processing profile, and the new auto-start workflow configuration.

      Processing profiles can easily be applied to folders and all assets uploaded to folders are processing using these profiles

    • Asset reprocessing option allows to select a specific processing profile to reprocess user-selected assets in sub-folders.

      Reprocess selected assets using a specific processing profile

    • Dynamic Media: Added selective publish configuration so that assets are auto-published for secure preview only. Also, the assets can be explicitly published to Experience Manager without publishing to DMS7 for delivery in the public domain.

Bug Fixes assets-bug-fixes

  • Fixes for asset processing issues.
  • Fixes in Dynamic Media configuration and publishing assets to Dynamic Media delivery service.

What’s New in Cloud Manager whats-new-cloud-manager

  • Publisher URLs are now available from the Environment page in Cloud Manager UI.
  • Changes to navigation to allow user to edit, switch or add a program from Cloud Manager overview page.
  • Changes to allow user to Edit program from the program card on Cloud Manager landing page.
  • New pipeline status Pipeline Running displayed against the environment it is associated with.
  • Improvements to pipeline execution page comprehensibility. This includes display of Pipeline name (non-production pipeline only) and type, and a badge to indicate if the pipeline status is In Progress/Cancelled/Failed.
  • Tool tips to improve user experience and comprehensibility around why Add Program/Environment button is disabled.
  • Failed Environments can now be deleted through the UI and API.
  • The process used to generate git passwords has been made more resilient to issues in the underlying service layer.

Bug Fixes bug-fixes-cloud-manager

  • The links to the stage environment on the pipeline execution details page were not consistently navigating to the correct location.
  • Individual steps within the environment creation process would timeout earlier than necessary causing the process to fail.
  • The Maven configuration used in the build container was updated to avoid deadlocks when downloading artifact metadata.
  • In some cases, the Build Image step would fail to download customer packages successfully.
  • Certain infrequently occurring conditions would prevent environments from being deleted.
  • Experience Cloud notifications were not consistently received.