Build better products with our product team
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):
Request for Feature Enhancement (RFE) Summary: Improve multilingual content management in AEM by enabling a single content fragment to support multiple languages/locales through a tabbed or variant-based interface. Use-case: Our content authors manage over 500,000 content fragments across 12 languages. Currently, each language requires a separate content fragment, resulting in significant manual effort and complexity when performing routine tasks such as updates, moves, deletions, and publishing. Current/Experienced Behavior: AEM requires a separate content fragment for each language or locale. Authors must manually replicate actions (e.g., move, update, unpublish, delete) across all language versions. Shared fields must be updated individually in each of the 12 language-specific fragments. This leads to a high risk of inconsistency, increased maintenance overhead, and a time-consuming authoring experience. Improved/Expected Behavior: Enable a single content fragment to support multiple languages/locales using a tabbed or variant-based structure. Allow shared fields to be updated once and reflected across all language variants. Provide built-in tools or automation to manage language-specific content more efficiently (e.g., bulk move, update, unpublish, delete). Reduce manual effort and improve consistency across multilingual content. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Version: 6.5 Service Pack: 6.5.22 Deployment:On-premise Content Volume: Over 1 million content fragments across 20 languages Customer-name/Organization name: Hyatt Hotels Corporation Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The Preview environment should be in Sync with the Publisher, to be able to preview the changes and see only the needed modifications. At the moment, AEMaaCS relies on the publishers to replicate the changes to both environments (Preview and Publish) this could lead into errors, leaving the Preview environment out of sync and breaking the purpose of it. The request is to have a service running that triggers replication to the Preview environment as soon as one page gets published. Use-case: Improve usability of Preview instance since the publishers will see only the content modified Current/Experienced Behavior: The Preview and Publish instances relies on manual user input to be in sync (publish twice) Improved/Expected Behavior: Preview and Publish should be updated at the same time during replication Environment Details (AEM version/service pack, any other specifics if applicable): AEM SDK 2025.10.22943.20251009T135918Z Customer-name/Organization name: UBS Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Currently, Cloud Manager and Splunk dashboards do not provide visibility into leader pod restarts in AEM as a Cloud Service environments. Identifying when and why a leader pod restarts is essential for understanding system stability and troubleshooting potential performance or replication issues. Having this visibility directly in Cloud Manager (or accessible via Splunk logs) would help operations and development teams proactively monitor environment health, correlate incidents, and improve root-cause analysis without needing Adobe support intervention. Use-case: Leader pod restarts can affect replication, workflows, or cache invalidation, but currently there is no easy way for customers to detect or audit these events. Providing this visibility would reduce investigation time during incidents, enhance transparency, and empower teams to maintain stable AEM Cloud environments. Current/Experienced Behavior: There is no visibility or alert mechanism in Cloud Manager or Splunk for leader pod restarts. Customers must rely on Adobe Support to confirm such events. Improved/Expected Behavior: Display leader pod restart events in Cloud Manager’s monitoring section, with timestamps and pod names. Alternatively, include this information in the Splunk logs or provide an API endpoint to query pod restart history.Optional alerting mechanism (email or webhook) when leader pods restart unexpectedly. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service – SDK version 2025.9.22758 (build: 20250928T092442Z) Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Added configurability for retaining applied filters when a user navigates away from a page where there are filters applied. Use-case: Improved user experience, greater levels of control/customisation over our environment. Current/Experienced Behavior: As a user on Asset UI/AEMaaCS/AEM Assets, when I apply filters for a search and navigate away from the page with filters applied and return to the search, the filters are cleared. This means that I have to reapply the filters to return the same search. Improved/Expected Behavior: I want the filters to remain applied so that I do not have to add the filters again. Environment Details (AEM version/service pack, any other specifics if applicable): Asset UI/AEMaaCS/AEM Assets Customer-name/Organization name: NatWest Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Cloud Manager: Move Pipeline Configuration from "Source" to "Configuration" tab. Use-case: Configuring Pipelines Current/Experienced Behavior: Configurations are distributed randomly in unrelated tabs, Improved/Expected Behavior: The Pipeline Configuration is not related to the source code repository. Thus it is more intuitive to place it under the "Configuration" tab rather then "Source". Even better would be to divide the tabs as - General - Behavior - Source - Test and Experience Audit Environment Details (AEM version/service pack, any other specifics if applicable): CloudManager / all Customer-name/Organization name: all Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: Offer an option to disable the new Assets UI Use-case: Our users work in AEM and are used utilize the AEM UI also to upload assets to AEM Assets Console. The new Assets UI should not be used as as e.g. important custom validation of file names or folders that we have implement as customizations are not effective. Current/Experienced Behavior: As new Assets UI is completely decoupled from AEM UI for Assets console, custom validations on file and folder names are not effective. Therefore unwanted file names and folder patterns are possible to create. Improved/Expected Behavior: We as a customer want to control if and when our users could see/use the new Assets 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: Environment configuration copy between the environments. Example: Stage to Development Use-case: We have two Development environment and on a requirement basis we would like to have the similar configuration between the environments. Current/Experienced Behavior: We cannot copy the configurations between the environments Improved/Expected Behavior: Similar to content copy feature, having this configurations copy will be added benefit Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: McAfee Screenshot (if applicable): Ticket No: E-001871093 Code package (if applicable): Ticket No: E-001871093
Request for Feature Enhancement (RFE) Summary: Enable Rollout of Cq:tags property by default for content update and other relevant MSM configs Use-case: In AEM page properties basic tab, the Tags field is excluded from rollout to Live copies. This is due to an exclusion rule applied in MSM content update Action OSGI config where anything that starts with cq: is excluded from getting rolled out to love copies. while this makes sense for node specific , under the hood properties like cq:lastModified, cq:lastModifiedBy, cq:lastReplicatedBy , unfortunately this also excludes cq:tags property as well. This should be included by default and the current excluded properties regex should be updated to include this property by default for rollout. Current exclusion regex (CQ MSM Content Update Action) - cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|redirectTarget).*) New regex value to include cq:tags - cq:(?!(designPath|template|lastTranslationUpdate|targetEngine|redirectTarget|tags).*) Current/Experienced Behavior: Currently , the cq:tags property is not enabled for rollout by default Improved/Expected Behavior: cq:tags property should be enabled for rollout by default. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: TCS Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enhance the Content Fragment Models (CFM) console to support folder navigation and organization of models within nested folder structures. Use-case: Authors and developers often need to organize multiple Content Fragment Models logically (e.g., by business domain, content type, or project) under nested folders within the configuration structure. Supporting folder navigation in the CFM console would help teams manage large sets of models more efficiently and maintain a cleaner, more intuitive structure aligned with their business taxonomy. Current/Experienced Behavior: Although it is possible to create nested folders for models using CRXDE or the repository directly, the CFM console UI currently displays only the models located within the root configuration folder. Users cannot navigate into subfolders, which results in all models being listed together without hierarchical grouping. Improved/Expected Behavior: The Content Fragment Models console should allow navigation through nested folder structures under the configuration path. This enhancement would let users browse, create, and manage models within organized subfolders, improving model discoverability and aligning with how other AEM consoles (like Assets or Sites) handle hierarchical structures. Environment Details (AEM version/service pack, any other specifics if applicable): Reproducible on AEM 6.5 and AEMasCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Possibility to schedule the production deployment via Cloudmanager for Blue/Green deployment type. Currently, this feature is not available for Blue/Green deployments via Cloudmanager Use-case: The deployments via cloud manager takes too long, and we also don't want to start this in the evening a day before as then it doesn't leave much time for the next day for the new Green instances. Green instances stay active only for 24 hours. With scheduled deployment capability, we will schedule this to run early morning before the working hours start so that we are ready for next steps when the working hours start. Current/Experienced Behavior: This capability is not present Improved/Expected Behavior: Scheduled Cloud manager deployment for Blue/Green deployment Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, Cloudmanager Customer-name/Organization name: Eurowings Screenshot (if applicable): Code package (if applicable):
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
