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

Dynamic Media Image Smart Crop and Swatch is now powered by latest Sensei services, that generates improved crops and swatches. Also, an enhancement has been launched to generate different crop content, for same aspect ratio but across different resolutions. In addition, any manual edits are preserved on reprocessing, if there is no change in the width and height in the Image Profile.

Smart Tags are automatically applied to the assets using asset microservices, instead of Smart Content Services. The underlying model is updated to improve tagging results and reduce bias.

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

• Generate documents by populating template files (PDF and XDP) with XML data.
• Generate output forms in various formats, including non-interactive PDF print streams.

The CIF add-on supports latest Commerce v2.4.3 with new GraphQL APIs and schemas

Authors can add links to product and catalog pages in text fields using the rich text editor (RTE). A CIF icon has been added to the RTE toolbar that opens up the pickers to quickly search and select the product or category without leaving the context.

Existing pop-up shopping cart and checkout have been replaced with dedicated AEM shopping cart and checkout pages. The components on these pages are built using Adobe Commerce’s extensible Peregrine components

Merchants can hide certain product catalog categories in the navigation using the Commerce backend. The CIF Navigation Core Component respects the commerce backend configuration “include in menu” to show / hide categories in navigation

AEM Storefront Venia returns HTTP 404 error if category or product page is not found

Users can now use new Front End pipelines to exclusively deploy front end code in an accelerated manner. See Cloud Manager Front End Pipelines to learn more.

Code Quality pipeline duration is significantly reduced by performing the code analysis in a more efficient way without the need of building a whole AEM image. This change will roll out progressively over the weeks following the release.

The Git Commit ID will now be displayed in the pipeline execution details making it easier to track the code that was built.

Program Creation is now available via publicly exposed API.

Environment Creation is now available via publicly exposed API.

The x-request-id response header is now visible in the API Playground on www.adobe.io. This header is useful when submitting customer care issues for troubleshooting.

As a user, I see Pipeline card with zero pipelines provide me with appropriate guidance.

A new Activity Page is now available where activities such as pipeline and code executions can be viewed along with their associated details. Over time, the activities listed in this page will expand in scope along with the details provided.

A new Pipelines page with an on-hover, status popover for easy view of the summary of details is now available. Pipeline executions can be viewed along with their associated details.

The Edit Pipeline API now supports changing the environment used in the deploy phases.

An optimization in the OakPal scanning process has been introduced for large packages.

The quality issue CSV file will now contain the timestamp for each quality issue.

Certain unorthodox build configurations resulted in unnecessary files being stored in the pipeline’s Maven artifact cache which resulted in extraneous network I/O when starting and stopping the build container.

Pipeline PATCH API fails if deploy phase does not exist.

The ClientlibProxyResourceCheck quality rule was producing false positive issues when there were client libraries with common base paths.

Error message when max number of repositories has been reached did not specify the reason for the error.

In rare cases, pipelines were failing due to inappropriate retry handling of certain response codes.

In preparation for some upcoming changes, existing deployment pipelines will now be referenced and labelled in the user interface as Full Stack pipelines.

Pipeline card has been refreshed to now display a single, integrated face that shows both production and non-production pipelines, and user can select Run/Pause/Resume directly from the action menu associated with each pipeline.

A user in Deployment Manager role can now delete Production pipeline in a self-service manner via the UI.

Add and edit pipeline experiences have been refreshed to now use familiar, modern modals.

Users of Cloud Manager can now submit feedback directly from the user interface via the Feedback button on top right of the landing page.

Yearly SLA Graphs can now be downloaded from the Cloud Manager’s user interface.

Code quality and non-production pipeline executions will now use a more efficient shallow cloning process during the build step, leading to a faster build time for customers with especially large git repositories.

Add IP Allow List wizard will now inform the user if maximum allowed number of IP Allow Lists has been reached.

The Cloud Manager API documentation now includes an interactive playground that allows logged-in users to experiment with the API from their browser. See Cloud Manager API Playground for more details.

The tool tip on the Program card will be more descriptive if a selection option under ‘Navigate To’ is disabled. It now displays “A production environment does not exist.”

In rare situations, when an Adobe staff would restore a customer’s environment, the restore was considered complete before the environment was fully operational.

Certain internal requests made during environment creation were not being retried.

If deployment failed error occurs following domain name verification, the error message has been corrected to request the customer to contact their Adobe representative.

Ability to detect and report on node name length.

Ability to detect and report on the total Index size.

Ability to detect and report on assets that are missing their original rendition.