Current Release Notes for Adobe Experience Manager as a Cloud Service

Last update: 2024-02-22

The following section outlines the general Release Notes for the current (latest) version of Experience Manager as a Cloud Service.


From here you can navigate to release notes of previous versions; for example, for those in 2020, 2021 and so on.


See Recent Documentation Updates for details of documentation updates not directly related to a release.

Release Date

The Release Date for Adobe Experience Manager as a Cloud Service 2021.3.0 is March 25, 2021.
The following release (2021.4.0) will be on April 29, 2021.

Adobe Experience Manager Sites as a Cloud Service

  • A Progressive Web App (PWA) version of a site can now be enabled at the project level via simple configuration.
  • Content Fragment Model Extensions - now possible to define multi-line text data types as multi-field lists.
  • Content Fragment Editor UX Enhancements - nested child fragments now displayed in breadcrumb, and improved view of publish, save, and save&exit actions

Adobe Experience Manager Assets as a Cloud Service

What is new in Assets

  • Experience Manager extends the Connected Assets functionality to support use of Dynamic Media images in the supported core components. See use Connected Assets.
  • Experience Manager administrators can schedule bulk asset ingestions at a specific date or time. Also, administrators can schedule recurring ingestions based on date and time. See bulk asset ingestion.

Bug fixes in Assets

  • The copyright page does not display when attempting to download multiple rights-managed assets. (CQ-4314403)
  • When choosing to edit an INDD file, the resolution changes unexpectedly. (CQ-4317376)
  • Only the last page of the InDesign Template is there in the PDF Rendition. (CQ-4317305)
  • Tag picker takes long to open when the picker is part of a complex metadata schema. (CQ-4316426)
  • When uploading asset with same filename as an existing one, the name conflict dialog does not display to prompt the user to create a version. (CQ-4315424)
  • Folder Metadata Properties can be set and saved from the pop-up menu in a folder’s Properties page. While the selection is saved in the repository, it is not displayed when the Folder Metadata Properties are opened again. (CQ-4314429)
  • Assets with filenames containing spaces or special characters get uploaded using the browser. (CQ-4318381)

Adobe Experience Manager Forms as a Cloud Service

AEM Forms has helped many organizations deliver great onboarding and enrollment experiences over the years. These experiences have helped organizations convert leads to sales, process captured customer data, deliver responsive experiences based on the audience profile, and much more. Now, AEM Forms is available as a cloud service.

You can use AEM Forms as a Cloud Service to create digital forms, connect forms to existing data sources, integrate forms with Adobe Sign to add e-signatures to forms, generate Document of Record (DoR) to archive submitted forms as PDF files. The service can also convert your existing PDF forms to digital forms. In addition to standard AEM Forms features, the service offers several cloud-native capabilities like auto-scaling, zero downtime for upgrades, and cloud-native development environment.

You can reach out to your Adobe representative for a demo or to sign up for the service.

Adobe Experience Manager Commerce as a Cloud Service

What is New

  • Support for Adobe Commerce 2.4.2

  • Product detail component can now be used and configured on any content page

  • Released CIF Venia Reference Site - 2021.03.25 that includes the latest CIF Core Components version v1.9.0. See CIF Venia Reference Site for more details.

  • Released CIF Core Components v1.9.0. See CIF Core Components for more details.

Cloud Manager

This section outlines the Release Notes for Cloud Manager in AEM as a Cloud Service 2021.3.0.

Release Date

The Release Date for Cloud Manager in AEM as a Cloud Service 2021.3.0 is March 11, 2021.
The next release is planned for April 08, 2021.

What’s New

  • Customers with environments with pre-existing Custom Domain Name configurations for IP Allow Lists, SSL Certificates and Custom Domain Names see a message about their previously existing configurations and can self-serve by way of the user interface.

  • Users with requisite permissions can now edit a Program, allowing them to do the following in a self-service manner:

    • Add Sites solution to an existing program with Assets or conversely.
    • Remove Sites or Assets from an existing program with both Sites and Assets.
    • Add second, unused solution entitlement either to an existing program or as a new Program.
  • AEM Push Update label will now be displayed for both Pipeline Execution and Activity screens.

  • If an environment is hibernated but there is also an AEM update available, the Hibernated status will take precedence over Update available.

  • Users can now see their Cloud Manager role(s) by selecting the ‘View Cloud Manager Role(s)’ option after navigating to the User Profile icon (top right) of Unified Shell.

  • The label Application for Approval has been relabeled to Production Approval for greater clarity.

  • The Version label has been relabeled to Git Tag in the Production pipeline execution screen.

  • The labels which define the behavior when important metrics do not meet the defined threshold have been relabeled to reflect their true behavior: Cancel Immediately and Approve Immediately.

  • The class and method deprecation lists have been updated based on version 2021.3.4997.20210303T022849Z-210225 of the AEM Cloud Service SDK.

  • Cloud Manager Production pipeline will now include Custom UI Testing capability.

Bug Fixes

  • Package versioning was skipped in some cases during AEM push upgrade.

  • Some quality issues were not properly discovered when packages were embedded in other packages.

  • In obscure situations, the default program name generated upon opening the Add Program dialog could be a duplicate of an existing program name.

  • On occasion, if user navigates away from pipeline execution page immediately after starting a pipeline, an error message is displayed stating that the action failed, although the execution actually starts.

  • The build step was unnecessarily restarted when customer builds resulted in invalid packages.

  • On occasion, user may see a green “active” status next to an IP Allowlist even when that configuration was not deployed.

  • All existing production pipelines are automatically enabled with the Experience Audit step.

Content Transfer Tool

Release Date

The Release Date for Content Transfer Tool v1.3.4 is March 19, 2021.

Bug Fixes

  • CTT was skipping content from folders with the same name but with a hyphen in the name. This has been fixed.

Release Date

The Release Date for Content Transfer Tool v1.3.0 is March 04, 2021.

What is new in Content Transfer Tool

  • CTT now installs to /apps instead of /libs Browser bookmarks to certain pages may no longer be valid.
  • When CTT is installed, user will have to navigate an additional level to get to the Content Transfer page. See Using Content Transfer Tool for more details.

Bug Fixes

  • When migrating content from a specific path, CTT was pulling in unrelated resources. This has been fixed

Best Practices Analyzer

Release Date

The Release Date for Best Practices Analyzer v2.1.8 is March 22, 2021.

What is new in Best Practices Analyzer

  • Ability to filter out ACS Commons findings from the BPA report in the user interface and from the report exported as a CSV file.

Code Refactoring Tools

What is new in Code Refactoring Tools

  • New features and enhancements for Repository Modernizer. See GitHub Resource: Repository Modernizer for the latest version.

    • Normalize OSGi configs (except RepoInit configs) to the preferred .cfg.json format.
    • Rename OSGi config folders to the specified format.
    • Generate the ui.apps.structure project.
    • Create the analyze module.
  • New features and enhancements for Dispatcher Converter. See GitHub Resource: Dispatcher Converter

    • Creation of separate files for different inclusions instead of in lining the content.
    • Ability to handle both folder path of vhosts and path to vhost files.
    • Generation of farm files with large customer configurations in range of 600 and more.

On this page