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

Preview Service will be deployed on a rolling basis to all Programs. Customers are notified in-product when their Program is enabled for Preview Service. See Accessing Preview Service for more details.

Maven Dependencies downloaded during the build step will now be cached between pipeline executions. This feature will be enabled for customers over the next several weeks.

The name of the program can now be edited through the edit program dialog.

The default branch name used during both project creation and in the default push command via manage git workflows has been changed to main.

Edit program experience in the UI has been refreshed.

The quality rule ImmutableMutableMixCheck has been updated to classify /oak:index nodes as being immutable.

The quality rules CQBP-84 and CQBP-84--dependencies have been consolidated into a single rule. As part of this consolidation, the scanning of dependencies more accurately identifies issues in third-party dependencies which are being deployed to the AEM runtime.

To avoid confusion, the Publish AEM and Publish Dispatcher segment rows on the Environment Details page have been consolidated.

A new code quality rule has been added to validate the structure of damAssetLucene indexes. See Custom DAM Asset Lucene Oak Indexes for more details.

Environment details page will now display multiple domain names for Publish and Preview services (as applicable). See Environment Details to more details.

JCR node definitions containing a newline after the root element name were not correctly parsed.

List repositories API would not filter deleted repositories.

An incorrect error message was displayed when an invalid value was provided for the schedule step.

On occasion, user may see a green active status next to an IP Allow List even when that configuration was not deployed.

Some program editing sequences could result in the inability to create or edit the production pipeline.

Some program editing sequences could result in the Overview page displaying a misleading message to re-execute program setup.

Content Automation functionality lets Experience Manager Assets use the Adobe Creative Cloud APIs to automate asset production at scale. It improves content velocity by dramatically decreasing the time taken and iterations required to create variations of same asset. The functionality does not require any code and works from within the DAM.

Adobe Asset Link v3.0 for Adobe Photoshop, Adobe Illustrator, and Adobe InDesign and Adobe Asset Link v2.0 for Adobe XD is released. It provides:

• Support for Assets Essentials.
• Ability to automatically connect to Experience Manager as a Cloud Service or Assets Essentials.

AEM Forms as a Cloud Service - Communications: Communication APIs helps you combine XDP templates and XML data to generate print documents in various formats. The service lets you generate documents in synchronous mode. The APIs enables you to create applications that let you:

• Generate final form documents by populating template files with XML data.
• Generate output forms in various formats, including non-interactive PDF print streams.
• Generate print PDFs from an XFA form PDF and Adobe Acrobat Form (AcroForm).

Variable Data Externalizer: You can save data of AEM Workflow variables on an external storage system managed by your organization.

Bulk Device Registration Management means that provisioning massive amounts of player devices is faster and more efficient.

Improved search and filter options for each of the Device, Display, and Channel inventory views.

Device heath snapshot saves time by providing critical status as a glance.

Object details page offers a summary of the most relevant information for each object in your project.

Support for an optional pre-copy step added to use with CTT. The pre-copy step can be used to significantly speed up the extraction and ingestion phases of the content transfer activity when the source AEM instance is configured to use an Amazon S3 or Azure Blob Storage data store.

Guardrail added to CTT to prevent users from stopping an ingestion and potentially corrupting data once it has reached the critical point during the ingestion phase.

Extraction logs made more descriptive to help with troubleshooting.

Added more descriptive ingestion status messages in the UI.

Ability to detect and report on missing child nodes in folders under /content/dam.

Ability to detect and report on the version of Best Practices Analyzer used.