Adobe Experience Manager Sites

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

Request for Feature Enhancement (RFE) Summary: When any value in the therapeutic area is changed then i want to open the warning popup Use-case: If the user changes the value of TA in the ISI field then pop-up appears for "Changing the TA will move the CF to the directory of the newly selected TA" Current/Experienced Behavior: Only changed value is getting saved Improved/Expected Behavior: If the user changes the value of TA in the ISI field then pop-up appears for "Changing the TA will move the CF to the directory of the newly selected TA" Environment Details (AEM version/service pack, any other specifics if applicable): New rte , open any content fragment in the new rte Customer-name/Organization name: J&J Screenshot (if applicable):   Code package (if applicable):     const getProperties = async () => {         await new Promise((resolve) => setTimeout(resolve, 100));       }     return [

Request for Feature Enhancement (RFE) Summary: Content Hub Display  Use-case:   Current/Experienced Behavior: Content Hub Display Labels on Filters Improved/Expected Behavior: The filter list in Content Hub currently shows technical values instead of display labels. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The AI-powered reverse image search in AEM Assets can find identical or similar images not by comparing meta data, but by analyzing the content of the image itself. Sample images can be uploaded via a button/form to trigger similarity search/reverse image search with an external asset. Use-case: When searching for a certain image or similar images in the asset bank, AI will help turn up the best matches regardless of meta data. I can easily upload any image to search for similar or identical images in the asset bank. Current/Experienced Behavior: Similarity search relies on meta data to find similar images Improved/Expected Behavior: similarity search/reverse image search uses AI to find duplicates and similar images regardless of meta data Environment Details (AEM version/service pack, any other specifics if applicable): ARM Assets Customer-name/Organization name: HBK Screenshot (if applicable):   Code package (if ap

Request for Feature Enhancement (RFE) Summary: Allow editors and viewers to share their collections with other users of Brand Portal (not share link) Use-case: Brand Portal users uses Brand Portal and Assets to self-service with assets and sharing collection would support ideation, team collaboration and system adoption. It would create addition value and likeable feature support system engagement. Current/Experienced Behavior: Non-adm users can create collections or smart collections but they cannot share with other Brand Portal and Assets users. Improved/Expected Behavior: Non-admin users can share the collections and smart collections they create. Environment Details (AEM version/service pack, any other specifics if applicable): Service Manager 6.5 Customer-name/Organization name: Fabiana Barticioti / British Airways Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Publish Button in "Open in Assets" view in new CF Editor Use-case: To enhance user convenience, "Publish Button" should be available once the user click "Open in Assets" view. Current/Experienced Behavior: There's no publish button option for the user after clicking "Open in Assets". User needs to manually navigate under full Assets UI. User should still have an option to publish the asset without publishing the CF which the asset is reference to. Improved/Expected Behavior: When the user clicks "Open in Assets," the system should provide an option to publish the asset directly within the "Open in Assets" view. This eliminates the need for the user to manually navigate to the full Assets UI. Additionally, the system should ensure that the user can publish the asset independently without publishing the Content Fragment (CF) that references the asset. This allows for greater flexibility and avoids unintended changes to the assoc

Request for Feature Enhancement (RFE) Summary: Export / Import Metadata Use-case: Contributors need to export assets metadata which are on the jcr:content node like onTime or offTime, then modify these values and update them massively in the dam Current/Experienced Behavior: Contributors cannot select offTime or onTime property on the export metadata interface /mnt/overlay/dam/gui/content/metadataexport.html?payload=/content/dam/nicephore/animations/nouvel_an_lunaire&_charset_=utf8 On the import interface /mnt/overlay/dam/gui/content/metadataimport.html the columns offTime{{Date}} and onTime{{Date}} are ignored Improved/Expected Behavior: All metadata can be exported and imported, no matter if they are on the /jcr:content or /jcr:content/metadata node Environment Details (AEM version/service pack, any other specifics if applicable):  2025.8.22171.20250828T220440Z Customer-name/Organization name: Valtech Screenshot (if applicable):   Code p

Request for Feature Enhancement (RFE) Summary: When doing a quick publish in AEM 6.5.21 of a page that refers to a template that contains policies for components, the publish action fails (without any error message) when there is an issue when the cq:lastReplicated property is missing on a policy, and the cq:lastReplicationAction is set to Activate.Upon inspection of the logs, it seems like there is a NPE in the ActivationReferenceSearchBuilder.When manually replicating the default policy, the issue resolves and the replication works, as the reference search no longer errors with a NPE. I would expect either an error message, replication to skip the reference, or some more Null safety checks in the reference search service. Use-case: Users cannot Quick Publish content that has issues with related content missing cq:lastReplicated property.  Current/Experienced Behavior: It's very difficult for developers to debug this as we only have an internal NPE without any re

Request for Feature Enhancement (RFE) Summary: I want to be able to get suggestions while adding hyperlinks So that I can have the ability to choose the path much faster  These suggestions should be provided as root paths in the code.  Use-case: Authoring Internal pages content path in RTE - hyperlink fields  Current/Experienced Behavior: When we have to hyper link a page or content fragment , then while entering any text we do not get any suggestions and have to manually type full path or use path browser. It would be great if the path field can give suggestions of page paths as typing.  Improved/Expected Behavior: If we have to author hyperlink path manually and enter text like /content it provides suggestions for available nodes so users can select it and get the URL authored quickly.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a sites - Cloud - 2025.8.21994.20250818T175115Z Custo

Request for Feature Enhancement (RFE) Summary: Enable log collection from Adobe Experience Manager (AEM) in Dynatrace as part of the monitoring integration Use-case: We have successfully integrated Dynatrace with Adobe Experience Manager (AEM) for performance and application monitoring. However, the current integration does not support log collection from AEM servers. Having the ability to collect and analyze logs directly within Dynatrace would significantly enhance our monitoring and troubleshooting capabilities. Current/Experienced Behavior: Dynatrace is integrated with AEM for monitoring, but logs from AEM servers are not being collected, as this feature is not supported. We previously created a support ticket about this, and we were advised that currently, there is no solution for log collection through Dynatrace in AEM Improved/Expected Behavior: We expect Dynatrace to support log collection from AEM servers, in addition to the existing monitoring features. This would al