Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: The AEM Authoring interface doesn't work with the debugClientLibs query param so debugging client libraries is not possible anymore. Use-case: There is a documented parameter debugClientLibs that produces client libraries output in the debug mode, without combining and minifying the JS and CSS files. It was very useful in the early versions of AEM but stopped working some time ago, either due to new out-of-the-box client libraries or because of those libraries' modifications, or because of the evolution of modern web browsers. It would be good to have it back. Current/Experienced Behavior: The authoring interface doesn't work correctly when there is documented debugClientLibs=true parameter present in the query. Improved/Expected Behavior: The authoring interface should work when the debugClientLibs=true parameter is set in the query Environment Details (AEM version/service pack, any other specifics if applicable): Stopped wor

Using AEM along with Translation project to send pages/assets for translation, We can configure Translation rules to exclude/Include paths with /content/dam/ path allowed. Ex:- My DAM structure is "/content/dam/XYZ/global", "/content/dam/XYZ/us", "/content/dam/XYZ/uk" "/content/dam/XYZ/de" etc.. I have image component which will be used by authors in different sections of the page and browse images from the above paths. Here I want to exclude images from "/content/dam/XYZ/global" but take images from other locales for translation while they submit pages for translation. I have posted similar question earlier to questions section and was asked to submit the "support ticket", hope this is the right place to submit this. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/skip-assets-from-asset-translation-job/qaq-p/377318  

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): The expired assets predicate in the search filter currently only has one feature. Asset is already expired.Yet there are much more interesting things related to the expiry, that could be shown.Here are some examples for more interesting search filter regarding the expiry: Expired: The asset itself is expired(Ignore Dependencies) Has expired dependencies: The asset contains expired assets (Don't show expired assets, but instead those assets that contain an expired asset) Will expire: The asset will expire till (dateselect)+ usefull quickoptions: within the next 1 week, 1 month, 1year etc.)Be careful using those on sites / print projects that will be used for a longer period of time, since the printed media can't be "unpublished" but have to be destroyed, removed etc.) Will not expire: Show only assets that are free of an expiry restrictionI call it the "care free" option. Assetts can be used without having any f

Request for Feature Enhancement (RFE) Summary: Support for multiple SMTP configurations Use-case: Many client work in multi-tenant set-up. Very often they need different SMTP configurations to send emails. Current/Experienced Behavior: Only one SMTP server can be configured by Day CQ mail service Improved/Expected Behavior: A factory configuration is available for SMTP configs. One can pick one dynamically and send emails Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Brillio Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Use-case: Developers needs the replication behavior similar to that of a server for validating caching use cases. Current/Experienced Behavior: An (enabled) Dispatcher flush agent is not trigger on receive events. Thus, .stat files are not touched and the caching behavior cannot be mimicked for entire flow Improved/Expected Behavior: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Environment Details (AEM version/service pack, any other specifics if applicable): AaaCS local SDK Customer-name/Organization name: Brillio Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Extend Core components to display content from a linked CF Use-case: Many clients want to reuse content across multiple channels. Often recommendation is to use content fragments for authoring. However, being form-based, it cannot readily be used on a website. It would be good if we could extend core components such that they can display content from a linked CF Current/Experienced Behavior: CF being form-based cannot readily be used on web-pages  Improved/Expected Behavior: Components should be able to pull content from a linked CF to display Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.x & AaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Rollback feature for Production Deployment Use-case: Feature request for Cloud manager, where a process in place where we click on one button and confirm to roll back the code which was deployed to production. Current/Experienced Behavior: No efficient process to rollback in AEM production environment  Improved/Expected Behavior: Functionality that allows AEM users to roll back to a previous version in production environments 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: Providing advance notifications and implementing a code validation pipeline for upcoming CM rule updates would be highly beneficial, as it can help mitigate unexpected pipeline failures, such as the one mentioned in the provided link. Use-case: Failed pipelines due to sudden CM rule updates Current/Experienced Behavior: Pipelines suddenly start failing if they don't comply to CM rules Improved/Expected Behavior: A prior notification and separate pipeline to validate code against upcoming updates Environment Details (AEM version/service pack, any other specifics if applicable): AEM instances using Cloud manager Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Should have leverage to provide required permissions like (Read, Modify and Delete) from touch UI for Experience fragments folder. Use-case:   Current/Experienced Behavior: In order to get inherit Edit permission Adode team has suggest to provide jcr:all permissions for the Experience fragment folder. Improved/Expected Behavior: We need to leverage in such a way that we can provide required permissions like (Read, Modify and Delete) from touch UI.   Environment Details (AEM version/service pack, any other specifics if applicable): Version : Adobe Experience Manager (6.5.14.0) Customer-name/Organization name: American Express.  Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Extend Adobe Sensei capabilities in AEM Sites to extend capabilties of content creation and smart tagging Use-case: 1. Auto/smart tag webpages 2. Add description/title (for SEO) 3. Content curation Current/Experienced Behavior: Currently only content summary for CF using Sensei is supported Improved/Expected Behavior:   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: Enable bulk tagging of pages that are Live Copies Use-case: The client is using MSM to keep thousands of pages in sync with Blueprints. The client wishes to group some Live Copies in Group A and some Live Copies in group B, the obvious grouping method is tagging. However, bulk tagging pages is not possible if the pages are Live Copies. Current/Experienced Behavior: Bulk tagging does not work on Live Copies Improved/Expected Behavior: Bulk tagging works on Live Copies Environment Details (AEM version/service pack, any other specifics if applicable): AEM AMS 6.5.16 Customer-name/Organization name: Toyota Motor Europe Screenshot (if applicable): / Code package (if applicable): /

