Release Notes for Adobe Experience Manager as a Cloud Service 2020.7.0
The following section outlines the general Release Notes for Experience Manager as a Cloud Service 2020.7.0.
The release date for Experience Manager as a Cloud Service 2020.7.0 is July 30, 2020.
Adobe Experience Manager Sites as a Cloud Service
Experience Manager as a Cloud Service connectors for Adobe Target and Adobe Analytics are enhanced in the following ways:
- A new user interface implementation replaces the implementation based on the Classic UI.
- Configurations are now stored in /conf rather than /etc/cloudsettings in the Experience Manager repository.
Adobe Experience Manager Assets as a Cloud Service
What is new in Assets
- Asset Compute Service is a scalable and extensible service to process assets. Administrators can configure Experience Manager to invoke custom applications created using the Asset Compute Service. Developers can use the service to create specialized custom applications that cater to complex use cases. This web service can generate thumbnails for different file types, high-quality image renderings from Adobe file formats, encode videos (future), extract metadata, extract full text as precursor for indexing, and run an asset through all available Sensei services. see use asset microservices and processing profiles .
- The initial configuration of Dynamic Media in Experience Manager as a Cloud Service is improved to be more robust. It now provides progress of the processes to the administrators.
- Publishing of assets to Dynamic Media is simplified and made more robust by making it an integral part of overall asset processing pipeline using asset microservices and improving the batch publishing backend.
- Workflow steps that are not compatible with a Cloud Service deployment are now marked with a warning in the workflow model editor. Additionally, when executing the existing workflows on Cloud Service environment, the incompatible workflow steps are skipped.
- Workflow models created by customers that are deployed to /conf/global in the Git project associated with the environment in Cloud Manager are automatically deployed to /var and thus available in Experience Manager. The product workflow models under /libs that were changed by customer are not automatically deployed to /var .
- The Move Asset wizard does not load as expected for the assets that are included in Collections. (CQ-4296756)
- The values of dam:size and dam:sha1 are excluded from XMP writeback. (CQ-4237355)
- When unpublishing assets in bulk, Brand Portal generates an error suggesting that the request URI is too long. (CQ-4299474)
Adobe Experience Manager Commerce as a Cloud Service
AEM Commerce is now available on Cloud Service.
Refer to Getting started with AEM Commerce as a Cloud Service for more details.
Release 2.11.0 of the AEM Core Components is now available as part of AEM Sites including:
- Introduction of a new PDF Viewer Component .
- Accelerated Mobile Pages (AMP) support of Core Components is now available. It helps to produce faster customer experiences by making the page transition instantaneously when entering the site from a Google mobile search result, which improves user engagement and SEO. Refer to AMP Support for the Core Components for more details.
- Compatibility with version 1.0.2 of the Adobe Client Data Layer .
- Bug fixes and code quality improvements.
The Release Date for Cloud Manager Version 2020.7.0 is July 09, 2020.
- The environments page has been redesigned.
- Hibernated environments now show a discrete status in Cloud Manager when they are hibernated.
- The number of environment variables per environment has been increased to 200.
- Cloud Manager pipelines now support customer-set variables and secrets.Refer to Pipeline Variables for more details.
- Authentication-bound Private Maven Repositories are now supported.
- The Cloud Manager build container now supports both Java 8 and Java 11. Refer to Using Java 11 Support for more details.
- The link from Cloud Manager to the Developer Console was incorrectly active before environments were fully created.
- The link to the Developer Console directly from Cloud Manager did not display the option to de-hibernate/hibernate a Sandbox Program's environment.
- The Cancel and Save options on the Non-Production Pipeline edit page were not always visible.
- Certain failures in the code quality process could result in the log file not being generated correctly.
- When creating a new program, the suggested name would sometimes return a duplicate of an existing program name.
- Some large pipeline step logs could not be consistently downloaded through the user interface.
- The validation of environment names had an off-by-one error.
- The Environments page would sometimes show publish and dispatcher segments when none was present.
- Due to a change in how code coverage is calculated, the minimum version of the Jacoco plugin is now 0.7.5.201505241946 (released May 2015). Customers explicitly referencing an older version receive an error message in the code quality process.
Adobe Experience Manager as a Cloud Service Foundation
- Logs can be forwarded to Splunk accounts , which allows organizations to leverage their Splunk investment.
- A static, dedicated egress IP address can be assigned for outbound traffic programmed in Java code, which may be useful for some integrations.
- Ported AEM Analytics cloud service UI from Classic UI to new AEM UI. Also moved location of Analytics cloud service in AEM repository from /etc to /conf , to align with other AEM cloud services.
- Ported AEM Target cloud service UI from Classic UI to new AEM UI. Also moved location of Target cloud service in AEM repository from /etc to /conf , to align with other AEM cloud services.
Cloud Readiness Analyzer
Follow this section to learn about what is new and the updates for Cloud Readiness Analyzer Release v1.0.2.
- Earlier version of the CRA could not be run on Adobe Experience Manager (AEM) 6.1. Explicit support to allow users in the administrators group was added.Refer to Installing CRA on AEM 6.1 for more details.
- The expiration timestamp displayed on the summary report was incorrect.
- CRA was detecting duplicate custom components.
- On AEM 6.1, the content inspection was exiting before completing the full inspection. Exception handling was added to allow the inspector to skip and continue until the full inspection is completed.