Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Have a direct link to the specific topic submitted for review from within the email notification that's sent to the reviewer. Use-case: We ask PMs to review topics, and have received feedback that the current process is confusing for them as they need to navigate within AEM to find the relevant topic to review. Current/Experienced Behavior: The email takes the reviewer to the review inbox Improved/Expected Behavior: Take reviewer directly to the topic that the email was about Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Improve UX by adding contextual help/tooltips/instructional help within AEM. Use-case: Technical writers currently find it difficult to know the purpose of many icons, buttons, and menu items when navigating the AEM UI as they don't have any/sufficient tooltips or instructional help. Current/Experienced Behavior:   Improved/Expected Behavior: Clarity regarding the purpose and meaning of:   Menu items. The distinction between "Experience Fragments", "Assets", and "Content Fragments". Global vs iLX Profile.  It would be helpful to have an easily accessible link to Adobe's documentation within AEM. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Move the Inbox icon on top Use-case: On AEM as a Cloud the notification icon(on Navigation bar) opens the popover, where the inbox is at the bottom and kind of hides it from Business users. Why not move it on the same level as Request, Notifications & Announcements or provide an option to configure this. Current/Experienced Behavior: Inbox button at the bottom which moves the focus away for business users Improved/Expected Behavior: Moving the inbox to the top improves the focal point 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: When you're updating a review task in Guides, the Assign To prompt on the Task tab should show the names of viewers who are assigned to the task.  Use-case: When writers see the Assign To prompt is blank, they think they have to add reviewers again, but that's not true. Current/Experienced Behavior: Currently the reviewer names can be seen at the bottom of the Task tab where you're not expecting them and on the Reviewers tab. Improved/Expected Behavior: Show the names of assigned reviewers in the Assign To prompt on the Task tab or move the Assigned list from the bottom of the page to directly after this prompt. Environment Details (AEM version/service pack, any other specifics if applicable): https://author-p108955-e1062829.adobeaemcloud.com/ Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM References Manager Use-case: Track references and control changes Current/Experienced Behavior: It is very common situation when for example an AEM component definition gets changed and the changes immediately need to be reflected on the content. For example a new field is added and it needs to set a default value on the component instance. When the component is newly dragged on the page, this new field is stored in JCR. But then when the component already exists on the page, the new field does not get reflected in the JCR. When content is too large, and contains dozens or hundreds of pages that have this component, if becomes very hard or even impossible for the authors to manually make a false edit of the component and do a dummy save just to have the new property in JCR. Usually either developers end up writing specific on-time-use code helpers to updated entire content in subject, or solution codebase is updated to handle n

