Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: AR/VR Authoring experience in AEM/ Integartion of Adobe Aero Use-case: Future proof content authoringAR e-commerce CMS experience. Current/Experienced Behavior: Authoring mode in AEM / Adobe Areo Improved/Expected Behavior: AR authroing experience.AR asset management.Using AR to create content. AR website experiecne. Adobe Aero Integartion. Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Organization name: NA Screenshot (if applicable):   Code package (if applicable):  

Hi, I'm looking for a way to make personalization (A/B tests, targeted ID, etc..) more visible on a page in editor mode for all authors. In classic UI the annotations are more visible and directly on the page. In Touch UI most authors do not notice the annotations in the right corner. Comments in the timeline could also be an option but that is still not very visible or specific.

Request for Feature Enhancement (RFE) Summary: It would be helpful in AEM Assets if the breadcrumbs were always visible, so that you can click directly on the selected parent folder.  Use-case:   Current/Experienced Behavior: Breadcrumbs not fully visible Improved/Expected Behavior: Breadcrumbs fully visible Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Maurine Zorko, REWE Markt GmbH / REWE Systems GmbH Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The "..."-menu in AEM Assets should always be at the end and the order of the menu items should also always be the same, so that you don't have to search for elements. Use-case:   Current/Experienced Behavior: Position of "..."- menu changes. Sometimes it's in the middle of the elements but you expect it at the end. Improved/Expected Behavior:   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: In AEM Assets you have to refresh manually to see changes. It would be helpful if this happens automatically. Use-case:   Current/Experienced Behavior: Changes are not automatically visible. Improved/Expected Behavior:   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: Integration tests and UI tests are executed automatically on the Stage environment as part of a Production pipeline. We would like to run our integration tests earlier, when pushing code to one of our Development environments. This would allow us to catch bugs early without risking the timeline of Production deployment. Use-case: We have two Development environments. One receives the latest code, another is used as a stabilization/bugfixing environment before a Production release. We would like to run our integration tests on the stabilization environment to catch issues early. Current/Experienced Behavior: Integration tests can only be executed against the Stage environment, as part of a Production pipeline. Improved/Expected Behavior: Integration tests can be executed against a Non-Production pipeline. This could be another toggle in the UI, in addition to the Deployment Trigger and Important Metric Failures Behavior toggles.

Request for Feature Enhancement (RFE) Summary: Add a Save As Button to the Image Set Creation Screen Use-case: Currently there is no option to select an existing image set to modify it and then save under a different name; keeping the original image set as is. Current/Experienced Behavior: We are creating images sets that vary slightly and are basically creating the same image set; just giving it a new name due to business. Improved/Expected Behavior: Saves time and efficiency as we need to search/re-create image sets rather than being able to select an existing image set to add/delete re-arrange images and save under a different name.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as CS Customer-name/Organization name: Ashley Furniture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: To fecilitate Component documentation on component dialog within AEM and remove external dependencies Use-case: Each custom component/ core compoenents need documenation like authroing guide/ component use-case doc etc. Current/Experienced Behavior: Currently we have to provide separate doc. in sites or word doc and is not integarted within AEM; Another approach: Also there is a way to use cusomized js to read and show the html to achive this. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/aem-components-markdown-documentation/ba-p/540904 Improved/Expected Behavior: To have a property something like within AEM :  granite/ui/components/coral/foundation/includeReadme  That takes an additional path property pointing to a ".md" file.   This enables author to view component docs, with ease and reduces efforts to use 3rd party sites/dependencies. Also as its associated within the c

Request for Feature Enhancement (RFE) Summary: Enable a reporting tool that can extract the list of all pages Use-case: Be able to generate a report about pages that should include basic properties a well such as page status (published or not) Current/Experienced Behavior: Right now, what's being recommended is ACS Report builder.  Improved/Expected Behavior: We want something that's truly out of the box not community created Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Proquire Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: In order to troubleshoot issues effectively each AEMaaCS should expose an upgrade log so development team can debug issues effectively (i.e. there was no feature deployment and something stopped working all of a sudden).   Information I'd like see inside:- timestamp- AEMaaCS version/release prior to and after the (up|down)grade - who (or what; mind that RO/RV is out there) scheduled/triggered a deployment- is given version already deployed or a deployment has to take place to enforce that- notes (i.e. if the upgrade was requested via support ticket then I'd love to see a reference to that)   Moreover it'd be great if such a log is available via Cloud Manager API (1 per environment). Use-case: Identifying if, why and though whom an upgrade was executed (also to analyze why some feature "suddenly fails") .If a feature fails to work through an upgrade - this is impossible to determine or debug. Current/Experienced Behavior:

