Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Show version for out of the box Workflow "manage publications" Use-case: When using the AEMaaCS Workflow "manage publications", there currently is no version published in the timeline. It is also not possible to add a custom parameter "enableVersion=true", as this is an out of the box Workflow, which is not editable. Versioning is needed to keep track of the published content and do proper version control. This is problematic when there is a need to revert to an older version, as it is not possible to access the new versions through the timeline. Also it is inconsistent with Page editor and Quick publish versioning who do show up in the timeline. Current/Experienced Behavior: No version is shown in the timeline for content published via the out of the box Workflow "manage publications" Improved/Expected Behavior: Add a version to show up in the timeline for content published via the of the box Workflow "manage publications"

Request for Feature Enhancement (RFE) Summary: Content fragments created using custom CFM show size as 0B Use-case: Authors create CFs and they see the size of the CF is 0B as opposed to having some numeric value since the CF is not empty Current/Experienced Behavior: Create a Content fragment model in Tools->Assets->Content Fragment Models. Go to Navigation->Assets, click create, select content fragment from the drop-down. Select the content fragment model you created. Enter data into CF and click save. Change the view in Assets folder to List view, the size column for this content fragment shows 0B. When you create a content fragment which uses an OOB AEM CFM, the size is calculated correctly Improved/Expected Behavior: The size of the content fragment refering any CFM (custom or OOB) should show the actual size. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21.0 Customer-name/Organization name: Fidelity Investme

Request for Feature Enhancement (RFE) Summary: Currently, Smart Tagging in AEM leverages AI to generate metadata for assets automatically. While this increases efficiency, it can lead to irrelevant or inconsistent tagging. Introducing an allow-list would complement the existing block-tags functionality, providing both restrictive (block) and permissive (allow) controls over tag generation.The ask is the Implementation of an Allow-List Functionality for AEM Smart Tagging based on a Dictionary/JSON File. This feature will ensure that only business-relevant tags, as defined by the organization, are applied to assets, enhancing tagging accuracy and consistency. Use-case: Organizations require precise control over the metadata applied to their digital assets to maintain brand integrity, regulatory compliance, and content relevance. For example, a fashion brand may only want tags related to specific product lines, materials, or styles. An allow-list would enable them to define a set o

Request for Feature Enhancement (RFE) Summary: We have a requirement, where the authors want by default the folder structure in an alphabetical order while the user is performing any operations such as the "move" operation on files or folders. The current display is not helpful to them to find locations. They also want to default their different views to list in alphabetical order as an option. Use-case: 1. As an author, I want to have the option to view my files and folders in alphabetical order by default, so that I can easily locate areas and not have to change the display to alphabetical each time. 2. As an author, I want to have the option to view my files and folders in alphabetical order by default when performing any operations such as move for example, so that I can easily locate areas. Current/Experienced Behavior: 1. The first time you load the sites or assets experience; you must change to list view and then sort on the column you desire to view in alphabetical or

Request for Feature Enhancement (RFE) Summary: Automate TLS certificate renewal Use-case: Imagine you have 20+ different websites running on your AEMaaCS instance, each one with its own domain name, and therefore its associated TLS certificates. Further imagine that there are dev, staging and prod environments, both for preview and publish. Finally, the certificates may not be wildcard certs (*.example.org) but specific subdomain (preview.example.org, preview-st.example.org, ...).   So you have easily 50+ certificates to renew, and they will not renew at the same time, but across the whole year. Having to manually renew each certificate is error-prone and time-consuming. Also, in order to do this job, the person needs to have elevated administrative rights, but the job itself does not have a lot of added value.   It would therefore be appreciable to automate the renewal of the TLS certificates. In a different environment in the past I was using the certbot tool integrat

Request for Feature Enhancement (RFE) Summary: We should have an improved way of authentication and  authorization of GraphQL endpoint.In the current design, even unauthenticated or improperly authenticated requests are allowed to hit the endpoint with 200 response code. Instead we should have 401 or 403 response code with proper messages. Use-case: If we are doing any implementation on basis of response code the current implementation will not work as it will always giving 200 as response code. Current/Experienced Behavior: In the current design, even unauthenticated or improperly authenticated requests are allowed to hit the endpoint with 200 response code.  Improved/Expected Behavior: If access token is not correct or request is unauthenticated then we should have 401 or 403 response code with proper error messages. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as SaaS Customer-name/Organization name:   Screensho

