Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Provide Composite fields in multifield Use-case: As an CF editor, I want to add different type of values as a combination and I would prefer to use a field like composite multifield (same as we have in component dialogs) Current/Experienced Behavior: Currently no composite field is available for CF Improved/Expected Behavior: Composite multifield allowed for CF Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: On Modification of page needs amber colour flag display in sites console when page is selected  Use-case:   Current/Experienced Behavior: It just displays page modification date , last published date etc, no colour flags to display which cold help alerting page is in modified stage. Improved/Expected Behavior: On Modification of page needs amber colour flag display in sites console when page is selected . <meta charset="utf-8" /> It makes life easy for authors to avoid any draft page publication as modified date displayed might not get attention as amber color flag does. Environment Details (AEM version/service pack, any other specifics if applicable): AEM SaaS Customer-name/Organization name: Unilever Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Search on the same page DAM and Adobe Stock Assets using filters (DAM path, asset type, etc) Use-case: On the one page in AEM we can search for Adobe Stock. On the other page in AEM we can search DAM assets. Is it possible to search on the same page DAM and Adobe Stock Assets? Current/Experienced Behavior: it is not possible to search on the same page DAM and Adobe Stock Assets using filters (DAM path, asset type, etc) Improved/Expected Behavior: it is possible to search on the same page DAM and Adobe Stock Assets using filters (DAM path, asset type, etc) Environment Details (AEM version/service pack, any other specifics if applicable): https://author-p131706-e1282790.adobeaemcloud.com/ Customer-name/Organization name: Legrand Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: With AEM 6.4 SP8, Adobe introduced restriction that only members of the AEM administrator group could publish to the Brand Portal. This request is to align publishing permission for the Brand Portal with the standard replicate ACL. Use-case: An AEM Assets user--i.e. a designer or a marketer--completes work on an asset and would like to publish the asset to the Brand Portal. The administrator for AEM would like to be able to grant that user the permission to publish their assets to the Brand Portal without making them an administrator (and granting many permissions which are inappropriate for their role). Current/Experienced Behavior: Only members of the AEM administrators group can publish to the Brand Portal Improved/Expected Behavior: Users with replicate permissions on the asset or folder can publish to the Brand Portal Environment Details (AEM version/service pack, any other specifics if applicable): This is applicable since

Request for Feature Enhancement (RFE) Summary: If someone is migrating to AEM and now want to add whole folder in assets without choosing single files. So, to reduce production time there should be option to upload a folder in AEM assets. Use-case: It will help to upload folder in assets and helpful in bulk assets upload. Current/Experienced Behavior: Currently there is no option for uploading folder in AEM assets while we upload DAM assets to AEM Assets. Improved/Expected Behavior: It will be helpful to upload a complete folder of assets instead of single assets file. Environment Details (AEM version/service pack, any other specifics if applicable): All Versions. Customer-name/Organization name: Bhavi Screenshot (if applicable):   Code package (if applicable):      

I have good experience on SharePoint and other CMS's, one thing I noticed when I compare AEM with others, the Recycle Bin is not available in AEM.If content authors accidentally delete any pages or assets, then it is difficult to get it back, sometimes they need to depend on developers to get it back and it is time consuming process, are there any plans to implement the same in future releases? 

Request for Feature Enhancement (RFE) Summary: Developers should have a read-only view of CRX/DE for debugging purposes Use-case: Debug deployment issues, check paths and properties Current/Experienced Behavior: Currently AEMaaCS has repository browser but it has limitations - It is sometimes not showing few paths/folders even though it is there in author/publisher. It requires separate access via developer console and not all developers may have access to that. Improved/Expected Behavior: Simplifies read-only view of crx/de is a better way to provide access to author and publish repository. Developers should even have this in production so that issue resolution for production content issues or code deployment issues can be expedited. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS author and publish environments Customer-name/Organization name: GSPANN Technologies Screenshot (if applicable):   Code package (if applicable

Request for Feature Enhancement (RFE) Summary: I know this was previously available as part of the AEM social package and then unsupported with the move to AEMaaCS, but our organization (and I believe most others as well) would greatly benefit from using a native 5-star rating system on our assets, interactive from the card view and sortable in the list view. Use-case: Particularly with our photography assets, we have a process in place to rank images on a 5-point scale from Best to Worst, which directly translates into how people are discovering and using these assets in other marketing materials. Having the stars on the card and properties view--both to actually apply the rating as well as to immediately have the visual cue (like how it's managed in Adobe Bridge)--would be extremely helpful, and would create the ability to filter out lower rankings, sorting assets in the list view according to ranking, etc. It would also be a very intuitive, user-friendly enhancement as a star-r

Request for Feature Enhancement (RFE) Summary: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Use-case: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Current/Experienced Behavior: Asset are allowed to publish wit

Request for Feature Enhancement (RFE) Summary: Show an indicator (small lock symbol) also within the List and Column View to give and editor to see at one glance which pages are locked. Use-case: As an editor I want to see "outside" which pages are locked and from whom. E.g. when I do a publish with children this will fail if one child page is locked because version creation is not possible in that case. Current/Experienced Behavior: Only in Card View you have this small symbol which indicates that page is locked. On hover you just get the information "Locked" without the user who is locking it! Improved/Expected Behavior: In every view of the Sites console the information if a page is locked should be displayed. In addition to that the information which user locked the page should be available (on hover for Card and List and as text item in Column view. In the old Classic UI this was in - not sure why in TUI is has been removed. Environment Details (AEM version/service pa

Request for Feature Enhancement (RFE) Summary: Remove limitation how many columns can be shown in the List View. Use-case: As an editor I want to see despite the standard columns also ones showing e.g. translation status or analytics data at on glance. I want to be flexible which columns I want to see according to my field of works. Current/Experienced Behavior: Currently you can only select up to 7 columns which should be shown in the list view. But there are a lot of more columns which could display additional information. So, you can't have all information at one glance or even an additional column to be shown apart from the standard ones. Improved/Expected Behavior: Remove limitation and let user decide how many columns he wants to be displayed depending on the use case he has. We have responsive UI, this should be no problem! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Scree

Request for Feature Enhancement (RFE) Summary: Cloud Manager Deployment: Add emergency production deployment pipeline Use-case: LGE.com is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as

Request for Feature Enhancement (RFE) Summary: Sort the list of groups in the User Profile alphabetically. Use-case: As an administrator I want efficiently check to which groups a specific user is assigned to. Current/Experienced Behavior: After opening the user profile and selecting the tab "Groups", the list below the headline "Groups that this user is a member of" is not sorted, it just displays the group names randomly. You need to scroll through all the list to check if a certain group is in. Improved/Expected Behavior: The list below the headline "Groups that this user is a member of" should be ordered alphabetically to easily get an overview! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

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

  Request for Feature Enhancement (RFE) Summary: As a DAM Asset Report user, when I try to create a "Download" asset report, I should be able to see a default "Downloaded by" option in the default column. Use-case: User should be able to generate a report of the assets in a given path, associated with the users list who have downloaded those assets, in a column Current/Experienced Behavior: There is no option to know about the users who have downloaded the assets in author environment. However, the feature is present in Brand portal Improved/Expected Behavior: "Downloaded by" column should be available while creating "Asset Report" of "Download" type Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.4 with planned upgrade to 6.5.7 by installing the service pack Customer-name/Organization name: Oxford Properties Screenshot (if applicable):     Code package (if applicable):