Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: In 6.5.7 sorting feature is added which by default sort based on created and in ascending order.  Use-case: We would like the facility to change default setting, instead of default sorting by created, we would like to sort it via Name. Current/Experienced Behavior: If we go to any card/list/column view it will sort by created. Improved/Expected Behavior: Some kind of setting to change default sorting, so when we go to any view card/list/column it will sort based on that new default setting i.e. by name. 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:   Use-case: Local user lockdown for 6 Password try fails for 30 minutes Current/Experienced Behavior: No such OOBT feature  Improved/Expected Behavior: Local user lockdown for 6 Password try fails for 30 minutes Environment Details (AEM version/service pack, any other specifics if applicable): All AEM/AMS instances Customer-name/Organization name: Canadiantire Corp Screenshot (if applicable):   Code package (if applicable):  

機能強化リクエスト（RFE）のサマリー： customize the page displayed when AEM service outage occured. ユースケース：   現在／過去のビヘイビアー： nothing(default page will be displayed) 改善済み／予想されるビヘイビアー: customers can customize the page for their users. 環境の詳細（AEM バージョン／サービスパック、該当する場合はその他の詳細）： AEM as Cloud Service 顧客名／組織名：   スクリーンショット（該当する場合）：   コードパッケージ（該当する場合）：  

Request for Feature Enhancement (RFE) Summary: The AEM superuser 'admin' account can perform certain functions within AEM. It cannot be delegated to a group such as 'Administrators'. As you mentioned, perhaps this would be addressed by the internal enhancement to extend this access to the groups configured in Apache Sling Web Console Security Provider.   Use-case: e.g. keystore/truststore functions Current/Experienced Behavior: only the 'admin' user provides some functions in AEM. Improved/Expected Behavior: Allow 'admin' functions to be delegated/managed by other users. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5, SP2 Customer-name/Organization name: USAA Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary:   Use-case:   Current/Experienced Behavior:   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):  

Prerequisites Node 8.9.0 - https://nodejs.org/dist/latest-v8.x/ Java 1.8 - https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html Maven 3.5.2 - https://archive.apache.org/dist/maven/maven-3/3.5.2/binaries/ AEM 6.4 with Service pack 2    Use the below cmd to create your project-      mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=24 -D aemVersion=6.5.0 -D appTitle="My React SPA Site" -D appId="mysitereact" -D groupId="com.demomysite.react" -D frontendModule=react -D includeExamples=y -D includeDispatcherConfig=n Open terminal and navigate to react-app directory and execute “npm install --save-dev webpack webpack-cli” to install Webpack webpack.config.js file need to be created and paste the following code snippet---- const path = require("path"); module.exports = {  entry: "./src",  output: {    filename: "App.js

Request for Feature Enhancement (RFE) Summary: Horizontal breadcrumb navigation option instead of the drop down version that is the current functionality. Use-case: As a global DAM user, I want a horizontal breadcrumb trail on top of the dropdown navigation in Assets > Files like the horizontal breadcrumb in AEM > Navigation so that I can easily see where I am in the navigation. Current/Experienced Behavior:   Improved/Expected Behavior: Situated in the middle of the rail, and always showing the description of the currently selected item, the breadcrumbs display a drop-down listing the levels of the hierarchy of the currently selected item. Click on an entry to jump to that location. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: By having the ability to make fields in inbox notifications non-editable, it will make the notification more secure and can act more as a reference for details and assignments. Use-case: As a user, I want the ability to make fields in the inbox notification to be non-editable so that users won't be able to change the details of the notification. Current/Experienced Behavior: Currently, all fields in the inbox notifications can be edited by multiple users and this can potentially lead to confusion for users. Users can change the content path, assignee, description, priority, etc.  Improved/Expected Behavior: Ability to make the fields in the inbox notification to be non-editable for more security and dependability. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applica

