Build better products with our product team
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.xml into /apps, which may cause maintenance issues with future updates. Comportamiento mejorado/esperado: AEM should include the attributes aria-label, aria-hidden, role, and tabindex (and potentially other accessibility-related attributes) in the default XSSProtection configuration, allowing them to be safely rendered through HTL without requiring overlay. Detalles del entorno (versión de AEM, Service Pack y cualquier otra especificación, si corresponde): AEM as a Cloud Service Issue reproducible in both Author and Publish environments. Core Components and custom components affected. Nombre del cliente o de la organización: TELEFONICA ESPANA Captura de pantalla (si corresponde): N/A Paquete de código (si corresponde) Not required – issue reproducible with any component rendering an HTL property with @2941342='html' containing ARIA attributes.
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 certificate Although one could use a custom wildcard certificate right now, that needs to be OV/EV (too expensive for DEV/STAGE purposes) and also the management per subdomain still needs to be done manually. Improved/Expected Behavior: Allow wildcard domains so that the setup is only necessary once, instead of per sub domain. This requires:- Allow configuration of wildcard domains in Domain management - Allow Adobe managed DV certificates for wildcards (supported by Let's Encrypt with every ACMEv2 compatible client) - Adjust UI to allow mapping the wildcard certificates to the wildcard domain Environment Details (AEM version/service pack, any other specifics if applicable): n/a Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
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 enhancement would significantly improve the authoring experience by: Reducing the time spent searching for specific images Streamlining content creation and updates Minimizing manual navigation errors Increasing overall productivity for large-scale content teams Current/Experienced Behavior: When we select/pick an image into the image component, we have to select the aem directory and hunt for the image we want Improved/Expected Behavior: Could we have the ability to search for an image using file names or descriptions and then select the one we want Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
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 asset view (neither on browse or asset view) Improved/Expected Behavior: There should be a way to extend or modify the action buttons at the top of the asset view Environment Details (AEM version/service pack, any other specifics if applicable): N/A Customer-name/Organization name: Banking Screenshot (if applicable): Code package (if applicable):
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 applicable):
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 [ { fieldNameExp: "therapeuticArea" , onchange: (newValue) => { console.log("[Log] Therapeutic Area changed to:", newValue); } }, ]; };this console is not working . im using this in my extensionRegistration
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 applicable):
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 associated CF: A "Publish" button should be available in the "Open in Assets" view. The "Publish" action should apply only to the selected asset and not affect the referencing Content Fragment (CF). The user experience should be streamlined, reducing unnecessary navigation steps. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Accenture, Inc. Screenshot (if applicable): Code package (if applicable):
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 package (if applicable):
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 reference to what is the error. The ActivationReferenceSearchBuilder could point to related content, content fragments, experience fragments, but in this case there is an issue with a linked component policy on the template. Improved/Expected Behavior: At least: an error message in the user-facing quick publish dialog. Currently the behavior is a red Warning icon without any text. Secondary: a more relevant error message: instead of a run-time NPE, a dedicated exception or a warning/debug log would be nice. Environment Details (AEM version/service pack, any other specifics if applicable): AEM6.5.23 Customer-name/Organization name: Nationale Loterij Screenshot (if applicable): Code package (if applicable):
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 Customer-name/Organization name: EY Screenshot (if applicable): Code package (if applicable):
Add a Full‑Screen Toggle for Proof ViewerAdd a button that allows the Proof viewer to be displayed in full‑screen mode. With the new unified experience, both the Adobe and Workfront toolbars occupy space at the top of the screen, reducing the available viewing area. Our editors would find it much easier to review Proofs if they could toggle into a true full‑screen view and see the content at full size without interface distractions.
This feature was recently removed. Now if I happen make a change to my document and require the approver’s decision again, I have to remove them and then re-add them. This will trigger an email to the approver saying “Your approval is no longer required.” followed by “Your approval is required” which is extremely confusing. From a user-experience standpoint, the removal of this option is a step backwards. It was a feature up until a bug was fixed. Why remove a feature?
What we’ve discovered with live chat is that when our BDRs miss a chat, we don’t have any way to engage with them in Marketo. When you build a smart list, you cannot use a filter at all for live chat was missed or anything similar. We have a weird workaround that we’re implementing with a goal right before the chat starts that we’re going to try, but I think this is a fundamental piece especially with the chat to Marketo integration. You can trigger off of goals and all kinds of other items, but there’s no way to trigger or even to provide visibility for chats that were missed.
In autumn 2025 Adobe released the Marketo email collaboration feature that allows a team to collaborate and comment on emails within the platform. https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/email-marketing/email-designer/email-collaborationWhile that is all good, this feature seems well designed for small marketing teams. , Unfortunately its not very useful for centralized MOPs teams where the business stakeholders are not actually Marketo users. Request: A way for Adobe Experience Cloud users without a Marketo license to collaborate/comment on emails (and other Marketo assets).
Hi everyone! Just have another idea I figured I’d throw in here. It would be great if we could enter alt text when uploading an image into Marketo, and have that alt text follow the image around whenever it’s placed into an email. That way we wouldn’t have to re-type it every time we re-use an image. (With the caveat that it would still be great to have the option to overwrite the alt text in the individual emails if needed).
I’m not sure if this is a bug, an oversight, or intentional, but the UI in the new email builder for text styling isn’t the most intuitive. Right now, bolding (italicizing, etc) specific words from this black bar menu works as expected: However, when you bold from the right sidebar, it bolds the entire text block: It would be great if both of these text styling options functioned the same. Thank you! 😊
Hello, at the moment, there is no possibility of adding any type of column descriptions in the reports. A some reports can be quite complex it would be beneficial to have some kind of descriptions of columns, either an information icon or mouse-over text. It would be great if this could be implemented. Best regards,Sara
Description - when marking your own PTO in Workfront, at that point to also offer the opportunity to create an out of office notification if you are tagged, messaged or sent requests etc within Workfront - a notification to send to the originator that you are not available to process their ask or make comments etc.Why is this feature important to you - we encourage all project related comms to be in the relevant projects. If you are not aware of people not being in the office/at work then assumption is that they are there to receive the message.How would you like the feature to work - as an email out of office notification.Current Behaviour - if you have not heard from someone after a while, need to investigate if they are working by checking email out of office notifications.
It would be great if you could see a Thumbnail from a Video once you upload it to Workfront in Documents right Away before you proof. As we usally take a few versions until we start the proof process and we have large lists of files, sometimes even 200 :) Thanks
This is a basic functionality of any tool so I would expect to have Conditional Contents enabled on Subject lines in New Editor as well. Please enable it in the next release otherwise the conditional content is pointless if it is only for the email body. Right now I am using tokens to localize the different language versions in subject lines and sender details but this is not ideal and our local marketers are not comfortable with using tokens yet.
ContextAn enterprise customer implementing Adobe Workfront Planning encountered a platform‑imposed limit of 20 calculated fields per record type while trying to add a few additional calculated fields to support new teams. They asked whether this restriction could be overridden.Steps takenSupport investigated and confirmed that Workfront Planning currently enforces a hard limit of 20 calculated fields per record type. This limit is part of the product’s performance guardrails and cannot be changed or increased within an individual customer environment.Business impactThe customer is using a single, centrally governed workspace to maintain consistent intake, taxonomy, and reporting across multiple lines of business. Calculated fields are a core component of their sizing, normalization, and reporting logic. The 20‑field cap forces them to:Remove or consolidate existing calculations Introduce manual workarounds Fragment their data model across multiple record types or workspacesThis undermines their goal of using Planning as a centralized, enterprise‑grade planning system, slows down their rollout, and risks reduced data quality, higher operational overhead, and limited scalability as more teams onboard.The askWhy does the 20‑field limit on calculated fields exist in Workfront Planning? Is there any plan or timeline to increase or remove this cap? Given that this limitation has surfaced for multiple organizations, what is the recommended enterprise design pattern or workaround when the need clearly exceeds 20 calculated fields per record type?
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.