Request for Feature Enhancement (RFE) Summary: This is a request to have a scroll bar added to the bottom of the AEM Guides editor repository. Use-case: Some of our DITA assets have long titles that go beyond the maximum width of the repository. When there are multiple search results with such long titles, an author would have to hover over each one until the needed asset is found (imagine having to go thru hundreds of assets!). Current/Experienced Behavior: Some of our DITA assets have long titles that go beyond the maximum width of the repository. When there are multiple search results with such long titles, an author would have to hover over each one until the needed asset is found Improved/Expected Behavior: With a horizontal scroll bar, the author will only need to scroll left or right to be able to see the search result titles in full. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.12.  AEM Guide 4.1 Customer-name/Orga

Demande de résumé des améliorations des fonctionnalités (RFE) : There was a functionality on AEM 6.3 that allowed users to copy an asset or a page, then refresh the page (go to another folder by modifying the URL on the browser) and then paste the asset or page to the destination folder. This functionality has been removed on AEM 6.4 to avoid a copy/paste from a module to another one (Assets to Sites for example). But it should still be available when you stay on the same module : copy/paste an asset in the module Assets. Cas d’utilisation : Users used this functionality on 6.3 to avoid going through the whole folder hierarchy when they already know the destination path. It's time saving. Comportement actuel/expérimenté : Select an asset or a page Click on “Copy” In the same window, manually modify the browser URL to go to another folder to paste it Example : From : https://{localhost}/assets.html/content/dam/fr/2022/products/hr To : https://{localhost}/asset

Request for Feature Enhancement (RFE) Summary: Strong and Em tags in multiline text in Content Fragments Use-case: editing multiline text in RTE components while meeting requirements for WCAG 2.0 Current/Experienced Behavior: b/i/u buttons create <b>,<i>,<u> tags which have no semantic meaning Improved/Expected Behavior: in order to convey meaning to users using assistive technology, we should be able to add <strong> and <em> instead of <b> and <i>. <u> on the other hand has little semantic value and will likely confuse users who will think it is a link. it should probably be removed or replaced with something with similar semantic meaning like  the <mark> element Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.4-6.5 Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Would like the following feature - Enable Priority Queue configuration in SCD agents for AEMaaCS. Use-case: We want to implement a priority queue for one of our tenant in a multi-tenant architecture for sites in AEMaaCS. While other sites may have multiple pages that are getting activated, one site needs to avoid delay in replication. Current/Experienced Behavior: No option to configure a priority queue in AEMaaCS. Improved/Expected Behavior: Option to configure a priority queue in AEMaaCS should be available. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS - Version - 2023.1 Customer-name/Organization name: TA Digital Screenshot (if applicable): N.A Code package (if applicable): N.A   @kautuk_sahni 

