Product Communities

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 adminis

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

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 u

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

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

  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 visibi

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|targetEngin

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

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

Request for Feature Enhancement (RFE) Summary: Do not open Page Properties in fullscreen  Use-case: Users provide images in the page properties to be used by teasers, og:image, etc.   Current/Experienced Behavior: In AEM page editor, when one opens the page properties, the dialog is opened full-screen. I.e. It covers the Asset selector on the left rail. This means a user cannot use the search, filter and drag&drop capabilities the asset dialog offers. If more than one page is to provided with the same image, a user has to open each page and browse to the asset individually. Improved/Expected Behavior: Keep the left editor rail visible and open the properties dialog in a modal lightbox or only covering the page. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest and AEM 6.5 Customer-name/Organization name: all Screenshot (if applicable): Desired behavior:   Code package (if applicable):  

Resumen de la solicitud de mejora de funciones (RFE): Currently, AEM’s XSSProtection configuration (/libs/cq/xssprotection/config.xml) does not allow several accessibility-related attributes such as aria-label, aria-hidden, role, and tabindex.We propose including these attributes by default in the configuration to improve accessibility support and reduce the need for overlays or custom configurations. Caso de uso: Developers using HTL expressions like: ${property @ context='html'} cannot render accessibility attributes defined in component properties, since they are filtered by the XSSProtection mechanism. This limits the ability to build fully accessible components following WCAG and ARIA standards. Comportamiento actual/experimentado: When rendering properties that contain ARIA or accessibility-related attributes, these attributes are removed by XSSProtection because they are not listed in config.xml. The only current workaround is to overlay /libs/cq/xssprotection/config.xm

Request for Feature Enhancement (RFE) Summary: Wildcard DV certificates and wildcard subdomains Use-case: For DEV and STAGE environments often a common publish domain is being used. As the default Adobe one (https://publish-pxxx-eyyy.adobeaemcloud.com/) does not allow subdomains the individual sites are addressed via subdomains of that common domain to have a similar setup as PROD (1 domain = 1 website). That allows even automatic mapping of content paths to sites without needing setup costs for additional sites. Current/Experienced Behavior: Cloud Manager does neither support wildcard domains in the domain settings (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/custom-domain-names/introduction#usage-notes) nor does it allow wildcard DV Adobe-managed certificates. Therefore each subdomain requires - Configuration via the Domain - Domain verification via additional TXT record - Set up a dedicated DV manager c

Request for Feature Enhancement (RFE) Summary: Ability to search for images in the “Pick Image” window on the image component   As of now, when an author tries to select an image using the “browse for image” option in components or page properties, they need to drill through the entire AEM directory and hunt for the image they want with truncated file names and tiny thumbnails. Could we have the ability to search for an image using file names or descriptions? Use-case: Image Search in “Pick Image” Dialog Currently, when authors select an image in AEM through the “Browse for Image” option (in components or page properties), they must manually navigate through the entire directory structure. This process is inefficient and error-prone, especially when dealing with large repositories, truncated file names, or small thumbnail previews. By adding a search capability within the “Pick Image” dialog, authors could quickly locate assets by file name, description, or metadata. This

Request for Feature Enhancement (RFE) Summary: When using UI Extensibility for the Asset view, when using UI Extensibility on the Asset view, the current options are rather limited and does not allow to cover all cases. Particularly features like "download asset" are basically impossible to override, since the button exists within the toolbar but also outside in the top bar Use-case: Asset View extensibility should provide an extension point for the top bar (the button list in the top right ) .  As an example of things that cannot be done right now is overriding the button for "download asset". It is possible to hide or override the behavior of the download button in browse view (since it appears in the quick actions and action bar), but that button also exists in the top bar in a place where no extension points exists, making overriding all cases impossible Current/Experienced Behavior: There is no possibility to extend or modify the action buttons at the top of the as

Request for Feature Enhancement (RFE) Summary: Add timeout configuration to the pipeline Use-case: Pipelines can take a long time to finish, and the only way to cancel them is to contact Adobe support. While this is perfectly valid in cases when something is not working properly in the pipeline itself, it would be good to have the possibility to cancel pipelines in case there is something wrong with the user code, and there is no need for Adobe intervention. Current/Experienced Behavior: Pipelines can take up to several hours to fail.  Improved/Expected Behavior: The configuration for the pipeline timeout is explicitly defined value in minutes, or as a relative threshold compared to the average calculated time over 90 days (this value is already shown in the pipeline). Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Any Screenshot (if applicable):   Code package (if a