Adobe Experience Manager

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.

Add a built‑in lifecycle engine in AEM Assets that automatically manages asset retention, archival, legal holds, license expirations, and recommended repurposing based on usage, metadata, and business rules. Key capabilities:Automatic rules engine to retire, archive, restore, or delete assets by usage, age, or license terms. License & rights tracker with expiry alerts and automatic enforcement (block publish, flag usage). Legal hold mode preventing deletion or archival for specified assets/collections. Usage-driven recommendations: suggest reuse, transcoding, or promotion based on analytics and similarity. Audit trail and impact analysis showing where an asset is used (pages, campaigns, syndications). Configurable workflows and notifications for stakeholders (legal, marketing, ops). API/webhooks for integration with MAM, PIM, CMS and governance systems.Business value:Cuts storage costs by archiving unused assets automatically. Speeds audits and reduces manual governance overhead. I

As Adobe continues to make significant strides in optimizing Assets, particularly through the use of Dynamic Media for delivery, many product teams have begun to utilize AEM assets as a centralized repository. This allows them to host all assets and distribute them across various downstream channels for utilization. The current challenge we face is the absence of reporting capabilities. There is no out-of-the-box (OOTB) reporting mechanism available when assets are referenced across multiple channels without the Dynamic Media embed code; instead, they are accessed through direct dynamic media URLs. Furthermore, it is not always feasible to rely on the DM embed code for asset usage. Therefore, we are seeking a feature that can provide insights into the usage of any asset when it is referenced on any channel.Is this capability on Adobe’s roadmap or planned as a feature enhancement? 

Current LimitationHEIC files can be uploaded and stored in AEM Assets, but:No thumbnails are generated No visual previews are available in the Assets UI Authors must download the file to view it This negatively impacts usability, discoverability, and editorial efficiency.AEM Assets should:Automatically generate thumbnails for HEIC files Generate standard preview renditions (similar to JPEG/PNG) Display HEIC previews directly in the Assets UI and picker dialogs Work out of the box in AEM as a Cloud Service Leverage existing asset processing pipelines (e.g. Dynamic Media or asset microservices) Respect existing permissions and renditions logicBusiness ValueImproved author experience: Editors can visually identify assets without downloads Operational efficiency: Faster asset selection and reduced friction in content creation Modern format support: HEIC is increasingly common on iOS devices and in creative workflows Reduced manual conversion: Avoids the need to pre-convert HEIC files outsi

The unique field validation is not functioning in the Universal Editor. Users can enter duplicate values without any checks. Unique fields are defined in the content fragment model.Expected behaviourThe system should validate that the field is unique in the Universal Editor. It should reject duplicate values. Or at least throw an error when editor add/patch this field in de CF.Actual behaviourThe system currently allows any value to be entered in the unique field without validation. Duplicate values are accepted.Steps to reproduceOpen the Universal Editor in Adobe.Navigate to the content fragment with the unique field (ID).Enter a value in the unique field.Enter the same value again in another unique field (ID).Observe that the system accepts the duplicate value.

Hi,Following this documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/detect-duplicate-assets for enabling the asset duplication detection, we are able to see a new message in the Touch UI’s inbox when the same asset has been uploaded to 2 different folders within the DAM.However, there are no new task created in the Asset Essentials’ task inboxWould it be possible to also have a new task created to the administrators in the Asset Essentials UI when duplicate assets are uploaded to the DAM?Regards,Henry

If you have a completed translation job, you can click on “Archive”. With that, the job is not displayed anymore in the UI. BUT there is also no chance to restore it - the word “Archive” indicates something completely different for the editor and this is, that he can restore it. So, currently it is same like “Delete Tile”. So, totally missleading options here.Request: Provide an option to restore archived jobs!   

Description:In AEM Guides as a Cloud Service, the XML Editor toolbar allows customization through ui_config.json and extension JSON for multiple actions.However, the Insert Relationship Table (reltable) action currently does not support overriding default values for:Header Rows Rows ColumnsFor our project, we need the relationship table to be inserted with the following custom defaults:Header Rows: 0 Rows: 2 Columns: 2At present, AEM Guides always inserts a relationship table with the hard‑coded defaults:Header Rows: 0 Rows: 1 Columns: 3These values cannot be overridden through any configuration methods.Current Limitation (Confirmed by Adobe Support):The relationship table insertion dialog does not read values from ui_config.json or the extension JSON. Default row/column values are hard‑coded in the product and cannot be changed. Only standard tables/simpletables support configurable default settings as per the 2502 release updates. Therefore, configuring relationship table defaults is

We recently completed our year‑end penetration testing for the application and identified a medium‑severity issue. The system does not restrict or sanitize PDF uploads that contain embedded JavaScript code. An attacker could upload a specially crafted PDF with embedded JavaScript, and if a privileged user later opens the PDF in a PDF reader, the JavaScript may execute within the reader process.As a remediation, can we block or reject PDF files that contain embedded JavaScript during upload?

