Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: When using the new AEM view, the default columns that are available to users in the Configurable Columns settings should be customizable in two ways:1. Admins should be able to add/remove metadata fields (especially custom metadata fields) to the overall list available to users.2. Users should be able to select attributes relevant to their workflow experience and save the configuration. Note: Users being able to save/load multiple configurations for different workflows would be nice. Use-case: Current fields offered in Configurable Columns are limited and not applicable to many of our users. The ability for admins to offer custom metadata in these columns would eliminate bad habits by decreasing the need for users to include these values in asset file names in order to see them easily. Current/Experienced Behavior: Current metadata available to view in Configurable Columns is locked to 9 default values. Improved/Expected Behavio

Request for Feature Enhancement (RFE) Summary: Pickers must remember their last location and start from there  Use-case: Our editors create pages on specific topics and upload assets related to that topic. They very often upload the assets into the same folder to have everything in one place. Then they start to build a page and add the assets to the page.  Current/Experienced Behavior: For the first image asset:  1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm   For the second image asset: 1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm   ... repeat for each asset Improved/Expected Behavior: For the first image asset:   1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Co

Request for Feature Enhancement (RFE) Summary: Introduce a tile where editors can go to see their 15 recently edited pages, assets, experience fragments -etc. incl. links to them and their parent folders. Use-case: Our editors have a newsroom culture. They must quickly put content out there. They can get interrupted to do another task and continue later.  Current/Experienced Behavior: Currently, they just have the option to open all pages, assets -etc. one by one using the various locations in AEM and continue work then. Improved/Expected Behavior: In future they could just go to the Recently Used and re-open all their work from within one single place. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: VERLAG DES ÖGB GMBH Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Need access to old Blue environment after Blue/Green switch Use-case: To evaluate roll-back decision based on the issues found after Blue/Green switch we need to be able to verify issue is introduced due to the change, or existing issue. Current/Experienced Behavior: Currently, old Blue environment is only accessible by Adobe, and not integrated with the rest of the systems. Improved/Expected Behavior: Instead of putting the old Blue environment away, place them into the Green Load-Balancer, so that Green URL can be used after the switch. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager for AMS deployment Customer-name/Organization name: Go Endo Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add Save as Version to Page Information menu Use-case: Many of our users miss a saving button. We don't promote that. Their need is to: Create page Modify it to their liking Save the page once they reached a "milestone" Colleagues then publish the "milestone" version or use it for approval The main editor continues working on the page Currently, the main editor must leave the page editor, go the Content Tree and create a version from there. They wish to create a version from within the page editor. Current/Experienced Behavior: The menu is not existant yet.   Currently: User must close the page editor User goes to location of page User selects page User switches to the Timeline sidebar User clicks the three dots at the bottom (see screenshot) User clicks Save as Version User fills in Label User fills in Comment User clicks Create System saves Version Improved/Expected Behavior: User clicks Page Information menu (see

Request for Feature Enhancement (RFE) Summary: Add a column with path (/content/...) to the search result list in Sites Console. Use-case: As an editor I want to search for pages which contain a special keyword in the name and/or title. In the Sites console I use the search functionality and enter my keyword to find those pages. Current/Experienced Behavior: The search result contain name and title of the pages (and also other information) but the important information where the pages are located is NOT visible - there is no column or information which is displayed via mouse over. So, I need to open each search result to get to know about location - this is not efficient! Improved/Expected Behavior: Have a column with a path available so that editor sees at on glance the location information Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code pa

Request for Feature Enhancement (RFE) Summary: When text is highlighted (or selected) in the Author view of the content. fragment editor, it would be ideal to see the same highlighted info in Source view. Use-case: 1. In the content fragment editor Author view, select or highlight a link or sentence.2. Go to Source view; the same piece of information should also be highlighted or selected. Current/Experienced Behavior: Text selected in Author view is not selected in Source view Improved/Expected Behavior: Text selected in Author view is also selected in Source view and vice versa Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.19.0 Customer-name/Organization name: Verizon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Customer when using Adobe Managed Services, the AMS team used a distribution list that client managed (they could add and remove users) internally. Then, that list appeared on the notifications so they knew who received the notices. Unfortunately, for AEMaaCS, they can only see their individual names, so it's not very reassuring. Hence, customer would like to have a similar option as in AMS for AEMaaCS. Use-case: Handle, managing with more control proactive / incident notifications. Current/Experienced Behavior: When receiving incident/proactive notifications in AEMaaCS, customer can only see their individual names in the recipient list, not all. Improved/Expected Behavior: Include a distribution list that client manages (add and remove users) internally. Then, show the list on the notifications so they know who received the notices. Environment Details (AEM version/service pack, any other specifics if applicable): AE

Request for Feature Enhancement (RFE) Summary: Customer would like to have available logs related to Proactive/Incident notifications in their end for troubleshooting Use-case: In case a notification presents irregularities, customer would like to have logs available for knowing what's happening in the backend and proceed with trouble. Current/Experienced Behavior: No logs available for customer. Improved/Expected Behavior: Getting access for notification logs and get details about who received, managed, included in proactive / incident notifications. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Nordstrom  Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The Add Content menu is not available in Manage Publishing of XF (Experience Fragment).I want to use the Add Content menu. Use-case: We can launch multiple publishing workflows at once for pages (sites),but this is not possible with Manage Publishing of XF (Experience Fragment). I want to use the Add Content menu for XF (Experience Fragment) as well as for pages (sites).   Background There are many cases where XF (Experience Fragment) is launched in a publishing workflow at once, and the current function does not allow efficient work. Current/Experienced Behavior: The Add Content menu is not available in Manage Publishing of XF (Experience Fragment). Improved/Expected Behavior: We want to use the Add Content menu for XF (Experience Fragment) as well as for pages (sites). Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.4.16145.20240430T082417Z Customer-name/Organization

Request for Feature Enhancement (RFE) Summary: Update Timewarp functionality to work with nested launches and with launches utilizing experience fragments.  Use-case: Successfully utilize Timewarp functionality within all AEM  launches, to avoid capturing manual screenshots of all scheduled updates to have on record. This will allow us to compare our home page to older versions of itself in order to compare metrics, trends, and any other data needed to help us improve our business.  Current/Experienced Behavior: Timewarp does not work as desired for Nested Launches or when experience fragments are used. The experience fragment is not loading when the page is viewed in Timewrap or the Version UI for Preview or Compare versions. The experience fragment does load appropriately if it was part of the initial template.    Our process for home page launches today involves creating nested launches off each Sunday's home page. The breaking the inheri