Request for Feature Enhancement (RFE) Summary: Add dir attribute dropdown feature in page properties dialog Use-case: To enable RTL support for arabic sites. Current/Experienced Behavior: Currently there is no dir attribute in HTML element, and also we have written a sling model to dynamically choose the dir attribute based on the url/language choosen. Improved/Expected Behavior: Need to have a dropdown for dir attributes below the language dropdown in 'Advanced' tab of page properties. Also dir="rtl" should automatically be added if we translate our contents (machine translation) from any other language to arabic. Environment Details (AEM version/service pack, any other specifics if applicable): AEM aaCS Customer-name/Organization name: Born Group commerce private ltd. Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: While some assets may satisfy the search requirements of a Smart Collection, they may not be wanted by the user that created the Smart Collection. Use-case: As a user, I want to be able to exclude certain assets from a Smart Collection. Current/Experienced Behavior: Users must make manual Collections or allow unwanted assets in Smart Collections. Improved/Expected Behavior: The option to exclude specific assets from a Smart Collection. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Users would like to 1-click to their saved Collections. Use-case: As an AEM user, I only want to easily see MY Collections And Smart Collections. Current/Experienced Behavior: Manual/visual search of Collections. Improved/Expected Behavior: 1-click filter for self created Collections. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable page versioning from page editor UI Use-case: A content author is making changes to a page and would like to create a version with its current state before proceeding with editing Current/Experienced Behavior: One should go to Sites navigation UI, switch the left toolbar to Timeline, create the version and return to the editor Improved/Expected Behavior: It is possible to create the version without leaving the editor. I see two ways how it could look: 1) there is a new "Create version" item in the "Page information dropdown"; 2) in "Page information" dropdown, when you select "Start workflow", there is an out-of-the box "Create page" workflow model you can pick. Please see pictures for both options attached. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP8 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Option 1: Option 2: Code package (

Request for Feature Enhancement (RFE) Summary: Online compaction not that effective and observed repository growth and which is causing slowness in author. Adobe suggesting to run offline compaction. This offline compaction is very unpredictable process, not sure how long it might take. This idea request is to know if there is any way we estimate how much time it will take before we start offline compaction? Use-case: Looking for feasibility of developing something which calculate estimate time offline compaction will take. Current/Experienced Behavior: No way to calculate how long that process take. Improved/Expected Behavior: If this is possible, we can give clear timeline to business about downtime that needed to run offline compaction and it's very very helpful. 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: Have seperation of duties in the roles so that production pipeline execution can be limited to Program or Business owner roles.  Use-case: As per https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/requirements/role-based-permissions.html?lang=en , anyone in the roles Business owner, Program Manager or Deployment Manager can start / approve the production pipeline execution in Cloud Manager. It would be a very beneficial control to have settings limiting production approval to business or program roles as this will allow a more stricter approval workflow to help regulate production pipelines . A deployment manager role that manages all the day to day environment deployments that doesn’t have to go through a business approval makes sense for lower environments. But for production it would be great if this was limited to a Business owner or Program manager.  Current/Experienced Behav

Request for Feature Enhancement (RFE) Summary: Would like an interface to the Adobe Experience Fragment Export via IMS (enhancement to the export/serve/status of Fragment Export) Use-case: Many orgs have limited bandwidth to troubleshoot the destination of Experience Fragments as they are exported to Target (i.e. workspace destination). Development development team updates the experience fragment incorrectly or a bad config gets installed via the build or is misconfigured via IMS in some way, it would be useful to see the ultimate destination (and potentially where the XF is embedded by Target if possible) within some kind of reporting interface.  Current/Experienced Behavior: No visibility into Experience Fragment destination our serving after export Improved/Expected Behavior: Some level of visibility into Experience Fragment "Journey" Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 Customer-name/Organization name: Large Medica

Request for Feature Enhancement (RFE) Summary: Asset Picker should not interrupt user typing Use-case: Searching assets by typing search terms in Asset Picker Current/Experienced Behavior: Asset Picker trims tailing space while user is typing. It is very difficult to type in more than one word in the search input box Improved/Expected Behavior: User typing is not interrupted. Tailing space could be removed when user hits enter key, clicks the search icon, or the input box loses focus.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP7 Customer-name/Organization name: Loblaw Inc, Ltd. Screenshot (if applicable):   Code package (if applicable):  

Currently, there is no option in AEM collection details UI to add individual assets from one collection to another collection. However,  It does have have a feature add entire asset collection to another collection, but not individual assets inside that collection. It would be beneficial to user to combining assets from one multiple collections and perform actions on those assets Thanks,Vineeth 

Most of the documentation is hot garbage, and since Adobe takes AEM and makes it the one true source for information, Can we improve the documentation? Almost all of the walkthroughs are rarely show coding through the steps or just skip over it and copy and paste. My mentor always said if the documentation is garbage then the product probably is too....

Currently, editor for the Content Fragments, Metadata Schemas and Folder Metadata Schemas does not have a documented way to add custom components into the editor. This is incredibly restrictive when you want to do things which can be done in standard AEM Dialogs such as:Drive Dropdowns off a list of valuesCreate Multi / Multi-Composite FieldsCustomize Field behaviorIf there was a documented way to extend / customize the fields, this would allow implementors to better meet their business needs.

Request for Feature Enhancement (RFE) Summary: When using property predicates in the search rail, it shouldn't matter what listOrder they are assigned and that listOrder shouldn't change how the query. Currently, some listOrders make the query search on every property and other listOrders correctly searches for the term on the property it points to. Obviously the location of the search facet in the search rail should not change the query. For example, a listOrder of 35 gives this query: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(jcr:content/metadata/@nord.row.item.brand, 'nike'))] and searches for "nike" in the jcr:content/metadata/nord.row.item.brand metadata field. However, change the listOrder of the search facet to 36 and the query changes to: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(., 'nike'))]  and search on ALL metadata fields for "nike." This is obviously a bug, but the support team told me to open an enhancemen

