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.
The Release Date for Adobe Experience Manager as a Cloud Service 2021.4.0 is May 6, 2021.
The following release (2021.5.0) will be on May 27, 2021.
GraphQL Endpoints - it is now possible to enable the AEM GraphQL API for individual AEM Sites configurations and to create custom GraphQL endpoints for those configurations by using a new GraphQL Console UI. The UI also allows managing GraphQL endpoints.
Content Models, enhanced Date&Time data type - it is now possible to configure the Date&Time date type to allow authoring only date, only time, or date and time information.
Content Models, enhanced Tags data type - it is now possible to configure the Tags data type to allow authoring single or multiple tags.
Content Models, new Tab Placeholder data type - the new Tab Placeholder data type allows grouping data types into sections that will be rendered under tabs in the content fragment editor.
Content Fragments - moving content fragments or folders now updates nested references inside the fragment (CQ-4320815)
GraphQL - persisted queries now support user-defined endpoints that are specific to AEM Sites configurations (CQ-4315928)
Experience Manager does not archive single asset downloads where the original file is downloaded. This enhancement allows for faster downloads.
When an asset is downloaded via linkshare option, you can now choose to download or not download the renditions. Previously, all the asset renditions were downloaded.
Administrators can configure Experience Manager to delete the source of assets after doing a bulk asset ingestions. See bulk asset ingestion.
When executing a health check to import assets in bulk, Experience Manager now provides more information reasons for failures. See bulk asset ingestion.
When importing assets using bulk import tool, administrators now have the option to delete the source files after the import is successful. See bulk asset ingestion.
When editing a metadata schema, a new root path selector field allows administrators to quickly and easily make the selection, thereby reducing the configuration time.
Metadata of many assets can be imported in bulk using a CSV file and can be exported to a CSV file. The default date format is now
yyyy-MM-dd'T'HH:mm:ss.SSSXXX. Users can leverage a different format by updating the column header. For example, add
Date: DateFormat: yyyy-MM-dd'T'HH:mm:ssXXX as the column header in the CSV file instead of the word
When browsing assets in Column view, a visual indicator displays the approved or rejected status of each asset.
When browsing assets in Column view, a visual indicator displays for expired assets.
A text area data type is made available in Assets metadata editor. You can use this option to let your users input metadata in a free-form text field.
When attempting to move multiple assets or folders, an error is logged in the console and the move operation is not completed. Move operation fails if the title cannot be updated. (CQ-4322080)
A metadata field can be hidden based on a rule such that when a predefined condition is met the metadata is not mandatory. However, such hidden metadata fields are displayed as required fields. (CQ-4321285)
Bulk metadata import fails because of incorrect date format. (CQ-4319014)
When a selection is made in the Properties page to update metadata, the interface is slow to respond when there are many options provided by the schema. (CQ-4318538)
While updating and saving metadata value in a single-line text field, the values in the dropdown menu get deleted, even if edits are disabled on the dropdown menu. (CQ-4317077)
You can use ellipsis as an annotation to review assets. When a small ellipse is used, the ellipse overlaps with the number of the annotation in the print version. (CQ-4316792)
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. Read this blog post to learn about capabilities and features of AEM Forms as a Cloud Service.
Use Government ID identity authentication method in Adobe Sign enabled Adaptive Forms
Powered by advanced machine learning algorithms, Adobe Sign’s Government ID process empowers companies across the globe with the ability to secure a high-quality authentication of their recipient’s identity. Now, you can use Government ID identity authentication method in Adobe Sign enabled Adaptive Forms.
Government ID is a premium identity authentication method that instructs the recipient to upload the image of a government-issued identity document (driver’s license, national ID, passport), and then evaluates that document to ensure it’s authentic.
Support to use in-form signing experience for asynchronous adaptive form submissions
You can now use the in-form signing experience for asynchronous adaptive form submissions. You can also embed an adaptive form in an Experience Manager Sites page and use the in-form signing experience for adaptive form submissions.
Support to use a variable to specify an attachment while prepopulating an Adaptive Form for an Assign Task step
While prepopulating an Adaptive Form for an Assign Task step, you can now use a document type variable to select an input attachment for the Adaptive Form.
Support to use the literal option to set value for a JSON type variable
You can use literal option to set value for a JSON type variable in the set variable step of an AEM Workflow. The literal option allows you to specify a JSON in the form of a string.
Use local development environment to create Document of Record (DoR)
You can use an XDP as a Document of Record template on Cloud Service instances and AEM Forms as a Cloud Service SDK (Local development environment). Previously, the support was limited to Cloud Service instances only.
Support for category UID - This unlocks 3rd party commerce integrations for systems that use Strings for category ids
AEM extension for PWA Studio incl. example integration
New CIF navigation core component that extends WCM navigation core component
Visual indicator for staged catalog data in AEM storefront
Commerce endpoint is now configurable via Cloud Manager UI
This section outlines the Release Notes for Cloud Manager in AEM as a Cloud Service 2021.5.0 and 2021.4.0.
The Release Date for Cloud Manager in AEM as a Cloud Service 2021.5.0 is May 06, 2021.
The next release is planned for June 03, 2021.
The PackageOverlaps quality rule now detects cases where the same package was deployed multiple times, i.e. in multiple embedded locations, in the same deployed package set.
The repository endpoint in the Public API now includes the Git URL.
Deployment log downloaded by a Cloud Manager user will be more insightful and will now include details about failures and success scenarios.
Intermittent failures encountered while pushing code to Adobe git have now been resolved.
Commerce add-on can now be applied to Sandbox programs during the Edit program workflow.
The Edit program experience has been refreshed.
The Domain Names table in the Environment Details page will display up to 250 Domain names via pagination.
The Solutions tab in Add Program and Edit Program workflows will display the solution, even if only one solution is available for the Program.
The error message in the build step log when the build did not produce any deployed content packages was unclear.
On occasion, user may see a green “active” status next to an IP Allow List even when that configuration was not deployed.
Instead of removing ‘deleted’ variables, the pipelines variables API would only mark them with status DELETED.
Some Code Smell-type quality issues were incorrectly impacting the Reliability Rating.
Since wildcard domains are not supported, the UI will disallow the user from submitting a wildcard domain.
When a pipeline execution was started between midnight and 1am UTC the artifact version generated by Cloud Manager was not guaranteed to be greater than a version created the prior day.
During Sandbox program setup, once the project with sample code has been successfully created, Manage Git will appear as a link from the hero card in the Overview page.
The Release Date for Cloud Manager in AEM as a Cloud Service 2021.4.0 is April 08, 2021.
UI updates to the Add and Edit Program workflows to make it more intuitive.
A user with requisite permissions can now submit the commerce end point via the UI.
Environment variables can now be scoped to a specific service, either author or publish. Requires AEM Version
2021.03.5104.20210328T185548Z or higher.
The Manage Git button is displayed on the Pipelines card even when no pipelines have been configured.
The version of the AEM project archetype used by Cloud Manager has been updated to version 27.
Projects in the Adobe I/O Developer Console created by Cloud Manager can no longer be unintentionally edited or deleted.
When a user adds a new environment they will be informed that once an environment is created it cannot be moved to a different region.
Environment variables can now be scoped to a specific service, either author or publish. Requires AEM Version 2021.03.5104.20210328T185548Z or higher.
The error message when starting a pipeline when an environment was deleted has been clarified.
OSGi bundles provided by Eclipse projects are now excluded from rule
When editing the Experience audit page of a pipeline, an input path starting with a slash
( / ) will no longer result in the step being stuck in pending status.
When a new production pipeline is created, if no content audit override is added by the user, the default homepage was not audited.
Issues for the
CloudServiceIncompatibleWorkflowProcess had the incorrect severity in the downloadable issue CSV file.
Runmode check was producing false positives on non-folder nodes.
The Release Date for Content Transfer Tool v1.4.0 is May 11, 2021.
wipe=trueresulted in incorrect counter index on the target. This has been fixed.
The Release Date for Best Practices Analyzer v2.1.12 is April 12, 2021.