Request for Feature Enhancement (RFE) Summary: At the time of writing AEMaaCS environment API [1] does not allow me to: inspect which version of AEMaaCS given environment runs check if the version I have is the latest upgrade the environment programmatically. The only way to do it is via Cloud Manager Web UI (non PROD envs) or support ticket (STAGE/PROD). The latter may not be something Adobe considers doable (due to RO/RV), but we'd love to see such a feature for lower level environments. We has dozens of dev environments spread across multiple programs, so it is cumbersome to keep them in sync [1] https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#tag/Environments Use-case: enable to "automate upgrades" and across many  programs and environments (customers with up to 10 programs) - and to understand current and latest available verison. Current/Experienced Behavior: API and CLI do not provide information on * current AEM version of en

Request for Feature Enhancement (RFE) Summary: Published Status Visualization with colours Use-case: People with access to an AEM author should be able to be quick in recognizing a node as “never published”, “published”, “unpublished”, “modified” and/or “locked”. This should be true in each of the view modes, “Card View”, “Column View” and “List View”. Current/Experienced Behavior: a) In Column View, there user has no possibility to get a quick view of the published states. The status of a single file can be verified only when clicking it. b) in Card View a user can see the published status but also does not easily detect whether a node is published or unpublished – although the cards can vary in size in case they need to show more meta data. c) In “List View” a user gets the only possibility to get a pretty quick view of the matter, although – as said earlier – the different icons look pretty alike. Improved/Expected Behavior: If the three view modes would be enriched with co

Request for Feature Enhancement (RFE) Summary: Enable toggling side panel while using any component's dialog. In general, whenever a author tries to author and image or drag any asset on to the component, the author might require the side panel to be toggled on before even opening the dialog.So how about we provide the ease of accessing side panel while editing the page even when the author opened the dialog box. Use-case:   Current/Experienced Behavior: Author is not able to open side panel when component's dialog is opened. Improved/Expected Behavior: Author should be able to open/toggle side panel when component's dialog is opened in order to drag any asset. Environment Details (AEM version/service pack, any other specifics if applicable): All versions Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):     I saw a few solutions to make this possible with some custom JS but I believe it would be

Request for Feature Enhancement (RFE) Summary: Adding syntax highlight feature in CRX DE editor Use-case: While updating HTML/CSS/JS file in CRX DE editor, it should highlight the syntax. It will give a better understanding and help to navigate quickly to the particular element of the code. Current/Experienced Behavior: Currently, it is not highlighting the syntax for any of the files Improved/Expected Behavior: at least a basic syntax highlight should be there. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 On-Premise   AEM Cloud as a Service Customer-name/Organization name: Bounteous Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary:   Use-case: AEM is sending duplicate content to the third party applications like smartling when the page is submitted for the translation which has Experience fragment referred in it. Example: Let's assume, we have a page where experience fragment component is used. The moment experience fragment is added on the page, 'text' property gets created at node level and all the experience fragment content will be stored at page level as well which is not required.   Current/Experienced Behavior: 'text' property gets created at node level and all the experience fragment content will be stored at page level as well which is not required. Improved/Expected Behavior: 'text' property should be removed Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.12 Customer-name/Organization name:   Screenshot (if applicable):   Steps to reproduce:  1. Create Experience f

