Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Locked pages should prevent other users from editing the content; however, it should allow the content to get copied because the content can still be viewed. A locked page should Only restrict other users from editing the page. Use-case: We have Toolkit area which guides our Authors on how each component works. Additionally, we provide many samples to help authors come up with ideas for building new pages. All of those pages — which we refer to as Toolkits. As we have locked all these pages to protect from any unauthorized changes, it also prevent our Authors to copy those samples or examples. Therefore, it will be good if locked pages only prohibit users from ed

Request for Feature Enhancement (RFE) Summary: Heap Utilization Warnings and graphs on Reporting console should match the heap memory usage on servers Use-case: The Cloud Manager Portal - Reports displays a System Monitoring stat for all the environments and servers in terms of Host, Network, Storage and Application. Sometimes it displays in warning "Heap size is 85% of the allocated memory"If you check the server in question, mostly the figures don't align - For instance in the publish server for which the warning was flashed the usage was around 35-40% which is way off the warning limits.Ideally there should be a strong co-relation between these 2 figures. Current/Experienced Behavior: The overall heap memory usage in /system/console/memoryusage does not align with the Reporting console in Cloud Manager. Improved/Expected Behavior: The overall heap memory usage in /system/console/memoryusage should align with the Reporting console in Cloud Manager. Environment De

Request for Feature Enhancement (RFE) Summary: This RFE proposes integrating AI capabilities into AEM to assist content creators with curation and content suggestion functionalities. Use-case: Content creators often spend significant time searching for relevant assets and information to build compelling content pieces. This can be particularly challenging when managing large content repositories. Current/Experienced Behavior: Content creators rely on manual searches and browsing through folders and tags to locate relevant assets. This process can be time-consuming and inefficient, especially for complex content structures. Improved/Expected Behavior: Integrate AI-powered content suggestion features within the AEM authoring environment. As a content creator drafts their content, the AI suggests relevant assets (images, text snippets, related articles) based on the current context. The AI considers factors like keywords, themes, content type, and past user behavior to deli

Request for Feature Enhancement (RFE) Summary: Request to add "find location of asset" feature in search results in Brand Portal which is already present in AEM DAM. Use-case: 1. We login to Brand Portal 2. We do a search for lets say "Truck" keyword in search bar. 3. Lets say, 25 assets show up in the search results. 4. Now, we want to navigate/go to the location/folder of any of one of these 25 assets. 5. Need an option to go to the location/folder of the asset. Current/Experienced Behavior: Currently we can only see the path of the asset like /content/dam/ Improved/Expected Behavior: The user can directly go to the location of asset. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a cloud service 2024.4.15860.20240410T113939Z-240300 Customer-name/Organization name: NA Screenshot (if applicable): Need the same option in Brand Portal as AEM DAM reference as shown below:         &nb

Request for Feature Enhancement (RFE) Summary: Request to improve behaviour for View in Admin button during page editing. Use-case: When user clicks “View in Admin” he or she expects that the same page will be opened in sites admin. Usually pages have many children, so it takes time to find edited page again. Current/Experienced Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin”   Opened parent page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience Improved/Expected Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin”   Opened edited page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten Environment Details

Request for Feature Enhancement (RFE) Summary: Instead of free form field when adding a content fragment variation, provide authors a pre-populated list of variation titles to choose from. Use-case: Content Fragment Variation titles are often used across an application. Current/Experienced Behavior: Author must type in correct variation title Improved/Expected Behavior: Allow developers to provide a list of variations for authors to choose from Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Customer-name/Organization name: UHG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enhancing Search Feature of Connected Assets with Path based search to Remote Assets in AEM 6.5 Use-case: Authors uses Assets finder in Media Library by using search features such as Keyword,Path,Tags etc. Whereas in Connected Assets 6.5 we just have search by Keyword|Tags but its not supporting Path based search which is a big degradation in author experience when they switch to use connected assets from AEM Assets Current/Experienced Behavior: AEM Author when using Connected Asset to fetch an Asset from Remote Asset unable to search Asset bu Path similar to Asset finder in media library Improved/Expected Behavior: Include Search feature similar to Asset Finder of Media Library Which is path based search in AEM 6.5.I hope this feature is available in CaaS. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP17 Customer-name/Organization name:   Screenshot (if applicable): &nbsp

