Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: When you upload native XD files in AEM Assets, auto-generate a preview image like other file types: ,jpg, .png etc. Use-case: Upload .xd file, auto-generate a preview image for .xd files Current/Experienced Behavior: Generic preview icon for .XD files (see attached) Improved/Expected Behavior: preview image based on contents of XD file Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets 6.5.x Customer-name/Organization name: Walgreens Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently, if you go and select an asset in the "Quick action" toolbar, you will see the option to smart crop and edit the asset no matter what role and permissions the user has.  Causing a poor experience and confusion for the end-user because the user cannot save the changes after using it. Use-case:   Current/Experienced Behavior: ‘Quick actions’ is visible for users that don't have permission to use that was causing performance issues Improved/Expected Behavior: To have an enhancement and OOTB solution from Adobe to help end users use the "Quick action" toolbar with the actions that they can perform based on the roles and permissions Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Manager service pack 2023.2.0 Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently, if you go to the metadata schema for assets, you can leave the field blank when you use the tag field, as this is not required. If you need that the user completes all the information in the metadata, including the tags, it wouldn't have the option to force the user to fill in the value Use-case:   Current/Experienced Behavior: Tag namespace required validation that does not exist today. So the user can leave this field blank. Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud   service pack 2023.2.0 Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Listener to automatically download files on AEM Assets.  Use-case: Easily download assets without having to to click on download inbox each time Current/Experienced Behavior: Currently users needs to click on download inbox each time to download files. After clicking on download button, user expects the files to be immediately downloaded. Instead user receives a message to check the download inbox each time a ZIP is created.  Improved/Expected Behavior: Listerner that automatically downloads files after zip it has been succesfully created.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service - Assets Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Download folder without all hierarchy folders Use-case: folder download in AEM assets Current/Experienced Behavior: all hierarchy folder is reconstructed when we download a folder Improved/Expected Behavior: if we have a long hierarchy, in download process, hierarchy is not needed. We loose time to rich the assets after download Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloudservice Customer-name/Organization name: Louis Vuitton Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: As an end user, when I use the download component on a page, then I should be able to see the file size of the document up to 1 decimal point(at least) or a configurable number of decimal points. Use-case: Display exact size of the document to the end user. Current/Experienced Behavior: The file size is rounded to the nearest GB(or KB, MB) Improved/Expected Behavior: The file size should display correct value up to at least 1 decimal. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2021.12.6145.20211216T083234Z. WCM Core Components - 2.17.12 Customer-name/Organization name: Abbott Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Related Case #E-000858459 Use-case: Customer has customized the renditions of an asset to exclude some of the OOTB renditions but when the same asset was used in the "Share Link" option and checked "Allow download of renditions of file" checkbox   In the Share Link downloads all the renditions including the OOTB renditions like 48x48 or 139x139 are visible and there is no way to customize the list of renditions on that screen. Current/Experienced Behavior: All the renditions are displayed on Share Link downloads including the OOTB ones. Improved/Expected Behavior: There should be a customization of what is being displayed on "Share Link" download renditions 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: Currently when users have to select assets or folders, they need to hover over for the small tick on the left-corner of a folder (in card view).  Use-case: The current approach is not user-friendly and time-consuming. For examples, editors have to select 50 assets out of 800 within a folder. Usually the editors use 'card view' which ensures a thumbnail preview of the assets. Editors then have to select each asset by clicking on top-right corner of each one.  Current/Experienced Behavior: Currently when users have to select assets or folders, they need to hover over for a small tick on the left-corner of a folder (in card view).  Improved/Expected Behavior: More user-friendly way of quickly selecting assets or folders. A big hover-over enabling the selection of assets or folders. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a cloud service Customer-name/Organi

Request for Feature Enhancement (RFE) Summary: Search should support fuzzy search Use-case: Portal User is searching for specific pages on portal Current/Experienced Behavior: Search Index just returns exact matches Improved/Expected Behavior: Search Index returns fuzzy search matches as well Environment Details (AEM version/service pack, any other specifics if applicable): 2023.3.11382.20230315T073850Z Customer-name/Organization name: Telefonica Germany B2B Screenshot (if applicable):     Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: We want to have a redirect tool that's built-in with AEM. Not ACS or opensourcee code Use-case: Currently, the only way to have a redirect tool in AEM is to install the ACS commons redirect manager Current/Experienced Behavior: None. There is no built-in redirect tool within AEM. ACS is the only way Improved/Expected Behavior: - Bulk upload and delete- Search- Export of lists- Suggest unnecessary redirects (chain redirects) - AI capability - Suggest how redirects can be consolidated (like suggesting the use of regular expressions for multiple rules that are similar)- Capacity for 500,000 rules Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Would like to add the following feature: Block some known Bot Requests by IP in CDN in AEMaaCS. Ignoring URL Parameters at CDN is currently not possible. Use-case: We are getting a lot of Bot Requests in our Dispatcher and Publish Logs. Ideally we would like to block these requests at CDN itself. These requests are coming from multiple IP and are impacting the performance of the application.Request Types - 1. /Solar_Image.php?mode=resize&fname=test%22%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E2./$%7b@java.lang.Runtime@getRuntime().exec(%22nslookup%20cec9ut6t9v7cv1g00010h8moeyzz4cmdk.oast.live%22)%7d/3. /pacs/login.php?message=%3Cimg%20src=%22%22%20onerror=%22alert(1);%22%3E1%3C/img%3EThere should be a way to block the IP or perform the action at WAF layer to block these bots. Current/Experienced Behavior: The requests are blocked at Dispatcher currently but the logs are choked with these requests. Improved/Exp

