Adobe Experience Manager

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

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: 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: Add Sorting filter in Card View for collections Use-case: Users created multiple collections but navigating into them using the card view, they are not able to easily sort the assets using name, title or other information like already happens for list view. Users require to have sortable functionality in the card view because they should have the possibility to see quickly preview of the asset to select from an ordered list. Same behaviour from list view is expected. Current/Experienced Behavior: Collections are sortable only in the list view. Improved/Expected Behavior: Each collection should be sortable by title, name, date, etc also in the card view. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.10.18175.20241010T124406Z-240900 Customer-name/Organization name: Jet2 Screenshot (if applicable): List view   Card view   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary:   Use-case:   In AEM, a proper preview can be generated, but this functionality is missing in Content Hub.   Current/Experienced Behavior: Many assets are stored in ZIP file formats, but Content Hub currently displays them as blank folders or icons. Improved/Expected Behavior: need for a feature to generate previews for ZIP files automatically to avoid manual effort Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

  Request for Feature Enhancement (RFE) Summary: Provide a way for the "Asset Compute microservice extensibility"/Asset Compute workers to access the default renditions for an Asset so the custom worker can use those as a baseline for further conversions. Either: Pass a default rendition to the worker (instead of, or in addition to, the original). Or: Defer worker invocation until default renditions are generated (opt-in), so the worker can fetch them reliably. Or: Allow non ARM64 containers and installation of custom binaries like imagemagick for the Asset Compute microservice Use-case: We need to generate custom renditions (e.g., square JPEGs with white borders) from assets like .ai (Adobe Illustrator), .psd (Adobe Photoshop), .svg, .eps, etc. These file types are already supported by AEM’s default rendition generation, but not by Asset Compute workers directly (see below for reasons). If workers could use AEM’s default renditions as inputs, they could reliably

Request for Feature Enhancement (RFE) Summary: Custom domain names are supported in Cloud Manager for both publish and preview services for Sites programs. Custom domains for author services are not supported. Use-case: Currently the Author service is accessed via URL in format -https://author-p<Program-ID>-e<Environment-ID>.adobeaemcloud.com Custom domain name for Author should be service should be supported similar to Preview and Publish Services. Current/Experienced Behavior: Only URLs of below format are allowed - https://author-p<Program-ID>-e<Environment-ID>.adobeaemcloud.com  Improved/Expected Behavior: Custom Domain Mapping should allow URLs like https://brandAauthor.brand.com to be mapped to Author service. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2023.4.12142.20230526T152858Z Customer-name/Organization name: TA Digital Screenshot (if applicable):   Code pac

Request for Feature Enhancement (RFE) Summary: Content managers need an ability to "Replace a file" from the asset's properties. We implemented an override for them (pictures attached). In future we'd like to have this feature as Out-of-the-box functionality. Use-case: Content manager creates an asset's language copy, then "Reveal in Asset", then goes to the asset's properties and need to Replace the original file by translated version of file, having stored it on local computer with different name. Current/Experienced Behavior: Content manager can update an asset's file by one of the 2 ways: Create a Version: Open the folder in the DAM. Find his/her asset file. Select it and click on the "+ Create" button, then select "Version" button. Replace an original file OR Create a version:Save a future image with the SAME name as an original asset's file in the DAM. Drag and drop the future image to the DAM. System suggests "Create a version" or "Replace". Improved/Expected Beha

Request for Feature Enhancement (RFE) Summary: Adobe provides monthly twice updates to AEMaaCS Environments. Even better, Adobe introduced Non-Intrusive Updates. But the updates are happening only to Prod and non-prod environments. No ability for RDE to update. Developers have to trash RDE and spin new RDE to receive latest updates.  Use-case: Extend the ability to update AEM servers to RDE environments as well.  Current/Experienced Behavior: RDE Environment cannot be updated to latest AEM version. Needs to be trashed and recreated new. This mandates redeploy to code, configuration, content and is time consuming.  Improved/Expected Behavior: RDE provides Update option similar to Non-prod environments      Environment Details (AEM version/service pack, any other specifics if applicable): RDE on AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable):   Code package (if applicable):