Product Communities

Within the Fields library you have columns:Name Type Instructions Display Type Active/DeactiveCurrently, there is no way to add a description column for fields. This makes it difficult to document important information about each field within the system.A description column would allow administrators and developers to include key details about a field, such as what the field represents, backend or integration-related notes, data source information, or other relevant technical context. This type of information is different from user instructions and is intended to provide internal documentation about the purpose or structure of the field.Having a dedicated description column would improve clarity, reduce confusion, and make it easier for teams to maintain and understand complex forms or datasets over time. It would serve as a central place to store field-specific metadata that is currently difficult to capture within the existing interface.

Request for Feature Enhancement (RFE) Summary: We would appreciate a capability in the Image component (including Hero/Carousel) to configure different images for desktop and mobile. Use-case: Authors set key visuals per device so that content remains legible and complete on smaller screens. Current/Experienced Behavior: It is not possible to switch images between smartphone and desktop. As a result, text in images may become unreadable on small screens, and key content can be cropped or cut off on mobile. Improved/Expected Behavior: Allow configuration of separate images for desktop and mobile. If either is not set, fall back to a common image for both. This would directly improve UX and reduce operational work, which would be very helpful. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):

Field Content Request for Feature Enhancement (RFE) Summary: We would be grateful for a feature to automatically retrieve the target file size and optionally display it in the link text (with an ON/OFF toggle). Use-case: When authors create links to files (e.g., PDFs), showing the file size in advance helps users make informed decisions (e.g., considering mobile data). Manual entry is time‑consuming and error‑prone. Current/Experienced Behavior: Automatic retrieval and display of file size is not available. Although displaying size improves usability (prevents unnecessary downloads and supports user decision‑making), maintaining sizes manually incurs operational cost and inconsistency risks. Improved/Expected Behavior: Automatically fetch the target file size and display it in the link text (with the ability to toggle display ON/OFF). This would stabilize operations and reduce effort—very helpful for large sites. Environment Details (AEM version/service pack, any other s

Request for Feature Enhancement (RFE) Summary: It would be very helpful if updates to Image Alternative Text were reflected immediately in the editor UI even when Show Image Caption is turned ON. Use-case: While authoring an Image block, authors enter or update Image Alternative Text in the properties panel. Current/Experienced Behavior: When Show Image Caption is ON, text entered in Image Alternative Text is sometimes not reflected immediately or disappears from the editor view (it only appears after a page reload or publish). Improved/Expected Behavior: The entered alternative text is consistently and immediately reflected in the editor UI and does not disappear. This would reduce verification effort during authoring and be much appreciated. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):

Feature / Enhancement RequestDescription of the Requested FeatureThe Ford .com team would like direct access to the execution logs produced by the AEM maintenance tasks VersionPurge and AuditLogPurge (plus any future purge-style tasks) without having to open a support ticket every time they need verification.Current Behavior• Both purge tasks execute in a dedicated maintenance pod.• Logs are stored internally and are not surfaced through Cloud Manager’s log download UI / API.• End customers therefore have no self-service method to confirm that their configuration changes (e.g., updated purge schedule) actually ran.• Support must manually retrieve and share CSV log extracts on request. Desired BehaviorExpose the maintenance-task logs to customers via one (or a combination) of the following:• Add the log files to the list of selectable log types in Cloud Manager ("Download Logs") for each environment.• Expose them through the existing Log API endpoints.• Alternative UI or API that allows

I had a specific requirement wherein when author is editing headless content, by publishing content fragment, the latest content must realtime, immediately show at clientside. Out of box cache mechanism only provided TTL based. So I combined few ways, cooking custom solution to clear graphql query cache. Explain my custom solution here. https://medium.com/@bsaravanaprakash/how-to-eagerpurge-persistedquery-cache-upon-cf-publish-8864e0419c5e

It will be great if we have in built feature in AEM assets to run PDF API services. Especially feature which has direct implication for websites. e.g. Tagged PDFs which is crucial for WCAG compliance.The way PDF API services are established, operations needs to be done in isolation via Adobe server or 3rd party service to process the PDFs. It will be great if we don’t have to leave AEM eco-system and perform these operations via workflows. 

Currently, if you open properties of a user accound, the assigned groups are listed randomly, there is no order. If a user has a bunch of assigned groups, it is very hard to search for those groups.  Request:Please sort them alphabetically - this would make it a lot easier!

Reference fields in CF models and in the Universal Editor’s Properties tab are fixed-width and use an odd font size in labels. The fixed width is quite limiting in the UE, it would be great to align the behaviour of reference fields with how other fields resize.A quick demo of the issue in is this video.

Hello, this is an enhancement request that the support team suggested I log here instead.I have an AEM Headless project with a decoupled Next.js frontend and components instrumented for the UE. Many components are containers that expect a certain structure of subcomponents. UE does not provide for instrumentation of such “precomposed” composite components, so all this inner substructure has to be tediously built out by authors. This is time-consuming and brings a learning curve: the authors don’t initially intuitively know which subcomponents are expected to go inside which container-type parent components.Obviously, we instrument the containers to only allow the right type of child components to be added, and in many cases a parent component only allows one specific type of child. Which is obvious to developers but not to authors, and here’s where the current behaviour of the Add (Plus) button gets in the way. If there is only one possible type of component that can be added, the Add

In Asset Essentials, when searching for assets using keywords and/or filters, the search results do not indicate the number of results (even the approximate number), unlike the Touch UI.The concern is that users do not know how many results are returned from on the search criteria and do not know if they need to refine the criteria.It would be a great addition if the number of results is displayed when searching for assets. 

Background:Currently if you start a translation for an existing page, a launch page of the target page will be created (under /content/launches). If editor recognizes that he picked up the wrong page, he will delete the project. An info box pops up and provides different options for clean up connected data related to the project.The created launches for update case is not included, so with deletion it will remain as orphaned ones (garbage) in the database as nobody will probably manually clean it up.Feature request:Just add a checkbox (default enable) which deletes connected launches pages. Benefit:No orphaned launches, no garbage in database, no manual todo for editors (which even do not know about the utilization of launches behind the scenes)   

The asset export metadata tool could use more customization to make the export simpler and more efficient.The properties to be exported dropdown only has 2 options: all and selective. The all selection exports all metadata properties. In our case, this results in 2000-3000+ columns in the excel sheet with the majority of them being blank. The selective option is not viable either because there are a couple hundred metadata properties we want included in the export which is too many to manually select.Since both of these options are not ideal, it would be beneficial to have some kind of in-between option, to be able to select metadata properties in bulk without having to select them individually or all at once.One solution could be to select which metadata schemas’ properties you would like exported. Also, if there was some way to save which properties were selected for a previous export, you would not have to re-select all of the properties each time time you want to export the metadat

I’m working on an Adobe project which uses almost 40 programs in Cloud Manager. All those programs trigger some notifications for deployment approvals, deployment started etc, but I’m only interested in two programs. Due to the large amount of these notifications, I basically every time miss the ones that are important to me. It would be great if Cloud Manager would allow filtering the notifications by program.The same applies to the events which we receive via the event hook / aws event bridge (https://developer.adobe.com/experience-cloud/cloud-manager/guides/api-usage/receiving-events/). Here it isn’t that problematic since we deployed a lambda function to filter the events, but filtering more than 90% of the events sounds like wasted resources on both sides.