Request for Feature Enhancement (RFE) Summary: The rich text editor clears content out if pasting content in while a table is present in the RTE. Use-case: Improve user experience when building Adaptive Forms Current/Experienced Behavior: Steps to reproduce: 1. Create adaptive form.2. Add "Text" component.3. Click the pencil icon to change the bar to the edit bar.4. Click the maximize icon to access the full wysiwyg editor.5. Add a table with some data.6. Paste some information into any part of the component. The result I get is the table is removed. However, by clicking the undo button, the table appears again with the pasted content. It is almost like something extra is running after the paste that triggers the removal of the table and the editor sees that as another step that was taken by the user. Improved/Expected Behavior: Pasting content should not remove existing content Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.9

機能強化リクエスト（RFE）のサマリー： Get logs more than one week from Cloud Manager ユースケース： When we receive Alert notification from Customer, We can retrace its past and survey it. 現在／過去のビヘイビアー： Within one week 改善済み／予想されるビヘイビアー: more than one week (for as long a time as possible) 環境の詳細（AEM バージョン／サービスパック、該当する場合はその他の詳細）： AEM as a Cloud Service 顧客名／組織名：   スクリーンショット（該当する場合）：   コードパッケージ（該当する場合）：  

Request for Feature Enhancement (RFE) Summary: As a general user, I'd like to be able to set a tagging profile to assets with common tags/consistent tag list rather than adding tags to each individual asset Use-case: User is adding a number of different assets to the same project or folder  Current/Experienced Behavior: User has to apply each tag manually Improved/Expected Behavior: A set of tags can be saved and recalled so that all of the tags will be applied at once rather than applying them individually.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Mark Edelstein/Accenture Screenshot (if applicable):   Code package (if applicable):  

  Request for Feature Enhancement (RFE) Summary: Enable DRM feature on DAM Shared links Use-case: Sales and engineers have access to assets only from Brand Portal: they share licensed assets, or not licensed assets with external users without any issue (exernal users have to access licenses when downloading licensed assets) Brand manager and marketing people are working daily in the DAM. They prepare the assets, manage their publishing to the Brand Portal They aslo share assets with external users like journalists, vendors or other potential assets consumers These external users do not have access to BP nor DAM cause their need is very limited in time (once or twice a year maybe) Brand Manager are working all day long in the DAM and they never or almost never go onto the Brand Portal (they might not even have an account) They use the Share link feature with these external users to provide them assets collections, assets and/or folders directly

Request for Feature Enhancement (RFE) Summary: Upgrade the Tags (Taxonomy) component with OOTB features that should of been addressed in 6.5. The 6.5 experience greatly reduced my ability to work efficiently. It removed functionality available in Classic UI rather than improve upon the Classic UI functionality and features. Pay attention to the Tags as much as you do to DAM, AI/ML. See current experience for details. Use-case: Taxonomy tag manager Current/Experienced Behavior: Degraded experience for tag management and findability in 6.5 OOTB features. Tag functionality was ignored in 6.5. The Touch UI experience is clunky, requires multiple clicks to do anything, unable to search for tags unless applying page properties. The Touch UI experience removed the ability to view tags in a tree or list, unable to easily scan the list of references applied to a tag, unable to sort, view tag status (published, deactivated, unpublished) modified by whom and when.  I work 90% of my ti