Adobe Experience Manager

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

Request for Feature Enhancement (RFE) Summary: Add caption and copyright to Image component policy Use-case: Our clients have legal issues with artists due to copyright not being shown. Authors forget to enable the checkbox. But they never forget the caption, because it's auto-enabled by policy. Current/Experienced Behavior: Author adds image to page Author edits properties Author enables "Get copyright from DAM" Author clicks Done Improved/Expected Behavior: Author adds image to page But that is only possible of the options "Get copyright from DAM" and "Display copyright" are added to the Image component policy and we as admin can enable them as default for our clients. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.10.18311.20241017T104455Z Customer-name/Organization name: Verlag des ÖGB GmbH Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Creating customised triggers in error logs. For an instance when a trigger for Null pointer is placed in the logs file then an email alert should be triggered when Null pointer is encountered in that log file. Use-case: Monitoring the expected errors  Current/Experienced Behavior: There is no notification kind of feature for error logs, download the log file and check the logs. Improved/Expected Behavior: An alert for customised errors in log file  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 onprem Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Adding rules to custom metadata fields in metadata form in Assets UI Use-case: A user wants to narrow the search for a particular asset by using fields where the parent is selected, only the remaining values of the children field are displayed to use.   An example is Brand/Subbrand. There may be 20 values in the brand, but there are 5 unique subbrand values under each brand. Current/Experienced Behavior: Rules are not available in Assets UI Improved/Expected Behavior: Add rules functionality or an alternative Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Hershey Screenshot (if applicable): Admin UI view Code package (if applicable):