Request for Feature Enhancement (RFE) Summary: I want to be able to migrate content created in each AEM environment (dev, stg, prd) to another environment on the console without going through the package manager. Specifically, I would like to be able to migrate by environment on the content fragment screen. Use-case: Example: It will be possible to migrate a content fragment created in the dev environment to the stg environment on the console. (In this case, the status of the public information will not be carried over.) Current/Experienced Behavior:Content fragments cannot be migrated to a different environment on the console Content fragments cannot be migrated to a different environment on the console Improved/Expected Behavior: Content fragments can be migrated to a different environment on the console Environment Details (AEM version/service pack, any other specifics if applicable): AEM version：2025.1.19352.20250131T194709Z Customer-name/Organization name: Yuki Mama /

Request for Feature Enhancement (RFE) Summary: Better way to create custom AEM components Use-case: One needs to build from scratch a new AEM component Current/Experienced Behavior: In the current AEM world, there are way too often the situations when developers end up building new AEM components (and not use the core components).   The experience of building a new component is not very pleasant, prone to human mistakes due to the heavy ponderous coding. Working manually with the XML to define the dialogs makes the developer very often lose focus on the big picture and easy get lost into details about not forgetting to add the well-known <items> element, or to keep track of tabs, or to properly arrange dialog fields, or to make the dropdowns work (specially when we have multiple dependent ones) and so on. All becomes even more complicated when he needs to (also manually) add extra clientlibs having to careful when writing it and not add a typo. On top of this, h

Request for Feature Enhancement (RFE) Summary: Making timelines more resilient to heavy workflow activities.  Currently timelines timeout because the number of nodes that it has to transvers is over the threshold.  We had to purge and reduce our timelines from 30 days to 5 days in order for us to see the timeline results. Use-case: We heavy workflows that causes the timelines to transverse over 30,000 and fail to return results. Current/Experienced Behavior: We expect the OOTB functionality of timelines should work as expected. Which out create custom indexes Improved/Expected Behavior: OOTB indexes should be able used to ensure timeline return in a timely fashion and not timeout. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP19 Customer-name/Organization name: Toyota Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: New content fragment editor console doesn't show the "Source Edit" option despite being enabled and visible. It appears correctly on the old/classic console Use-case: Our Content Fragment Model has a multi-line text field configured with default type as "rich text".Under path -  /apps/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.jsWe can find source edit under "uiSettings" as seen below -  The source edit option appears on the old/classic console -    But is missing on the new console -  Current/Experienced Behavior: Source Edit option is missing on the new console for editing CF Improved/Expected Behavior: Source Edit option should be displayed on the new console for editing CF Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release - 2025.3.19823.20250304T101418Z Customer-name/Organization name: EPAM Screenshot (if appl

Request for Feature Enhancement (RFE) Summary: Ability to use "granite:class" and "granite:data" in the new CF editor Use-case: We developed a show/hide fields plugin for the new CF editor based on a type selection made in a select field. For this purpose we used the example provivided in the docs: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/data/#setting-styles-to-the-field api.setStyles(fieldName, {"display": "none"}); However, this is not an optimal solution, as we need to hide each field per name instead of creating a generic plugin that could be reused on any content fragment. If we had an option to retrieve the value of a custom data attribute, then our plugin could be reusable. Current/Experienced Behavior: The "granite:class" and "granite:data" set in the CF model is not present in the HTML, and custom data attributes cannot be retrieved by custom plugins. Improved/Expected Behavior: The "granite:class" and "granite:data" set in the CF model is p

Request for Feature Enhancement (RFE) Summary: Add an API/extension point that would allow developers to change the rootPath for the Asset/CF/Content picker via a JS plugin: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/ Use-case: Our AEMaaCS project hosts more than 100 websites, each site has its own dedicated root folders for sites and assets (including subfolders for specific content fragment types). We had a custom, JS-based solution in the old CF editor to change the root paths of the CF/Content picker so that when an author opens the picker, it takes him to the correct location by default. This greatly improves the editorial experience of our 700+ authors that work on multiple sites. Current/Experienced Behavior: Asset/CF/Content picker always opens the root folder and editors need to navigate manually to their site and the correct folder. Improved/Expected Behavior: Customization can be enabled to programmatically set the correct root folder via JS, as