Currently, if you delete an asset via new Assets UI [1] this will end up in the trash folder. From here, you are able to restore it easily.Although CF are stored below /content/dam this functionality is not there for CF! Why is that. CF are holding same important content (maybe more if delivered to different channels) like an asset. Why does Adobe not offer the function? Please implement the restore functionality for CF![1] 

Request for Feature Enhancement (RFE) Summary: Today if we select multiple pages in sites and then click edit, only one page will open in a new tab for authors to edit the page. We wanted the behaviour where, if an author selects multiple pages and click edit, all of them should open up in new tabs. Use-case: ease of authoring Current/Experienced Behavior: Today if we select multiple pages in sites and then click edit, only one page will open in a new tab for authors to edit the page. Improved/Expected Behavior: it should open multiple aem pages in multiple browser tabs Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 SP 20 Customer-name/Organization name: Dyson Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ability to delete workflow packages before maintenance task configuration is requested Use-case: A large number of unnecessary workflow packages used before setting maintenance tasks remain in the PROD environment, and some functions are unavailable due to timeouts. In addition, there is a significant impact on the performance of Timeline display.Specifically,・In order to display Timeline, the retention period of workflow archives must be set to one day.・Due to timeouts, the launch function cannot be used effectively, putting a heavy burden on authoring operations and scheduling. Current/Experienced Behavior: How to delete past workflow packages is not disclosed. In addition, there is no official tool or knowledge. Improved/Expected Behavior: Provide tools or publish knowledge to remove remaining workflow packages that cannot currently be removed Environment Details (AEM version/service pack, any other specifics if applicable):

Request for Feature Enhancement (RFE) Summary: Remove Content Fragment jcr:title from being included for translation by default when using option "Enable Model Fields for Translation" Use-case: For translation rules for CF I don't want to maintain rules in the translation_rules.xml file, instead I want to give just the creator of the CF Model the chance to define which fields should considered for translation by setting the field "translatable". With current situation creator of CF Model does in fact have NO full control as jcr:title is always translated (creating costs for translation that I do not want to pay. Hence feature is useless as I need to maintain my translation rules manually.  Current/Experienced Behavior: Even if I use the option "Enable Content Model Fields for Translation" to use the Translatable field of the Content Fragment Model in order to control which fields should be translated, the jcr:title of the CF is in by default. I can not exclude it and the

Request for Feature Enhancement (RFE) Summary:   Use-case: Summary:Walmart data custodians continue to expand our metadata usage within AEM Assets, and it is necessary to reflect those metadata fields in custom search forms. Currently, adding new metadata fields to the custom search interface requires code-level updates, as we are using the Group Predicate option to consolidate search facets into a dropdown. This slows down iteration and limits the ability of administrators to maintain and evolve search functionality in step with schema updates.   Current/Experienced Behavior: The Group Predicate (dam/gui/coral/components/admin/customsearch/searchpredicates/grouppredicate)—which is essential for logically grouping and structuring search filters—is not available through the AEM interface for manual configuration. While this predicate can be added through code, it cannot be added or preserved directly through the UI, leading to our business admins not being able to dir

Request for Feature Enhancement (RFE) Summary: Email service should implement an change event listener to re-read its oauth and refresh token properties when these gete updated ( /conf/global/settings/mailer/oauth) without the need of manual pod restart to re-read its value Use-case: Microsoft Azure oauth token is expiring every 90 days and its get automatically updated on author instance in AEMaaCS. This change is replicated to publish instances, but this change is ignored by the Email Service running on publish, because these properties are read only once when service gets initialized. So a manual restart of the pods is needed. Current/Experienced Behavior: When oauth token expired and gets updated with its new value all our form that send emails on all our live websites stop working, because the Email Service does not update its in memory value for that token, despite the fact that the token is already updated in the publish instance Improved/Expected Behavior: An event li

Request for Feature Enhancement (RFE) Summary: enable scrolling "no" property for pdf viewer component iFrame Use-case: We are using pdf viewer component in our application. By default in some resolutions we see scrollbars(Horizontal and Vertical) appearing in some resolutions. We are looking for property or config to hide this scrollbars.  Current/Experienced Behavior: Scrollbars appearing in some resolutions. Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Introduce property to hide toolbar display in pdf viewer Use-case: We are using pdf viewer component in our application. By default we see tools are displaying with file name. This is appearing for both Desktop and Mobile devices. But we don't want to show these tools in our component and looking for property to make it hidden if required. Current/Experienced Behavior: Tools, icons and file name displaying by default Improved/Expected Behavior: Make it option to show or hide Environment Details (AEM version/service pack, any other specifics if applicable): AEM on Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):