Request for Feature Enhancement (RFE) Summary: The time is not displayed in the date (for example, PUBLISHD) of each node displayed on the Sites management screen. Therefore, the user cannot confirm when it was published. There is a way to customize the overlay, but I would like it to display the time as standard. Use-case: When creating a site, check when the node was published. The time is displayed on the Assets management screen, but it is not displayed on the Sites management screen. Current/Experienced Behavior: The format is "date". Improved/Expected Behavior: The format is "datetime". Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2023.4.12142.20230526T152858Z Customer-name/Organization name: SCSK Corp. Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: I propose adobe to include an option to expand the entire parent node along with its child nodes with a single click. Because, sometimes it feels annoying to click "+" on each node to see the final child node(leaf node) if it has a multiple child nodes.   Although the idea sounds simple, but it would be useful sometimes when people in a hurry to check something.   Use-case:   Current/Experienced Behavior: For example - cq: dialog, we have to expand it node by node until we reach the child node. Improved/Expected Behavior: My idea - When I right click on a node - a new option called "Expand Entire Node" should be implemented such that once I click on it, it would show/expand it till the last child node. Environment Details (AEM version/service pack, any other specifics if applicable): I think this feature is not present in any version of AEM it seems. Customer-name/Organization name: Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Dashboard to display total number of pages , Assets , users , users group , tags and ability to export the data in CSV format for individual AEM instance. Use-case: As a AEM admin i want to know how many assets , pages etc available in each AEM instance ( dev , qa , stage , prod) provisioned in my cloud environment and will be able to extract the data in csv format . Current/Experienced Behavior: No dashboard exist , need to run report or custom queries to get the data  Improved/Expected Behavior: Real time dashboard can help AEM admin to get this holistic view in one screen  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service  Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Brand Portal users to be able to update metadata property of uploaded assets in contribution folder Use-case: If user on  brand portal doesn't have access to AEM assets, he is not able to update the assets metadata for the assets that has been uploaded on Brand Portal Contribution folder and its not necessary that metadata should always be embedded and in some scenario there might be some purchased assets from other vendor and updating their metadata values on assets itself is not possible Current/Experienced Behavior: users on brand portal can't edit the metadata value as its read only Improved/Expected Behavior: Looking for improved feature to enable the edit of metadata only for New folder inside contribution folder on AEM brand Portal so that whenever user on brand portal upload the assets they can also modify/update the metadata value for the assets that they uploaded. Environment Details (AEM version/service pack, any

Request for Feature Enhancement (RFE) Summary: "Most Recent Run Date"  and "Most Recent Run Status" columns on the Adobe Cloud Manager Content Set screen. Use-case: As the customers, we create a lot of content copy sets inside the Content Sets screen of Adobe CM. As the list of content sets increases and used over time, it is not easy to track what is the most recent date a given content set was run and it's status unless we go into "Copy Content Activity" screen.  Current/Experienced Behavior: No way to check when was a given content set ran and it's status unless it is checked in the "Copy Content Activity" screen. Improved/Expected Behavior: Adobe CM Content Copy screens users will be able to easily get the information on when a given content set was last ran and it's status during the most recent run. It would be even helpful, if these columns can be sorted ASC/DESC. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Cloud

It would be helpful to provide a way to configure the build profile to choose while configuring the CI/CD pipeline through cloud manager instance.  

Request for Feature Enhancement (RFE) Summary: A tool that allows automation of creating tags and tagging pages and publishing those tags and pages by a CSV file and will generate a report of bulk tagging with some important information like page_path, tag_path, tag_name, status (success/error), etc. Use-case: The use case for your AEM tool is to automate the creation of tags, tagging pages, and publishing these tags and pages in Adobe Experience Manager (AEM) using a CSV file. By leveraging this tool, you can save time and effort for content editors while ensuring consistent tagging and publishing across multiple pages. Additionally, the tool generates a comprehensive report that provides insights into the status of each page, allowing you to track progress, identify errors, and ensure accurate tagging and publishing processes. This automation and reporting functionality enhances productivity and efficiency, making it particularly beneficial for organizations with large content r

Request for Feature Enhancement (RFE) Summary: If you have a lot of target data, you will run into problems during launch and promotion. Please improve the function. Use-case: launch, promotion Current/Experienced Behavior: 1. Issues when creating launchesAn error message is displayed even though the process has completed normally.Error message: Form could not be submitted 2. Problems with promotionThe following message is displayed and the process remains in progress.Message: Promoting launch Improved/Expected Behavior: 1. Improvements when creating launches　Improved so that users are not confused.・Prevent false error messages from being displayedIf the cause is a timeout, extend the timeout time (example: 1 minute → 5 minutes)・Change the message to match the actual situation. 2. Improvements when promotedImprove so that the process ends normally・If the cause is a timeout, extend the timeout time (example: 1 minute → 5 minutes)・Change the message to match the actual situat

Request for Feature Enhancement (RFE) Summary: Would like to change the displayed error code when a user with non-admin rights (system or product admin) tries to setup the technical account. Use-case: I am trying to generate access token using Developer Console. I have the support admin access but not the system admin access which is required to setup the technical account and generate clientID, clientSecret, privateKey, publicKey along with other parameters.  Current/Experienced Behavior: Currently getting the error - Gateway Timeout (HTTP 504) An error occurred attempting to load the provided log. Please check the URL and ensure it is reachable. Improved/Expected Behavior: Since the user is not authorized to generate Access Tokens the 504 Error should be changed. (401 deals with lack of validated authentication credentials for the requested resource)The HTTP Code 504 is associated with Gateway Timeout thereby implying that the server, while acting as a gateway or pro

Request for Feature Enhancement (RFE) Summary: Ability to Save a Content Fragment with a Nested Composite Multifield Use-case: 1. Add a nested composite multifield to a content fragment model. 2 . Add content to the fragment then try to save. Current/Experienced Behavior: Cannot save the content fragment with the nested composite multifield. Improved/Expected Behavior: Ability to save the content fragment with the nested composite multifield. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 6.5.15.0 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):