Request for Feature Enhancement (RFE) Summary: Prevent the browser caching of (potentially) sensitive data (e.g. some personal data of the logged-in user) Use-case: AEMaCS Author sets the Cache-Control header with a directive that does not prevent the caching of sensitive data in the user’s browser. An attacker gaining access to the browser of a user with which sensitive information has been retrieved can get insights into the data by reading the cache. Current/Experienced Behavior: The application does not prevent the caching of (potentially) sensitive data. In the responses, the value of the Cache-Control header is set to ”no-cache”, as can be seen in the following screen- shot (please check the attached report.) The “no-cache” instruction only ensures that the browser validates that the content is up-to-date on the server before using the cache. A look into the browser cache shows that sensitive data (e.g. some personal data of the logged-in user) is stored there. Improve

Request for Feature Enhancement (RFE) Summary: When we search any asset on author / Filter the assets, post doing that when we select single/multiple assets, can't see create option and hence unable to trigger the workflow for assets. Can we enable create option so business able to trigger the workflow. Use-case: 1. Business go to author 2. Search the assets / Apply filter and search the assets. 3. Select list of assets post searching. 4. Business looking for the option to trigger the workflow. (to run on single/multiple assets) Current/Experienced Behavior: Create option not visible. (So workflow option unable to use) Improved/Expected Behavior: If we can enable the create option, business can trigger workflow on searched/filtered assets. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.5 ( Also checked in 6.5.7 same behaviour) Customer-name/Organization name: Hershey's Screenshot (if applicable):    Code package (if appli

Request for Feature Enhancement (RFE) Summary: Enable cropping of WebP images in AEM Assets. Use-case: Enable cropping of WebP images in AEM Assets. Current/Experienced Behavior: Cropping of WebP images is currently not supported in AEM. When trying to Edit / crop it shows the following message:  "Editing is not supported for this type of assets." Improved/Expected Behavior: Cropping of WebP is possible. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service. Customer-name/Organization name: Hugo Boss AG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Would like the following feature - Cache Hit Ratio to be refined as a factor for Optimization in BPO Reports Use-case: We received a BPO Report highlighting Cache Hit Ratio of 80% against Adobe's recommendation of 90%.The implementation is AEMaaCS thus using Adobe's Fastly CDN. The metric is also calculated at CDN end. However, a large number of requests which are received at Dispatcher are not cache able. (Health Check based requests like /system/probes/health, /system/probes/live, /system/probes/ready and Bot Based Requests like GET /3x.php/?3x=3x which are blocked at Dispatcher) Current/Experienced Behavior: The metric calculated at CDN would take into account both bot based requests which are blocked at Dispatcher (but not CDN!) and Health Check based requests which are not cached and served to Publish instances via Dispatcher. Improved/Expected Behavior: The metric should exclude these service based requests (if not alre

Request for Feature Enhancement (RFE) Summary: Would like to add the following feature: Extend support for videos and content fragments to be part of Connected Assets. Use-case: We would like to establish a remote DAM instance as single source of truth across all environments. The DAM instance will store not only images and documents but videos & content fragments as well. Current/Experienced Behavior: Videos & Content Fragments are not part of Connected Assets. Improved/Expected Behavior: Videos & Content Fragments should be accessible from Remote DAM Instance. Environment Details (AEM version/service pack, any other specifics if applicable): AMS - AEM 6.5.11 Customer-name/Organization name: TA Digital Screenshot (if applicable):   Code package (if applicable):   @kautuk_sahni - This might not be a new feature request but would like to know the challenges involved in implementing this idea if it is categorized as non-feasible.

Request for Feature Enhancement (RFE) Summary: Related case #E-000849947 Use-case: Customer leverages AEM Assets & Screens on cloud service and AEM Sites on Managed service. They use Connected Assets to sync images from Assets CS to AEM Sites Managed service for use in component creation via drag & drop.   Currently, they see all images that they have permission to on Assets cloud service. Including images that are not published to Dynamic media / scene7.    More details can be found on #E-000849947 Current/Experienced Behavior: There is no way to filter these images with status Published / Unpublished. As a result they see too many images on the connected assets rail. Improved/Expected Behavior: Filtering for published & unpublished assets is necessary to be able to work efficiently on connected asset rail. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screen

Request for Feature Enhancement (RFE) Summary: configuration of columns orders in list views Use-case: in the view settings or directly in the table results, be able to change column order as prefered Current/Experienced Behavior: in the settings we can only sort by some of metadata  Improved/Expected Behavior: the expected behavior is to be able to order as we want the different columns Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloudservice Customer-name/Organization name: Louis Vuitton Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When deploying to Production from the stage pipeline, if the user clicks Resume manually or Approve that a popup dialog would appear to request the user to confirm the deployment to Production.  Use-case: If the user accidentally clicks on Resume manually or accidently clicks Approve Current/Experienced Behavior: The pipeline will deploy to Production without giving the user the option to cancel Improved/Expected Behavior: Provide a popup dialog box giving the user the option to cancel or proceed. Environment Details (AEM version/service pack, any other specifics if applicable): Your application code has been tested for quality and compiled into build artifacts REPOSITORY: OLDDOMINIONFREIGHTLINEINCProgram-p18552 BRANCH: release/WSP.2023.3 GIT TAG: 2023.303.1154227.0002373591 COMMIT: a97608cd708a9d72cfe36cfad945d55ff217fd9e   Your built artifacts will be combined with the base AEM 2023.1.10912.20230130T173736

Request for Feature Enhancement (RFE) Summary:   Use-case: Currently we have several projects / brands that are deployed on AEM, in the case of small fixes we are obliged to deploy all the projects /brands even if the fix concerns only one project / brand or a small module , which is very impactful in terms of deployment time if we consider that we deploy several times a day.   We hope to have a way to deploy by project / brand instead of a global deployment, or even better a deployment of modules, sub-projects, or a selection of specific files, which will optimize the deployment time that we currently has (15 to 20 minutes on average). Current/Experienced Behavior: Deployment average 15 to 20 min Improved/Expected Behavior: Deployment average 10 min (depending of the files deployed) Environment Details (AEM version/service pack, any other specifics if applicable): Dev, QA, UAT, Stage, PROD Customer-name/Organization name: Accor Screenshot (if applicable): &

Request for Feature Enhancement (RFE) Summary: Make `npm audit` a warning by changing it to audit-level="info" or remove it from the pipeline to prevent it blocking production builds Use-case: Npm audit should be used as an informative tool, not as a gateway test for building to production. The reason this is important is because most audit errors are caused by the build toolchain, and does NOT have an impact on the final application. Furthermore, remediation of npm audit is not always possible, meaning you'd be permanently blocked.   For more info, see this article: https://overreacted.io/npm-audit-broken-by-design/   Current/Experienced Behavior: npm audit returns exit code 1, blocking the pipeline from continuing. Improved/Expected Behavior: npm audit returns exit code 0 using audit-level="info", or remove it from the pipeline commands. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:

Request for Feature Enhancement (RFE) Summary: Support for Amazon Linux 2022(Linux kernel5.x). Use-case: Use as the OS for new servers. Since Amazon Linux2 is reaching EOL, I want to use a new standard OS. Current/Experienced Behavior: AEM 6.5 supports kernels up to 4.x. https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en#server-operating-systems Improved/Expected Behavior: AEM 6.5 supports kernel 5.x including Amazon Linux 2022. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Adobe's own Payment gateway for seamless integartion with applications via simple API calls. Use-case: Payments in any payment related applications. Current/Experienced Behavior: 3rd party integartion, white label payment gateway Improved/Expected Behavior: Use of APIs provided by Adobe to directly connect to payment gateways and get response seemslessly without redirecting to 3rd party pages within AEM. Create own payment experience. Additional add-on to AEM. 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: A couple of AEM versions ago, the ability to sort the assets in column and card view were introduced to Assets. In Sites, this is not yet possible. This is not only inconsistent, but also inconvenient. It would be great if the same sorting feature could be added to Sites in the main Sites navigation, in the tagging section and in the pathbrowser. Use-case: We have some page areas with many subpabes which cannot be structured in a sensible way.The authors usually want to edit the last created or last updated pages. This means in column and card view one must scroll down several pages or switching to the list view where sorting is possible. Both is not satisfying, especially the context switch between the several views, and would be solved by introducing the sort feature from Assets. We have the same issue in the tagging area and the pathbrowser when selecting another page (or asset / tag). Except there the workaroudn to switch list vi

Request for Feature Enhancement (RFE) Summary: We noticed recently the new warning message added to AEM bulk edit scenario, where user attempt to “Select all” and edit these sub-pages in separate tabs. The warning message says that “Bulk action not supported, The selected action Edit(e) will only have effect X selected items currently loaded…”. As we understand, the justification for that warning message is to let user know that not all sub pages might have been lazy-loaded, and that’s fine. That also explains why the massage doesn’t need to appear when pages have been selected manually. The point is that the mentioned logic might be confusing when there are only few sub-pages to be selected by “select all”. In that case lazy logic is not the case and user can be sure that “select all” picks all the sub pages we have on the screen. Please consider extending that logic, because our customers feels uncomfortable with new behavior and confusing warning. (More detail you can find in thr