2024.1.0 Release Notes for Adobe Experience Manager as a Cloud Service
- Applies to:
- Experience Manager as a Cloud Service
- Topics:
- Release Information
CREATED FOR:
- Admin
The following section outlines the feature release notes for the 2024.1.0 version of Experience Manager as a Cloud Service.
Release Date
The release date of Adobe Experience Manager as a Cloud Service current feature release (2024.1.0) is January 25, 2024. The next feature release (2024.3.0) is planned for April 11, 2024.
Maintenance Release Notes
You can find the latest maintenance release notes here.
Release Video
Have a look at the January 2024 Release Overview video for a summary of the features added in the 2024.1.0 release:
Experience Manager Sites as a Cloud Service
Extension Manager in AEM Sites
Explore the new Extension Manager in AEM Sites to personalize your AEM setup by configuring UI extensions.
The Extension Manager in AEM Sites enables developers and practitioners to access, manage, and customize UI extensions built with Adobe App Builder to enhance the functionality of AEM Sites.
With the Extension Manager, you can:
- Enable or disable extensions on a per-instance basis;
- Configure extension parameters;
- Preview extensions and generate a shareable preview link;
- Discover UI extensibility features via interactive demos;
- Access Adobe’s experimental features through first-party extensions.
We are actively seeking feedback and new use cases for UI extensions. If you would like to connect, please send an email to uix@adobe.com
.
Experience Manager Assets as a Cloud Service
Admin view prerelease features
Preview renditions for all supported video types
Experience Manager Assets now generates preview renditions of all supported video types by default without requiring a processing profile configuration
Assets view
Smart tags blocklist
Assets Essentials now enables you to define blocklist that comprises words that should not be added as Smart Tags to assets when they are uploaded to the repository. This capability helps you to maintain brand compliance and reduces effort to moderate Smart Tags.
Experience Manager Forms as a Cloud Service
Early Adopter Program
-
Submit an Adaptive Form to Adobe Workfront Fusion Scenario: Forms as a Cloud Service offers an out-of-the-box options to effortlessly connect an Adaptive Form with Adobe Workfront. This simplifies the process of submitting an Adaptive Form to an Adobe Workfront scenario, allowing you trigger a Workfront Fusion scenario on submission of an Adaptive Form.
-
Right to left languages support: Adaptive Forms built on Core Components can now be presented in a Right-to-Left (RTL) language like Arabic, Persian, and Urdu. The RTL languages are spoken by over 2 billion people globally. Using a form in RTL language allows you to extend the reach of your adaptive forms to cater to these diverse audiences and select into RTL markets. In certain regions, it’s also a legal mandate to provide forms in the local language. By accommodating local languages, you not only open doors to a broader audience but also ensure compliance with relevant laws and regulations.
-
Protect your documents with DocAssurance APIs (Part of Communication APIs): The DocAssurance APIs empower you to safeguard sensitive information by signing and encrypting the documents. Through encryption, the contents of a document are transformed into an unreadable format, ensuring that only authorized users can gain access. This fortified layer of protection not only shields valuable data from unauthorized eyes but also provides peace of mind. The Signature APIs let your organization protect the security and privacy of Adobe PDF documents that it distributes and receives. This service uses digital signatures and certification to ensure that only intended recipients can alter documents.
You can write to
aem-forms-early-adopter-program@adobe.com
from your official email id to join the early adopter program and request access to the capability. -
You can leverage the Real Use Monitoring (RUM) Data Service to enable client-side collection for AEM as a Cloud Service.
Real Use Monitoring (RUM) Data Service offers a more precise reflection of user interactions, ensuring a reliable measure of website engagement. It is a great opportunity to gain advanced insights into your page performance. While this is beneficial for customers who use either Adobe-managed CDN or non-Adobe-managed CDN. Additionally, for customers using a non-Adobe managed CDN, automated traffic reporting can now be enabled for them, thus removing the need to share any traffic report with Adobe.If you are interested in testing this new feature and sharing your feedback, please send an email to
aemcs-rum-adopter@adobe.com
, along with your domain name for each of the environments that you would like to enable RUM for from your email address associated with your Adobe ID. Adobe’s product team will then enable the Real Use Monitoring (RUM) Data Service for you.
Experience Manager as a Cloud Service Foundation
Support for Dynatrace
Dynatrace customers may monitor their AEM usage. Read how to request connectivity with your Dynatrace environment for application performance monitoring. Note that New Relic APM, which is available to all customers, will stop collecting data if Dynatrace is enabled.
RDE Support for Front-End Code using Site Themes and Site Templates: Early Adopter Program
Rapid Development Environments (RDEs) now support front-end code based on site themes and site templates, for early adopters. With RDEs, this is done using a command line directive, rather than a front-end pipeline. Please reach out to aemcs-rde-support@adobe.com to try it out and provide feedback.
Domain Mapping Early Adopter Program
In addition to the recently released Traffic Filter Rules, which includes the optionally licensable Web Application Firewall (WAF) rules, there’s an opportunity to use the Configuration Pipeline to declare and deploy other types of CDN configuration. Join the early adopter program by emailing aemcs-cdn-config-adopter@adobe.com to gain access to:
- 301/302 client-side redirects
- proxying requests at the edge to arbitrary origins
- URL transformations
- setting or modifying request or response headers
- custom error pages when the CDN can’t reach AEM