Build better products with our product team
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): AEM aa CS Customer-name/Organization name: Panasonic (Org Name: panasonicglobal) Screenshot (if applicable): - Code package (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 therefore is creates unnecessary costs. This makes no sense, as on the one hand you handover the control for translatable fields on creator of the Content Fragment Model, on the other hand you define the jcr:title to be translated by default with no option to control. See: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administering/reusing-content/translation/rules# Improved/Expected Behavior: Remove CF jcr:title from being translated by default and give creator of CF Models FULL control over fields to be translated. Actually it makes no sense to translate the jcr:title of a CF as it makes more sense to keep this in one language (English) for common readability in AEM UI. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
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 directly change the search form. Improved/Expected Behavior: Requested Enhancement:1. Make the Group Predicate Available in the AEM UI Users can add filters within group predicates Administrators can specify the title of the group predicate in the UI. The search form editor interface allows admins to specify whether the group predicate is initially open or closed for users. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Walmart US Marketing Screenshot (if applicable): Code package (if applicable):
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 listener to update the memory value of the access token will solve this problem and mail forms will continue to work without any downtime and need of manual interaction Similar approach should be implemented to other services that have the same issue Environment Details (AEM version/service pack, any other specifics if applicable): AEM as as Cloud Service, support ticket with RCA of the problem https://experienceleague.adobe.com/home?support-tab=my-cases&case-id=E-001916327&org-id=22DA472D57D07A817F000101%40AdobeOrg#support Customer-name/Organization name: BBraun Medical Screenshot (if applicable): Code package (if applicable):
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):
Request for Feature Enhancement (RFE) Summary: Automation mechanism within Developer Console or Adobe I/O Runtime Action to automatically renew the technical account certificate (Case E-001849802) Use-case: We are using the service credentials JSON to get bearer token from IMS and then send payload over to AEM Author. The key concern is how to maintain this as the certificate expires after 1 year. Currently, we see the manual provision of generating a new certificate and then manually updating the runtime action with the service credentials. This approach is rather manual and crude. We would appreciate a solution that could automate this. Current/Experienced Behavior: As of now, Adobe does not provide an automated mechanism within the Developer Console or Adobe I/O runtime to automatically renew the technical account’s certificate. This means that certificate rotation must be triggered manually via the Adobe Developer Console. Improved/Expected Behavior: The certificate rotation can be automated to alleviate the load for manual setup of technical account certificates post their expiry. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Customer-name/Organization name: EPAM Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Introduce a configuration (e.g., max.children.per.folder) that defines the maximum number of child nodes (assets or subfolders) allowed within a given folder. Use-case: AEM currently allows more than 1,000 assets (child nodes) to exist within a single folder. However, it’s well known that exceeding this threshold leads to significant performance degradation. To help our administrators effectively monitor and control within our environment, we request the addition of functionality that provides both preventive and diagnostic controls related to folder child limits. This request covers two main objectives: 1) Prevent Adding Assets Beyond a Configurable Folder Child Limit 2) Expose a Method to Identify Overpopulated Folders Current/Experienced Behavior: None Improved/Expected Behavior: Requested Enhancements1. Prevent Adding Assets Beyond a Configurable Folder Child Limit Introduce a configuration (e.g., max.children.per.folder) that defines the maximum number of child nodes (assets or subfolders) allowed within a given folder. Enforce this limit across all methods of asset ingestion or modification, including: Author UI uploads (single and bulk) Programmatic or API-based imports (e.g., via custom integrations) Workflow-driven imports Package or Content Transfer installations When the limit is reached, block additional assets from being created under that folder and return a clear, user-friendly error message (e.g., “Folder has reached its maximum capacity of 1000 assets. Please create or use a subfolder.”). 2. Expose a Method to Identify Overpopulated Folders Provide a reporting mechanism or API endpoint that identifies folders exceeding the configured child limit. This could be implemented in one or more of the following ways: A built-in report under Tools → Assets → Reports An accessible QueryBuilder or GraphQL endpoint for integration with monitoring tools The output should include: Folder path Number of children Configured limit (for context) Optional recommendation for remediation (e.g., “Consider splitting into subfolders”) RationaleManaging folder size manually is error-prone and often discovered only after performance issues surface. Providing built-in enforcement and visibility would: Prevent system degradation before it occurs. Reduce administrative overhead of custom scripting or monitoring. Improve user experience by giving immediate feedback and guidance. Encourage scalable and maintainable DAM structures across all AEM environments. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Walmart US Marketing Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add back the search field to the cq/gui/components/authoring/dialog/fileupload component Use-case: Back in AEM 6.5 the fileupload had a search field that made it easier to pick assets in core components such as Image v3 or Page v3. Now it's not supported and the "fix" is to use other components that lack the comprehensive UI of fileupload Current/Experienced Behavior: When you click on Pick you don't get a search field, it just says "Select Path" and you have to manually go to the image's path (which is troublesome in folders with over 100 files) Improved/Expected Behavior: Instead of the header that says "Select Path" add the search like in the pathfield Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service. Customer-name/Organization name: Teladoc Health Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add a confirmation pop-up asking “Are you sure you want to stop the execution of the pipeline?” when deploying through Cloud Manager. Use-case: When deploying a pipeline through Adobe Cloud Manager, users can accidentally click the “Stop Execution” button instead of “Resume” during the deployment process. If this happens, the pipeline stops immediately without any confirmation, forcing the user to restart the deployment from the beginning.Although the package is reused and some steps can be skipped, this still causes unnecessary delays and confusion, especially in production environments. Adding a confirmation pop-up (e.g., “Are you sure you want to stop the execution of the pipeline?”) would prevent accidental interruptions and help ensure smoother, safer deployments. Current/Experienced Behavior: Currently, when a pipeline is running in Adobe Cloud Manager, the “Stop Execution” button can be clicked at any time during the deployment process.Once it’s clicked — even by mistake — the pipeline stops immediately without any confirmation or warning message. As a result, users must restart the entire process, even if the interruption was accidental. Although Cloud Manager reuses the same package, some steps still need to be repeated, which causes unnecessary delays and additional manual work. Improved/Expected Behavior: When a user clicks the “Stop Execution” button during a pipeline deployment in Adobe Cloud Manager, a confirmation pop-up should appear asking for verification before the process is stopped. The pop-up could display a simple message such as: “Are you sure you want to stop the execution of the pipeline?” Only if the user confirms the action (for example, by clicking “Yes” or “Confirm”) should the deployment be terminated.If the user clicks “Cancel”, the pipeline should continue running without interruption. This improvement would prevent accidental clicks from stopping active deployments and help ensure a smoother and safer release process, especially in production environments. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Cloud Manager – Production and Staging pipelines Example shown from Production deployment pipeline Current version and service pack are aligned with AEM Cloud Service latest release (SP23) Customer-name/Organization name: MITECO Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Combined asset upload and meta data import with spreadsheet (e.g. csv) in one step. Use-case: Mass uploading assets will be faster and easier when meta data can be added in one step. Current/Experienced Behavior: To mass upload assets and apply meta data, you need to upload the assets first, then click "Create" again to add meta data with the help of a spradsheet. Improved/Expected Behavior: Combined mass upload dialog where you can upload the meta data spreadsheet AND the files in one step, e.g. drag/drop the meta data spreadsheet, then the files. When the assets are in the asset bank, all meta data is already there, no additional steps needed. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets Customer-name/Organization name: HBK Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In AEM Cloud UE, I want to update language copies or create structure. I want to be able to select particular languages without having to check all 33 languages first and then uncheck the ones that are not needed so that I can work efficiently and without wasting time. Use-case: Select a page, go to the left Current/Experienced Behavior: The language copy update dialogue only shows after selecting all 33 languages at once. If I want to work with (a) particular language(s) only, I need to uncheck all languages that are not needed. Improved/Expected Behavior: After the language copy rail opened, I want to be able to check the language layer I want to update immediately, without having the need to select all 33 languages first and THEN select my language Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud, Universal Editor, EDS Customer-name/Organization name: SAP SE Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: I'd like the possibility to add default environment variables for cloud manager pipelines. Those variables would available and up to date on any new pipeline execution.We would still be able to override those variables at pipeline level. Use-case: I'd like to setup default version of NODE for FE pipelines as well as some tokens for private npm registry. Current/Experienced Behavior: Env variables needs to be set for each FE pipelines. When a secret token expires, every pipelines need to be updated. Improved/Expected Behavior: Set some variables at program level, that are automatically assigned during pipeline build phase. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Danone Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: AEM Guides Content Authors face the issue of not able to use UI in Author to insert the new Attribute Value, instead they have to go to source view to add it. However, to make it come in Author view, the only option Authors find is to add in Folder Profiles, Conditional Attribute which seems difficult for Authors to understand and follow, Is there a way Authors can create new Value as they do in Source in Author view itself. Currently how it is handled:https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/user-guide/map-management-publishing/output-gen/conditional-content/generate-output-conditional-attribute-profilinghttps://experienceleague.adobe.com/en/docs/experience-manager-guides-learn/videos/advanced-user-guide/folder-profiles#edit-conditional-attributes-in-the-global-profile Use-case: AEM Guides Content Authors face the issue of not able to use UI in Author to insert the new Attribute Value, instead they have to go to source view to add it. However, to make it come in Author view, the only option Authors find is to add in Folder Profiles, Conditional Attribute which seems difficult for Authors to understand and follow, Is there a way Authors can create new Value as they do in Source in Author view itself. Currently how it is handled:https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/user-guide/map-management-publishing/output-gen/conditional-content/generate-output-conditional-attribute-profilinghttps://experienceleague.adobe.com/en/docs/experience-manager-guides-learn/videos/advanced-user-guide/folder-profiles#edit-conditional-attributes-in-the-global-profile Current/Experienced Behavior: Authors have to learn to add values in folder profiles Improved/Expected Behavior: Values saved OOTB on first type and suggests for future without adding in Folder profile conditional profiling Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2025.10.23122.20251023T134343Z-251000 AEM Guides 2025.10.0.278 Customer-name/Organization name: Sub-Zero and Wolf Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Option to edit the comment of a particular version of the Page in AEM as Cloud Service in AEM SITES. Use-case: When trying to add comment for each version of a page, if done mistakenly, there is no option to update the comment OOTB. Current/Experienced Behavior: When trying to add comment for each version of a page, if done mistakenly, there is no option to update the comment OOTB. Improved/Expected Behavior: Provide an option to update the comment OOTB. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2025.10.23122.20251023T134343Z-251000 AEM Guides 2025.10.0.278 Customer-name/Organization name: Sub-Zero and Wolf Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When using private GitHub repo for our AEM code on Cloud Manager it always triggers FS code quality pipeline, even if the repo is actually meant for FE pipeline. Use-case: Use private github repo in cloud manager for FE pipeline. Current/Experienced Behavior: For each pull request, a full stack code quality pipeline is created automatically. Improved/Expected Behavior: Add the possibility to disable that check when not relevant, in that case for FE only projects. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Danone Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Asset Selector Microfrontend - Rule-based hiding of Assets Use-case: AEM is used to manage and host the website. Assets are delivered from Publish.A 3rd party, external, customer-facing application uses AEM as delivery system for their assets. The according backoffice application uses the MFE to select assets. Users of the 3rd party application must not see or select assets that are in a certain state (e.g. have not been published or approved or are expired or ...). Otherwise the app would store references that have not been approved (in this case "published") and cannot be served from Publish.IMPORTANT NOTE:"Hiding assets" is not the same as filtering for assets (which can be configured): "Filtering" always triggers a search, i.e. it would display all assets of the current and _all subfolders_. Also, this is a user action. "Hiding" in turn would a) not be a user action, but configured by the administrators. And b) would be applied automatically when users browse through the folder structure (I believe a majority still uses folders and browsers over search/metadata). This hiding of course also needs to be applied to the results when a user does an explicit search. Current/Experienced Behavior: All assets are displayed - regardless of their state Improved/Expected Behavior: Administrators can define a set of rules that prevent certain assets to be displayed. ORThe MFE calls a callback on each asset tile / row it wants to render and a customizer can provide code to return a value to enable/disable/hide the asset's tile. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Asset Selector Microfrontend MFE: Make Status field Configurable to display publication status Use-case: The Status indicator on the MFE seems to have been designed for an Assets-only installation, and with the new Asset view in mind, only. On Enterprise installations, i.e. where one has an Author and a Publish system, tasks and the approval status are rarely used. Instead user would "publish" an asset, which implicitly means "approved" (otherwise why would you publish).Use Case: AEM is used to manage and host the website. Assets are delivered from Publish.,A 3rd party, external, customer-facing application uses AEM as delivery system for their assets. The according backoffice application uses the MFE to select assets. This application needs to know which assets have been published. Otherwise it would store path references that have not been approved (in this case "published") and cannot be resolved on Published. Current/Experienced Behavior: The field dam:status is rendered hard-coded in the MFE. Improved/Expected Behavior: Make the status field in the MFE configurable, so that the provider of the MFE can choose what to display here. In the described use case, show the publication status (not the approval status). Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest as of Nov. 2. 2025 Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The "Assign to" selection dropdown menu within the AEM Guides review process does not filter results when a user's name is typed into the field. This requires users to manually scroll through the entire list to find and select a name.This issue significantly hinders workflow efficiency, especially in projects with a large number of registered users, making the process time-consuming and prone to selection errors.Steps to ReproduceNavigate to the AEM Guides interface and select content for review.Initiate a review process (Menu -> "Create Review Task").Click on the "Assign to" dropdown field.Begin typing the name of a known user into the field.Feature Request:Implement a type-ahead search or filter functionality for the user selection dropdown menu to allow for quick and efficient searching. Use-case: Ease of functionality Current/Experienced Behavior: Typing into the field has no effect on the list. The full, unfiltered list of users remains visible, forcing the user to manually scroll to locate the correct person. Improved/Expected Behavior: As characters are typed into the field, the dropdown list should dynamically filter in real-time to display only the users and groups whose names match the entered text. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 Customer-name/Organization name: Red Hat Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Currently when reprocessing assets, a popup displays and informs the users that they will be notified when their async job finishes. However, no notification is sent. Use-case: Content authors should be notified of successful job completions, especially if they are told they will receive a notification. Current/Experienced Behavior: Popup says a notification will be sent when the async job completes. No notification is sent. Improved/Expected Behavior: Popup says a notification will be send when the async job completes. Notification is sent. Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Netjets Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In CloudManager label menu item "View current execution" when the execution is running Use-case: Current/Experienced Behavior: In CloudManager when the execution is running, the label in menu item says "View last execution" - this is semantically wrong/confusing. Improved/Expected Behavior: Current/Experienced Behavior: In CloudManager when the execution is running, the label in menu item says "View current execution" Environment Details (AEM version/service pack, any other specifics if applicable): latest Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: CloudManager: Status: Failed Use-case: Current/Experienced Behavior: In CloudManage, when the last pipeline execution failed, the status is "Running". Improved/Expected Behavior: In CloudManager in the dashboard and on the Pipeline view, show Status: Failed when the last execution failed (as do other CICD systems) Environment Details (AEM version/service pack, any other specifics if applicable): any Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: Migrate Content Hub configurations like Search Filters and Asset Metadata details across environments Use-case: Setting up of Content hub across program Current/Experienced Behavior: Need to configure all the settings including setting up of several custom search filters and asset metadata mappings manually across all environments. Improved/Expected Behavior: Need a self service way to import and export configurations for each environment or a mechanism to migrate the configurations from one environment to the other. Environment Details (AEM version/service pack, any other specifics if applicable): 2025.10.22943.20251009T135918Z Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
