The following section outlines the general Release Notes for Experience Manager as a Cloud Service 2020.10.0.
The Release Date for Adobe Experience Manager as a Cloud Service 2020.10.0 is October 28, 2020.
The following release (2020.11.0) will be on December 1, 2020.
DataLayerBuilder utility to simplify Adobe Data Layer integration in custom components. See the list of changes in 2.12.0.
Project Archetype 24: The recommended foundation to start a new Experience Manager project got better. It now includes the new Adobe Client Data Layer, option to deliver site in AMP, and new extension points to add project CSS/JS.
ContextHub Folders: Ability to create audience folders to easily organize, find, and select audience segments to use for ContextHub offer targeting capabilities.
Adobe Sensei powered video smart tagging: By applying AI models to analyze video content for object and action-specific tags, DAM users can spend less time adding tags and more time using the exposed, rich information. In turn, you deliver the right experience to customers. See Smart tag video assets.
Brand Portal enhancements: The following new features and more are available in Brand Portal. For details, see Brand Portal release notes.
Adobe Asset Link version 2.1: A new version of Adobe Asset Link extension for Adobe Photoshop, Adobe Illustrator, and Adobe InDesign is available. It adds compatibility with the latest Adobe Creative Cloud applications with version 2021, released in October 2020.
Assets WebP file support: Assets as a Cloud Service now supports WebP image format. WebP is an emerging image format created by Google. Images in WebP file format are visually indistinguishable from JPG or PNG files and the files are much smaller. Lowered file size of assets improves the page-load times and help content creators deliver a faster web experience. See how to use WebP in create processing profile.
You can write to firstname.lastname@example.org to sign up for the beta program.
Released CIF Venia Reference Site - 2020.10.2 that includes the latest CIF Core Components version v1.4.0. Refer to CIF Venia Reference Site for more details.
Released CIF Core Components v1.4.0. Refer to CIF Core Components for more details.
GraphQL requests that were in the Product Console and Pickers were done by way of HTTP POST. This issue has been fixed to ensure that the Apollo GraphQL client respects the setting in the GraphQL client OSGi configuration to support GET requests if configured.
CIF Cloud config UI displayed “Save & Close” buttons for configs in /lib and /apps/. But these interfaces are read-only hence UI fixed to display “Close” button only.
The Release Date for Cloud Manager in Experience Manager as a Cloud Service 2020.10.0 is October 02, 2020.
The Environments page has been redesigned.
Hibernated environments now show a discrete status in Cloud Manager when they are hibernated.
The Cloud Manager “build container” now supports compiling projects using either Java™ 8 or Java™ 11. Support for Java™ 11 is provided by the Maven toolchains system.
The number of environment variables per environment has been increased to 200.
The Environment card on the Overview page now lists up to three environments. Users can select the Show All button to navigate to the Environment summary page to view a table with a complete list of environments.
Refer to Viewing Environment 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 buttons 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 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.
Learn more about what is new and the updates for Content Transfer Tool Release v1.1.12.