Request for Feature Enhancement (RFE) Summary: The current API and the example shared in the docs to toggle (show/hide) fields in the new CF editor does not work as expected and contains multiple issues. Docs: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/data/#setting-styles-to-the-field Use-case: We have a few CF models where fields are shown or hidden depending on the type selection an editor makes. After creating a new CF, the editor first needs to select a provider, and then different fields show depending on the selection. Current/Experienced Behavior: While developing a small plugin for the new CF editor to show/hide fields based on a selection according to the documentation provided [1]. Concretely, we are relying on the api.setStyles , but we noticed two bugs:1) This approach works fine for standard input fields, but not for select boxes/enumeration fields, they remain visible even after we try to hide them with CSS display:none2) The standard i

Request for Feature Enhancement (RFE) Summary: New permission to remove the replace button on assets. Use-case: We have a lot of squad working in AEMAACS and for some areas we need to have more granularity on the permission, for example some areas can't publish, others can't upload assets and some areas can't replace the assets, so we need to have this permissions on the access control. Current/Experienced Behavior: We don't have this granularity to change this access level. Improved/Expected Behavior: The expectation is to have an access profile created with the “Replace” option profile disabled, in order to eliminate the risk of accidentally replacing the campaign image. We are currently exposed to this risk at all times. Environment Details (AEM version/service pack, any other specifics if applicable):   2025.3.19823.20250304T101418Z Customer-name/Organization name: Santander S.A Screenshot (if applicable):   Code package (if applicable): &

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): When a component is moved from a container to another container in a livecopy the component appears again after sync. There should be a ghost component to prevent this. Anwendungsfall: If you move a component from one container to another in a livecopy, the component appears again in the original container after syncing with the blueprint.Steps to reproduce:- Create a new page with the template Content Page and open it- Add a Layout Container to the page- Add a component to the layout container (for instance a Text Component) and fill in some text.- Create a LiveCopy of the above page with Standard Rollout Config and open the LiveCopy- Add a second Layout Container to the LiveCopy- Drag (move) the component in the first container to the second- In the page settings synchronize with the blueprint- The component appears again in the first container There should be a ghost component in the first container when the component

Request for Feature Enhancement (RFE) Summary: For in the loop page template, when user insert any link and provide specific dita file path and click on check icon of link option, its not routing to the provided dita folder.Steps to reproduce:Go to AEM sites https://auth-viewpoint-qa.pwc.com/sites.html/contentAuthor In The Loop Page Template.Add text component and add link by clicking on link option.Select a dita file manually.After selecting click on the tick icon on link option.Check that its not routing to provided dita path.Team, please look into this issue and help us at the earliest to resolve this issueAdobe support ticket : E-001529292 Use-case:   Current/Experienced Behavior: link is not routing to provided dita path. Improved/Expected Behavior: its should rout to provided dita path. The cloud version routs to the path properly. We need this facility in non cloud version too Environment Details (AEM version/service pack, any other specifics if applicable):

Request for Feature Enhancement (RFE) Summary: The proposed feature aims to enable businesses to generate customizable, template-based reports by leveraging metadata criteria for assets stored in Adobe Experience Manager (AEM). These reports can be scheduled for automated generation and distributed to various platforms or teams. Use-case: Businesses often need reports filtered based on specific metadata values (e.g., region, asset type, product category). These reports are essential for: Supporting marketing campaigns by identifying suitable content. Generating insights for compliance or governance reviews. However, manually filtering and compiling this data is time-intensive and prone to errors. Automating this process would save time and improve data accuracy. Current/Experienced Behavior: We need to manually filter the content after generating reports for all assets. Improved/Expected Behavior: Report Templates: Admins can create and save report templates with predefi

  Request for Feature Enhancement (RFE) Summary: I would like to be able to dehibernate my sandbox environments in a script using the Cloudmanger API (and CLI plugin). Use-case: My sandbox environments go down into hibernation daily, and once I get to development, I need to start the first, eating away 10 minutes every day.I would like to send the de-hibernation signals once i open my laptop in the morning - through a script using the Cloudmanager API or the aio cloudmanager plugin. I have tried to use the Call using from the CM-UI, but I did not get a positive response: Request URL: https://dev-console-ns-team-aem-cm-prd-n108153.ethos14-prod-deu6.dev.adobeaemcloud.com/api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Path: /api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Current/Experienced Behavior: Sanboxes are all hybernated, I have to spin them all up one-by-one manually. (this is very time-consuming ...

Request for Feature Enhancement (RFE) Summary: Option to easily replicate content on the Prod author and publisher to Stage or Dev Use-case: We want Stage or Dev environment to be in sync with Prod content, to be in more or less same state. Current/Experienced Behavior: At the moment we can use copy content sets, but that is only possible to author instance, and when we copy content set, copied pages or assets dont have the publications status. Improved/Expected Behavior: Copy content sets on author and publish instance, and assets and pages to have the same data from Prod to other stages Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: CSS KRANKEN-VERSICHERUNG AG Screenshot (if applicable):   Code package (if applicable):  

