Adobe Experience Manager Sites

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):  

Request for Feature Enhancement (RFE) Summary: Allow administrators to create API keys to use to authenticate with  Download Center. This feature would also include an API to download from Download Center. This would improve security for customers, as they do not have to maintain the security of downloaded items. Use-case: Be able to download via an automated process without authenticating with individual user credentials Current/Experienced Behavior: Download Center requires an interactive login Improved/Expected Behavior: Download via automated processes, such as shell scripts using curl Environment Details (AEM version/service pack, any other specifics if applicable): n/a Customer-name/Organization name: Hilti Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add custom fields to file details Use-case: User needs to see more custom metadata right in Asset Link to pick the correct asset. e.g. different product mutations Current/Experienced Behavior: Asset Link displays a small standard set of information within the file details page. Improved/Expected Behavior: Asset Link file detail can be customized or a metadata page is added which shows a set of extended data stored with the asset.  Environment Details (AEM version/service pack, any other specifics if applicable): InDesign 202217.0.1 AssetLink3.1.65 AEM 6.5SP9 Customer-name/Organization name: Spar ICS + Spar Austria Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Allow the filter categories in Asset Link to be customized either via a settings json or in the backend of AEM. Use-case: Even the out-of-box version of AEM offers way more metadata fields that would be useful filters.  Current/Experienced Behavior: Currently there are only two filters in Asset Link. File type and Last modified. Improved/Expected Behavior: Filter would help to speed up workflows and enrich the UX.  Environment Details (AEM version/service pack, any other specifics if applicable): InDesign 202217.0.1 AssetLink3.1.65 AEM 6.5SP9 Customer-name/Organization name: Spar ICS + Spar Austria Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Option to restrict the characters allowed in Create Tag Wizard using Regex Use-case: During SOLR/other third-party apps/service integration  Current/Experienced Behavior: As '+' is not converted to '-', this is causing some issues in our project. Especially, when tag data flows from AEM to SOLR and vice-versa. Improved/Expected Behavior: Let the customer decides, what all character needs to be allowed in creating Tag/Namespace Wizard Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.9 Customer-name/Organization name: Agilent Technologies Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: having the ability to open the blueprint control center (classic UI) in aem cloud service, Currently, any classic UI tool is disabled on cloud service, and the blueprint control center provides an interesting and useful option to manage MSM. I know about Live Copy Overview tool but blueprint control center has more options and its more helpful for business need Use-case: As a user, I need blueprint control center to manage MSM with options to check all the page status, rollout it out, restore any page deleted, restore any component canceled inheritance in one place Current/Experienced Behavior: I cannot access blueprint control center on cloud service Improved/Expected Behavior: to able to access blueprint control center on cloud service Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Accenture Screenshot (if applicable):   Co

Request for Feature Enhancement (RFE) Summary: Right now if business authors wants to move asset and rename in bulk they can first move assets in bulk from one folder to another, but they can't rename in bulk, at a time one asset we need to rename. Which is time consuming. Use-case: Ability to provide bulk move and rename functionality , so they can accomplish task in one go.  Current/Experienced Behavior: You can't rename assets in bulk. Improved/Expected Behavior: Authors able to move and rename assets in bulk. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.7 + Customer-name/Organization name: Hershey's Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: There should be a permission for user administrator or webmasters to unlock pages that have been locked by an Author.  Use-case: A client is on AMS. In this environment, an author locks a page, but goes on holiday or leaves for the weekend or is sick. The page remains locked and the client has to contact Adobe to unlock that page. It would be easier if a client-side user administrator or webmaster can unlock those pages as well.  Current/Experienced Behavior: Client needs to contact Adobe to unlock a page. Improved/Expected Behavior: Client can unlock a page himself, through an assigned user-administrator or webmaster...  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: National Lottery Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: As per current implementation experience fragments render server side. So every time we make a change in experience fragment we need to publish all the pages or include it in Sling Dynamic Include. Can we give a check box in experience fragment dialog where we can select whether we want to render our experience fragment client side or not Use-case: every time we make a change in experience fragment we need to publish all the pages or include it in Sling Dynamic Include Current/Experienced Behavior: current implementation experience fragments render server side Improved/Expected Behavior: Can we give a check box in experience fragment dialog where we can select whether we want to render our experience fragment client side or not Environment Details (AEM version/service pack, any other specifics if applicable): All AEM on premise and cloud versions Customer-name/Organization name: Adobe Screenshot (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ability to choose multiple options in defining rules with an "OR" logic Use-case: To be able to create "Requirement" and "Visibility" rules that would allow multiple options, with an OR logic so that we don't need to create the same field for the same rule just for the other option Current/Experienced Behavior: When setting rules, and referencing a dropdown field, we could only choose one option or multiple options but only with an AND logic.    Improved/Expected Behavior: When setting rules, and referencing a dropdown field, we should be able to choose one option or multiple options with an AND and OR logic. For example we are referencing a dropdown with 1,2,3 as its dropdown values. We would want to be able to choose 1 and 3 (with an OR logic) as the options for the "requirement" and "visibility" rules to take place.   This would mean that if a user chooses option 1 OR option 3, the field referencing this dropd

Request for Feature Enhancement (RFE) Summary: Ability to control "Requirement" and "Visibility" field settings for dropdowns linked to a JSON Use-case: To be able to reference a dropdown that uses a JSON for another field's "Requirement" and "Visibility" field settings Current/Experienced Behavior: We cannot control or use the "Requirement" and "Visibility" field settings, when referencing to a dropdown that uses a JSON for its options  Improved/Expected Behavior: Able to choose a dropdown field in the "Requirement" and "Visibility" field settings that uses a JSON 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: Fix overlapping elements in metadata schema editor Use-case: To have a better user experience in using the metadata schema editor Current/Experienced Behavior: Currently, there are some overlapping elements in the metadata schema editor. Some of these examples are using the "Multi-line text" field and adding multiple options for dropdowns. See screenshots below.  Improved/Expected Behavior: No overlapping elements or no UI errors 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: New  Contexthub Segments placed at conf location with 6.4 repository restructuring don't have copy-paste options Use-case: Content Authors who are extensively using context hub segments for personalization rely heavily on copy-pasting segments and tweaking some changes in the existing one  Current/Experienced Behavior: No copy paste option in new segment location. it was present though in 6.3 with the classic option under miscadmin Improved/Expected Behavior: Copy-paste option would definitely improve time to market for content authors who cater personalization Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.11 Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):