Request for Feature Enhancement (RFE) Summary: Replicate ACLs as a contributor Use-case: A contributor need to add or revoke access for some users groups on folders on both author and publish Current/Experienced Behavior: As a contributor or even an administrator, i go to a folder properties, set some rights thanks to the tab "permissions" and save. If i replicate the folder with the "manage publication" feature, my rights are not replicated to the publishers. Improved/Expected Behavior: As a contributor or even an administrator, i go to a folder properties, set some rights thanks to the tab "permissions" and save. If i replicate the folder with the "manage publication" feature, my rights are correctly replicated to the publishers. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service - Assets 2024.11.18598.20241113T125352Z Customer-name/Organization name: Valtech Screenshot (if applicable): Code package (if a

Request for Feature Enhancement (RFE) Summary: Provide a notification functionality for translation projects which informs a defined group of the translation project about the completion of a translation, listing all pages that have been translated so that you just need to click on the link to open the pages, review and publish them. Use-case: As an editor which has started a translation job, I want to be informed once the translation is back in AEM in order to check and publish the page. Current/Experienced Behavior: There is no functionality inside the Translation Project, you have do a customization by yourself. Improved/Expected Behavior: As the information about completed translation jobs is essential and no editor wants to check frequently the status of the translations projects, especially when there are hundreds running, I would expect that there is an ootb functionality for that. In the project you already have the chance to add member - here you could simply define

Request for Feature Enhancement (RFE) Summary: Email notification recipients struggle to see clickable links in email notifications for Content Fragment updates.  Use-case: When a user is tagged in the comments for a CF, an email is sent to the tagged user's inbox, which contains a link to the CF where the comment is posted. The notification does not appear visually to look like a clickable link.  Current/Experienced Behavior: Cannot discern notifications for comments contain a clickable link to the CF.  Improved/Expected Behavior: Users should easily see the email notification contains a clickable link to the CF.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 18493 Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable): n/a

Request for Feature Enhancement (RFE) Summary: Enhance the AEM Assets Search to support partial and full-text search functionality for metadata properties containing special characters, such as dot (.) and hyphen (-), as part of their values. Use-case: The customer has integrated a custom property (jcr:content/metadata/dc:suffix) into the filter search form and enabled partial search for this property. This property stores metadata values, such as product SKUs, which frequently include dots (.) and hyphens (-) as part of their structure (e.g., OLED48B46LA.AEUQLHX or OLED48B46-LA-AEUQLHX). However, the current search functionality treats these special characters as delimiters, breaking the search query into tokens and failing to retrieve relevant assets. For example, search for OLED48B46-LA.AEU* is not working where property value is OLED48B46-LA.AEUQLHX. This issue significantly impacts the customer’s ability to locate assets efficiently, disrupting workflows that depend on

Request for Feature Enhancement (RFE) Summary: If you add a page for a translation job which has not been modified since last translation, the editor should get a hint why it is not added! Use-case: As an editor I create a new translation job and add a page. The system recognizes that the page is existing in the target language and therefore gives you the option to "Update language copy". Current/Experienced Behavior: The select page does not appear in the list. There is no hint in the UI showing the reason. Also, there is no hint in the error log. The reason is that it is not added if source page has not been modified since last translation. BUT how should you as an editor working in a team with a lot of pages know that? Why does an enterprise system just don't show a message why the page is not added? It's that basic! Improved/Expected Behavior: System should show an appropriate hint in the UI telling the editor why his selected page has not been added. Something like "Th

Request for Feature Enhancement (RFE) Summary: Please improve the way how a creator of an translation project can add users to the project. Currently only an administrator can do that which is NOT feasible at all under real live scenarios. There this option is currently totally USELESS! The creator should be able to add users and there roles by himself. Use-case: As an editor which has the task to create translation projects, I need to be able to add other users to the translation project so that they can see and maintain it WITHOUT the help of an administrator. Current/Experienced Behavior: As a member of the 'project-administrators' can only add myself and the anonymous user to the project. I got the confirmation from Adobe Support that this by design and only members of the administrators group can see all users in the dropdown. With this the option to add users to the project with different rules is USELESS under normal circumstances! Normal users can not turn to administrat

Request for Feature Enhancement (RFE) Summary: On multifield component dialog: add sufficient space between the validation alert and the up/down arrows so each can be individually selected. This is a bug fix.  Use-case: When a user makes an error in the list component, eg by not filling a mandatory field, they cannot view the validation message that would tell them what to fix, because when they click it, they click into the field to drag items up and down. It is impossible to select the validation alert.  Current/Experienced Behavior: As above - user cannot select or read validation alert to know what to fix.  Improved/Expected Behavior: Sufficient space between the validation alert and the up/down errors so their selection field does not overlap. Then a user can click and read the validation message and / or click and move items up and down.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5  Customer-n

Request for Feature Enhancement (RFE) Summary: Chance to select which kind of assets(original or renditions or both) to download from shared assets. Use-case: AEM as Cloud Service: when I share multiple assets with a user through the Share functionality, the receiver can't choose if they want to download only the original assets or the renditions, it automatically downloads whatever was set up by the person initiating the share. Current/Experienced Behavior: When I share multiple assets with a user through the Share functionality, the receiver must download whatever was set up by the sender, not for folders or collections. Improved/Expected Behavior: The requirement is for the person receiving the assets to be able to specify what they want to download, similar to the functionality present when you just use the DAM as a normal user,  both for folders and collections. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.11.18598.2024111

Request for Feature Enhancement (RFE) Summary: Add Sorting Filter in Card View for various asset display variations Use-case: Use and enable Sort By filter in card view. Open AEM Asset Search and sort in card view. Current/Experienced Behavior: Sorting for Asset Search etc. is only available in List View, which only displays very small thumbnails. Card View Sort Filter function is currently only available at Assets>Files. Improved/Expected Behavior: Card View Sort Filter is available in AEM Search etc. like it is in its functionality DAM where you can sort the assets in the folders. We would like to use this existing function in Asset Search and Collection Detailview. Environment Details (AEM version/service pack, any other specifics if applicable): v6.5 AEM Assets Customer-name/Organization name: AIDA Cruises Screenshot (if applicable): possible use Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Optimize the synchronization process to minimize latency, ensuring that user data is available across all pods immediately upon creation. This will enhance user experience by providing real-time data access. Use-case:   Current/Experienced Behavior: it takes 200 to 500 ms in synching user across pods in cloud service Improved/Expected Behavior: it should be almost instant or with in few milliseconds Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Munich Re Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Develop functionality to execute user-related code within a single pod, preventing cross-pod requests for user data until it is fully synchronized. This will reduce errors and improve system reliability during user login. Use-case: When user get created on one pod and code check on another pod it results on authentications issues in applications Current/Experienced Behavior: should be able to guide code restrict code to run in same pod for whole flow. Improved/Expected Behavior: Same pod should be getting used for one set of request flow. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Customer-name/Organization name: Munich Re Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: To have the ability to undo the move or deleted assets/pages  Use-case: Sometimes we want to revert the bulk moved or deleted assets or pages, but we don't have any recycle bin or undo changes option Current/Experienced Behavior: No option to get back the deleted or undo the moved assets or pages Improved/Expected Behavior: We should have undo option in the action bar just like paste so that we can get back the unintentional action results 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: Ability to re-baseline RDE environment after reset / Backfill code image from Prod to other environments Use-case: After a production release we backfill our environments. This is done by executing pipelines for the various Dev environments however this could be different to whats deployed to production depending on when the master branch was deployed.For our RDE environments however, this is manual and when we have multiple RDE's for our developers its a time consuming task to reset each environment. It would be great if we could simply select an image that has previously been deployed to an environment such as Production and be able to deploy that to any dev/rde environment without having to run a build pipeline.This would minimise effort from executing multiple pipelines and manual effort and would also minimise processing by Adobe as the image would already be built and validated. Current/Experienced Behavior: Manual for devel

Request for Feature Enhancement (RFE) Summary: Allow to search for Assets by combination of options e.g. Created by, Created Date and Modified Date  Use-case:   goto aem activate filter Select created date - in last 2hours (same for all options) Select modified date - in last 2 hours (same for all options) Current/Experienced Behavior: Tick box now removed from created by and added to modified by Improved/Expected Behavior: Would expect to be able to filter by all 3? Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets CS, AEM Release ID 18175 Customer-name/Organization name: Jet2 Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Dispatcher GUI Use-case: Dispatcher management Current/Experienced Behavior: Not often it is cumbersome to develop, manage and trroubleshoot Dispatcher configurations, including those specifically belonging to Apache HTTP server. Improved/Expected Behavior: - I remember that back in the days there was a pretty good UI tool for managing Apache HTTP related configurations. It was called http://www.apache-gui.com/apache-windows.html and we can refer to it and check it out to see how it works.- I would propose to have a similar tool for managing Dispatcher configurations. Everything should nicely be viewed in a visual editor. It may contain hints and preferably validators that can be used during editing. The core engine for the tool can either be developed from scratch using maybe ANTLR or it may reuse the stuff that Adobe uses internal to read, interpret and apply the Dispatcher config. - I would be more than glad to participate and

Request for Feature Enhancement (RFE) Summary: Provide a means of permission and user-management for AppBuilder Applications (through Adobe IMS, AdminConsole) Use-case: When developing App Builder Apps, the question occurs how to give different users different permissions within the App (or access to the app at all).How can access to an App be granted or denied - and what about granual permissions within the app?How is permission-management / user-management within Appbuilder Apps handeled?IF we do not yet support something like that ..I think each app should have the ability for product profiles in the admin-console, which could then be customized to have as many different permission levels as required by creating additional profiles.(Naturally these should be easily available on runtime "OOTB" for developers to use. And not though something like the UMAPI - which is very cumbersome ... ) Current/Experienced Behavior: Unfortunately ORG level is the only granularity in terms of

Request for Feature Enhancement (RFE) Summary: Developer Console in AEMaaCS should display runtime environment variables values too - This helps to know which is the current value being picked (default or custom) Use-case: Currently the config.json displayed in the pod at cloud manager for an instance displays configuration for environment variable as is in the codebase -  "configKey": "/configValue/$[env:CUSTOM_KEY;default=9876543210]/rohan",   If the CUSTOM_KEY is configured in environment variable then the value that should be displayed is the actual one and not the above one. If it's not configured then the default value should be displayed to give a better idea of whether an environment value is configured for an instance or not. Current/Experienced Behavior: User has to navigate to the Environment Variable console to manually verify whether CUSTOM_KEY is configured or not. In a project with 150+ env variables this becomes an unnecessary lookup. Improved/E

Request for Feature Enhancement (RFE) Summary: The Cache metrics report generated by Adobe SME named "AEM CS BPO Tech Staff Report.pdf" monthly basis recommends improving the CDN Cache ratio but the way its generated needs to be revisited as the internal call, or URL forwarding requests, internal redirects are all being tracked differently causing the cache hit and coverage ratio scores reported low. Use-case: Ex: when the request is made for our website like fiserv.com gets (302) redirect to  https://fiserv.com and to https://www.fiserv.com/ in this case considered as different requests and reports miss or pass. As this is the homepage and the number of page visits to the homepages are high the score gets impacted significantly.   other examples like A) there are calls like /autodiscover.xml and other that gets originated from network or bots or health checks and not from core AEM application which also gets reported as MISS/PASS and impacts the score. B

Request for Feature Enhancement (RFE) Summary: Alias for Environment Names in Cloud Manager Use-case: We are working on AEM Cloud Service environment and due to our Business Strategy we were required to rename the cloud environments. I reached out to support to check on this topic. Unfortunately we do not have a possibility to rename or set another value to the name of the environment   https://experienceleague.adobe.com/home?support-tab=my-cases&case-id=E-001417728&org-id=21EC1DCC64F9DFD10A495FAA%40AdobeOrg#support   Current/Experienced Behavior: Due to this our customer is facing issue in remembering all the names which are not aligned with the business strategy Improved/Expected Behavior: Having Aliases will enable customer to have the names of the environment aligned to the business strategy Environment Details (AEM version/service pack, any other specifics if applicable): All Cloud Environments Customer-name/Organization name: PHILIP MORRIS INTERNA

Request for Feature Enhancement (RFE) Summary: We propose adding accessibility testing to the AEM Cloud Service Cloud Manager pipeline, providing a baseline assurance for compliance with the European Accessibility Act (EAA) and the Web Content Accessibility Guidelines (WCAG) 2.x.   By embedding accessibility checks directly into the CI/CD process, this feature would enable proactive identification and resolution of accessibility issues, fostering a more inclusive user experience and aligning with industry standards. Use-case: Compliance with Accessibility Standards (EAA, WCAG 2.x):Ensuring compliance with the European Accessibility Act (EAA) and WCAG 2.x is critical for organizations operating in Europe or serving global audiences. Automated testing within the Cloud Manager pipeline would provide a baseline for meeting these legal standards, reducing the risk of non-compliance and associated penalties. Early Detection of Accessibility Issues:By running accessibility ch