Can you believe both AEM Sites or AEM Assets do not have Trashcan feature where you can easily undelete/restore deleted files?As a robust product like AEM, this is absolutely inexcusable to not have such feature built in.. Even Wordpress has "Trash" feature..Please, I beg you, product team, consider adding this feature.Philip

Request for Feature Enhancement (RFE) Summary: AEM as Cloud service CDN (BYOCDN) logs should also include X-Forwarded-Host header value.  Use-case: AEM as Cloud service CDN (BYOCDN) logs should also include X-Forwarded-Host header value. This header is crucial in determining the request host in a multi-tenant environment. Current/Experienced Behavior: AEM as Cloud service CDN (BYOCDN) logs do not include X-Forwarded-Host header value. Improved/Expected Behavior: AEM as Cloud service CDN (BYOCDN) logs should include X-Forwarded-Host header value. Environment Details (AEM version/service pack, any other specifics if applicable): Sample logs (Current):  {"timestamp":"<timestamp>","ttfb":85,"cli_ip":"<cli_ip>","cli_country":"<cli_country>","rid":"<rid>","req_ua":"<req_ua>","aem_program_id":"<programID>","aem_env_id":"<environmentID>","aem_tier":"<aem_tier>","aem_env_type":"<aem_env_type>","hos

Request for Feature Enhancement (RFE) Summary: Enterprise level applications with the option to be able to upload binaries require anti-malware protection. Also, most enterprise policies require "Anti-malware" to be implemented to be compliant. AEM does not provide any means of Anti-Virus OOTB, but there are solutions which can be used in "on-premise" and AMS (managed Service) scenarios.However, in AEMaaCS (Cloud Service) there is no option, and no way to create a "customization" to be able to implement anti-virus/malware-protection.   In the AdaptTo()-2020 several ways to implement "Anti-Malware in AEM" were proposed [0][2].   The solution by Oliver Lietz (Sling Contributor) has the charm, that the malware scanning would be implemented on SLING level using SlingJobs (which would work across the Author Cluster in AEMaaCS), with a "CloudService" which is used to scan the binaries outside of the AEM instances - which seems to be compatible with AEMaaCS and it's Cloud-Servic

Request for Feature Enhancement (RFE) Summary: Enhance aem-upload library to accept sourceUrls instead of current local filePath and blob only. Use-case: After Adobe deprecated the legacy Asset Upload APIs the alternate solution suggested was Open-sourced upload library aem-upload. Unfortunately alternate solution is NOT fully ready. The library allows only local filePath and blob to be uploaded. Does allow external sourceUrls. This was possible with previous AssetManager API which is now deprecated.    Current/Experienced Behavior: aem-upload does not allow sourceUrl as input Improved/Expected Behavior: aem-upload must allow external https sourceUrl as input and must automatically download and upload into AEM. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Since the Dispatcher doesn't support ETags it creates unnecessary traffic between the Dispatcher and the CDN by sending unchanged content. Use-case: The page is cached on both CDN and Dispatcher. CDN sends a request to the Dispatcher with the f-None-Match header. The Dispatcher responds with HTTP 200 and the content in the body, even though the content hasn't changed and the CDN already has the latest version. Current/Experienced Behavior: The Dispatcher is always returning HTTP 200 code when delivering cached content. Even when the cache ETag header value matches the value of the If-None-Match header in the request. Improved/Expected Behavior: The expected behavior would be for the Dispatcher to return HTTP 304 code with no body when ETag matches the value of the If-None-Match header. Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEMaaCS - 2024.10.18311.20241017T104455Z Custom

Request for Feature Enhancement (RFE) Summary: This feature will enable organizations to define metadata validation rules based on compliance or guideline requirements and extract detailed reports for discrepancies. This will facilitate better data governance and streamlined updates to metadata across the organization. Use-case: Organizations often face challenges ensuring metadata adheres to evolving compliance regulations or organizational guidelines. Manual validation processes are time-intensive and error-prone, leading to non-compliance risks and inconsistencies in metadata quality. This feature addresses the need for automated validation and actionable reporting. Current/Experienced Behavior: Metadata validation is performed manually or using scripts, leading to inefficiencies. There is no unified interface or reporting mechanism to validate metadata against dynamically defined compliance rules. Discrepancies or outdated metadata are identified late, causing delays in re