Request for Feature Enhancement (RFE) Summary: Match previous AEM versions that allowed for stackable metadata profiles where folders accepted multiple metadata profiles Use-case: Larger libraries with multiple levels of folders can quickly apply metadata during upload/processing without the need to endlessly create new profiles for every folder. Current/Experienced Behavior: In AEM Cloud, a metadata profile assigned to a child folder neglects/ignores the profile applied to the parent. Improved/Expected Behavior: Can there be a toggle option to inherit the parent folder metadata profile in addition to the one applied to the child folder. This toggle option to "Accept Parent Folder Metadata Profiles" could be within folder properties on the Asset Processing tab. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a Cloud Service Customer-name/Organization name: Dominique Green / Keurig Dr Pepper Screenshot (if a

Request for Feature Enhancement (RFE) Summary: AEM template/component policy enhancements Use-case: Ability to easily make policy updates and see a record/history of updates in AEM Current/Experienced Behavior: When policies are manually changed, there is no record/history of changes, which makes policy management difficult when there are multiple template editors A code deployment is needed to make quick CSS changes needed for policies Improved/Expected Behavior: Ability for template editors to see a record/history of all manual changes made to a template/component policy, when and by whom in AEM Ability for admins to make quick CSS changes needed for policies in AEM in ACS e.g. ability to upload CSS packages in ACS, similar to what could be done in CRXDE in AMS Environment Details (AEM version/service pack, any other specifics if applicable): AEM Customer-name/Organization name: Deloitte Screenshot (if applicable): N/A Code package (if applicable): N/A

Request for Feature Enhancement (RFE) Summary: In AEM we have an out-of-box capability to have AEM OSGI Events sent to Adobe IO: https://developer.adobe.com/events/docs/guides/using/aem/ https://github.com/adobe/aio-lib-java/tree/main/aem/aio_aem_events/src/cs/content/jcr_root/apps/aio-aem-events/osgiconfig/config.author One of these OSGI events is for the Page Publish event in which we can have an external webhook notified when this event in AEM occurs. Additionally we have the Managed Publication feature which allows for content authors to publish a page to a "Destination" such as the Publisher environment or a Preview environment. In my use case I have an external webhook configured to receive Page Publish event. In my test I used the Managed Publication feature to publish the same page first with the "Publish" destination and then again with the "Preview" destination. In both cases my external webhook is receiving the event properly, however the Adobe IO event payload between th

Request for Feature Enhancement (RFE) Summary: Be able to preview Office assets on AEM. Currently, we only get to see the first page of PPTX and DOCX files  Use-case: Be able to page through PPTX and DOCX files uploaded Current/Experienced Behavior: Currently, we only get to see the first page of PPTX and DOCX files  Improved/Expected Behavior: Have the ability to page through Office Assets Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add a feature that will allow users to comment on assets like product reviews. The commenting on the timeline view is not intuitive since it seems more appropriate to be used for asset revision or updates Use-case: Be able to "product review" or comment on assets Current/Experienced Behavior: No dedicated area for "product reviewing" assets Improved/Expected Behavior: A dedicated tab or area for commenting on assets Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Hi Team,Currently we are using AEM 6.5.11.0 for assets project. Suppose if user navigate to search results page and if assets are more than 1000 then once user click on select all it is showing text count as 1100+ selected. So as a user it is confusing to them and is there anyway to remove plus and show accurate. As a product owner could you please check and let us know how to show the accurate count. Use-case: Hi Team,Currently we are using AEM 6.5.11.0 for assets project. Suppose if user navigate to search results page and if assets are more than 1000 then once user click on select all it is showing text count as 1100+ selected. So as a user it is confusing to them and is there anyway to remove plus and show accurate. As a product owner could you please check and let us know how to show the accurate count. Current/Experienced Behavior: Hi Team,Currently we are using AEM 6.5.11.0 for assets project. Suppose if user navigate to sear

Request for Feature Enhancement (RFE) Summary: Sort by custom metadata field in ListView (AEM Asset) Use-case: User should be able to use custom data fields to sort assets in list view Current/Experienced Behavior: Currently only sorting of out-of-the-box data fields is supported without altering the core code of the application. Improved/Expected Behavior: The user should be able to sort by data fields that are added with a specific use case in mind. e.g. checking when an asset has last been used in a given context.    Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 9 Customer-name/Organization name: Spar Austria Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: A quick indicator that a page has unpublished changes (e.g., something like a blue dot that indicates an unread message) Use-case: Large websites that get change requests from different avenues. Sometimes they overlap, creating issues when other changes get published before they should. Current/Experienced Behavior: An author must do a good deal of sleuthing through version history to find out if there might be unpublished changes to a page. That information can still be incomplete at times, depending on the workflows the previous author executed. Improved/Expected Behavior: An author would see this easy indicator on the Site Admin screen, so they could know immediately if there are unpublished changes. It will also serve as a reminder to publish the changes if they should be published. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.4 Customer-name/Organization name: U.S. Bancorp Scr

Request for Feature Enhancement (RFE) Summary: In AEM 6.4, we are able to configure audit logs for have audit logs for User and group changes (creating/deleting users/groups and adding/removing users from group) but not for ACL permission changes. Having audit logs for ACL permission changes will be of great help when a content author reports an issue that he's not able access a path anymore for which the user had access to previously.  Use-case: This feature will be helpful where the content authors report issues saying they lost access to a specific path for which they had access earlier. Current/Experienced Behavior: No Audit logs for ACL changes, We have audit logs only for User and group changes (creating/deleting users/groups and adding/removing users from group) Improved/Expected Behavior: Audit logs for ACL permission changes done for a user/group Environment Details (AEM version/service pack, any other specifics if applicable): 6.4.8 Customer-name/Organi

Request for Feature Enhancement (RFE) Summary: DAM Librarians want to be able to multi-select images with Smart tags, and click Manage Tags, to remove/edit Smart tags in bulk. Use-case: DAM Librarians want to be able to multi-select images with Smart tags, and click Manage Tags, to remove/edit Smart tags in bulk. Current/Experienced Behavior: Tags can only be edited on a single asset at a time via the UI. Improved/Expected Behavior: Tags can be removed/added to multiple assets when selected via UI as a multiselect. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.9+ Customer-name/Organization name: Humana Screenshot (if applicable):   Code package (if applicable):