Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: - AEM EDS Integration (cross-walk) for Adobe Target is currently very limited. - Clients heavily use the long existing feature, to upload experience fragments, created in AEM to the Adobe Target server for personalization usage. - This is currently a broken workflow in EDS cross-walk, as one can not create Experience Fragments from EDS Blocks - That's why - on behalf of our client DVAG - we request to have the possibility, to create Experience Fragments from EDS Blocks in the Universal Editor in order to export and update those to and on the Adobe Target Server in order to run A/B Tests and personalized Experiences in Adobe Target with provided Experience Fragments Use-case: 1. Editor creates Experience Fragment from EDS Block in Universal Editor (see provided draft image) 2. Editor creates variants of this Experience Fragment (existing feature for classic AEM Components) 3. User uploads the Variations to Adobe Target Server (

Request for Feature Enhancement (RFE) Summary:   Use-case:   Current/Experienced Behavior: As the number of created collections continues to grow, we’re observing some usability and maintenance challenges. Please refer to the attached recording for reference.   Key Issues: Difficulty for users to find or filter relevant collections Increasing need for better maintenance and hygiene of collections in AEM Assets Improved/Expected Behavior: Filter Option: Public vs. Private Collections Allow users to filter collections by:      Public (shared)      Private (created by the user) This would simplify navigation and reduce clutter in the list view.   Expiration Date for Collections Enable users to set an expiration date when creating a collection. After expiry, the collection could either:      Be automatically deleted, or      Moved to an Archived state for review befo

Request for Feature Enhancement (RFE) Summary: Feature Idea:Adobe Content Copy Tool (CCT) Enhancements - Enhance the Adobe Content Copy Tool (CCT) to improve performance, usability, and flexibility for handling large content sets, environment constraints, and exclusion rules. Use-case: Syncing a large amount of content between different cloud environments Current/Experienced Behavior: The CCT is not practical for back-staging large content sets; it takes an excessively long time and often does not finish when handling large amounts of content. Content cannot be copied from lower environments to higher environments. The tool cannot be used if another pipeline is currently running in the same environment. No support for wildcard-based exclusion or inclusion patterns in content sets (e.g., excluding all subdirectories under a given path using regex or wildcards). Building packages in crx/packmgr works but has a timeout of 10 minutes which makes it hard to split content up in smal

Request for Feature Enhancement (RFE) Summary: Give the editor who creates a translation project the option to switch easily with one click to the project which has been created. Use-case: As an editor I wanted to have a efficient way of working once I want to sent my page out for translation. I create the page in the source language and with only some clicks without leaving the Sites console I want to start the translation job. Current/Experienced Behavior: If I am in the editing mode of my source page I can not start a translation job (btw. Lionbridge connector offers that option in the page menu), so I have to switch to the Sites Admin. Here I create the translation project via the left rail but after creating, system just says "Project created". I have to switch to Projects, look for the project created and start the translation. This is not a fluent way of working and not efficient!I have attached a screen recording to make it clearer. Improved/Expected Behavior: To impro

Request for Feature Enhancement (RFE) Summary: Functionality improvement to allow users to define the tag order for CF Use-case: The order in which tags are displayed is very important because it is a selling point of the product. Currently, they are displayed in the order specified, but in the new CF editor, they are displayed in ascending order of tag name. Please improve the function so that users can define the display order of tags themselves, because it has a large impact on business. Current/Experienced Behavior: The old editor displays tags in the order you specify, but the new editor displays them in ascending order by tag name. Improved/Expected Behavior: The tag order specified by the user is maintained even in the new editor. Environment Details (AEM version/service pack, any other specifics if applicable): AEM aa CS 2025.03 Customer-name/Organization name: TOPCON POSITIONING ASIA CO LTD Screenshot (if applicable):   Code package (if applicable): &nbsp

Request for Feature Enhancement (RFE) Summary: Link Reference Update inside experience fragment when creating a live copy or rollout an experience fragment Use-case: When we rollout or create a site/live copy of a page the link reference gets updated from language master/language to respective country/language inside components with in that page. But in experience fragment this feature is missing Current/Experienced Behavior: Link Reference does not get update inside experience fragment when creating a live copy or rollout an experience fragment Improved/Expected Behavior: Link Reference Update inside experience fragment when creating a live copy or rollout an experience fragment 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: There should be a UI accessible to authors that will allow them to manage dictionaries Use-case: Translation management Current/Experienced Behavior: The current UI is not accessible to authors (and probably not available in Cloud) which means, updating this will require authors to be dependent on admins or developers to make changes https://<hostname>:<port-number>/libs/cq/i18n/translator.html Improved/Expected Behavior: A UI within the Authoring console is available AEnvironment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Proquire Screenshot (if applicable): N/A Code package (if applicable): N/A

Request for Feature Enhancement (RFE) Summary: suggest a product enhancement folder download size limit to 10GB Use-case: the maximum size for folder downloads set to 10 GB. Any downloads exceeding this limit would prompt a message instructing users to contact their assigned Asset Manager. Current/Experienced Behavior: issue with downloading large directories from a cloud service. When clients try to download project folders exceeding a certain size (e.g., 10GB), the process fails despite the feature being available. Improved/Expected Behavior: maximum size for folder downloads set to 10 GB. Any downloads exceeding this limit would prompt a message instructing users to contact their assigned Asset Manager. 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: 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