Request for Feature Enhancement (RFE) Summary: This is an outcome of support case - E-001180834. The support team determined that when the content copy tool is run for AMS linked cloud manager the tool fails if there were any modifications in the copy source Use-case: The tool is used frequently to downstage the content from prod back to the lower environments. It is not practical to pause all activities in the environments to perform the stage down Current/Experienced Behavior: Content copy tool breaks in cases if the server content is updated Improved/Expected Behavior: Content copy should run independent of system usage Environment Details (AEM version/service pack, any other specifics if applicable): AMS - AEM 6.5.16 Customer-name/Organization name: Philip morris international Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enhancing the IP Allow Lists functionality in Adobe Program Overview for Experience Manager Use-case: Providing users with IP Whitelist access to specific domains Current/Experienced Behavior: Recommendation 1 -  Improve how environments are applied for an IP Allow List Name. Currently, you have to go into the specific environments and add the IP for all relevant segments (author, publish, preview).     Recommendation 2 -  When adding an IP Allow List Name to the dispatcher/publish environment, there is no warning that this will stop all other users from viewing this environment. This can sometimes be an easy mistake with a significant impact.   Improved/Expected Behavior: Recommendation 1 -  Improve how environments applied are adding for a IP Allow List Name. Allow admins to add/remove environments in IP Allow List view provided below.     Recommendation 2 -  Add an alert for this

Request for Feature Enhancement (RFE) Summary: Cloud Manager - Table view - Order table data by column Use-case: Example:"Cloud Manager" -> "Services" -> "Domain Settings".We have round about 100 Domains configured in "Domain Settings".The Domains are listed in a table view with pagination function at the bottom.The latest Domain entry is alway on top of the table.We would like to have a function to order the table data by each column (Domain Name; DNS Record; SSL Certificate attached; Environment applied) Current/Experienced Behavior: You can't change the order of the data in any table view within cloud manager to get a better overview Improved/Expected Behavior: You can order table columns in all cloud manager views Same feature would be helpful on all other table views within cloud manager to be able to order table data Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: B. Braun SE Scre

Request for Feature Enhancement (RFE) Summary: As of now AEM author session is getting logout either user is active /inactive.is it possible to add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work  Use-case: it is useful for author to get notified to save their work. Current/Experienced Behavior: As of now AEM author session is getting logout either user is active /inactive. Improved/Expected Behavior: To add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work  Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 cloud Customer-name/Organization name: Shell Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently asset management is interlocked with site management, i.e. moving assets in the asset module requires republishing of pages in the sites module instead of just updating the asset references in the affected pages, especially on Publish. Use-case: We have dedicated asset and site managers. When an asset manager moves an asset the site manager is required to republish the page(s) with this asset to update its references on the page. This can become a hassle when page(s) with the asset are being reworked. These pages are not ready to be republished. Due to this dependency asset and site managers cannot work independently. Current/Experienced Behavior: When assets are being moved, affected pages need to republished Improved/Expected Behavior: When assets are being moved, asset links on affected pages should be updated without the need to republish the page Environment Details (AEM version/service pack, any other specifics

Request for Feature Enhancement (RFE) Summary: Enhance the publish/unpublish process on blueprint pages with a warning if the rollout configuration "Activation on Blueprint activation" or "Deactivation on Blueprint deactivation" is in place. Use-case: To efficiently manage large website the ootb rollout configs "Activation on Blueprint activation" and "Deactivation on Blueprint deactivation" are available, see: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-sync If you have set this up for e.g. on livecopy root page there is no indicator available which shows the editor, maintaining the blueprint page, that with publish a blueprint page or unpublish this action takes also place on the livecopy. So, it could happen that accidentally a livecopy page goes on or offline. Current/Experienced Behavior: No hint for the editor once he publishes or unpublishes a blueprint page that on the connected livecopy page the sa

Request for Feature Enhancement (RFE) Summary: Our system currently sends out automated emails to an uploader when an asset they uploaded expires. Would like to have the ability to this email to go out to more than just the uploader? Use-case: A team to have the ability to see when an asset has expired instead of one person. Current/Experienced Behavior: Our system currently sends out automated emails to an uploader when an asset they uploaded expires Improved/Expected Behavior:  A group of AEM members to have the ability to see when an asset has expired instead of one person. Environment Details (AEM version/service pack, any other specifics if applicable): AEMAACS Customer-name/Organization name: Epsilon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Move/Copy of Context-Aware Configurations when a page is moved/copied Use-case: Pages with special CAC's (like header, footer ...) are moved/copied and all the CAC's have to be manually set again in the destination tree. Current/Experienced Behavior: When a page with specific Context-Aware Configs (set below it) is moved or copied then all the CAC's (below /conf) remain in the same place so the editors have to redo the configurations every time. Improved/Expected Behavior: It would be easier that when page (or complete tree) is copied or moved that also it's related CAC's (/conf) are also copied/moved. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.4.16145.20240430T082417Z Customer-name/Organization name: Pictet/One Inside Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently for deploying code to RDE, developers have to use aio rde plugin and don't have a provision for configuring a pipeline to directly deploy through a branch. Also, huge packages of content need to be moved either through aio or via package manager. User should have a provision of deploying code through quick pipelines which are meant for simply deployment and should also have a provision for quick content movement from DEV/Stage/PROD environments to RDE. Use-case: Quick deployments to RDE Current/Experienced Behavior: time consuming process for making a RDE in complete working state Improved/Expected Behavior: Quick deployments to RDE Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: GSPANN Technologies Screenshot (if applicable):   Code package (if applicable):