Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: Update Timewarp functionality to work with nested launches and with launches utilizing experience fragments.  Use-case: Successfully utilize Timewarp functionality within all AEM  launches, to avoid capturing manual screenshots of all scheduled updates to have on record. This will allow us to compare our home page to older versions of itself in order to compare metrics, trends, and any other data needed to help us improve our business.  Current/Experienced Behavior: Timewarp does not work as desired for Nested Launches or when experience fragments are used. The experience fragment is not loading when the page is viewed in Timewrap or the Version UI for Preview or Compare versions. The experience fragment does load appropriately if it was part of the initial template.    Our process for home page launches today involves creating nested launches off each Sunday's home page. The breaking the inheri

  Request for Feature Enhancement (RFE) Summary: As a DAM Asset Report user, when I try to create a "Download" asset report, I should be able to see a default "Downloaded by" option in the default column. Use-case: User should be able to generate a report of the assets in a given path, associated with the users list who have downloaded those assets, in a column Current/Experienced Behavior: There is no option to know about the users who have downloaded the assets in author environment. However, the feature is present in Brand portal Improved/Expected Behavior: "Downloaded by" column should be available while creating "Asset Report" of "Download" type Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.4 with planned upgrade to 6.5.7 by installing the service pack Customer-name/Organization name: Oxford Properties Screenshot (if applicable):     Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Interface to understand and  manage permissions Use-case: It became very tough for the users to understand or manage the permissions in AEMasCS and was at least easy with legacy UI admin in AMS. Specially when it comes to fixing the access issues for authors and other business groups it's taking too much of time to go over the rules. Current/Experienced Behavior: Difficult to manage permissions. Improved/Expected Behavior: Easy to manage permissions. Environment Details (AEM version/service pack, any other specifics if applicable): AEMasCS Customer-name/Organization name: Bread financial Screenshot (if applicable): NA Code package (if applicable): NA

Request for Feature Enhancement (RFE) Summary: The click on the logo in the upper left corner should always lead to AEM start page. Use-case: If I'm into Assets (via Assets > Files) in order to maintain an asset and want to go quickly go to start page afterwards, I click on the logo link in the upper left corner to do so. Current/Experienced Behavior: If you are in /ui#/aem/assets.html/content/dam (via Assets > Files) and click on the logo you end up one level above and not on start page. Improved/Expected Behavior: If you enter AEM (/ui#/aem/aem/start.html), click Personalization > Audiences and the click on the logo you end up on start page. Same I would expect when I click on start page Assets > Files and click on the logo. This different behavior confuses the editors and I see no reason why it should behave differently. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG

Request for Feature Enhancement (RFE) Summary: I suggest to have a PNG option for the FPO setting slider to enable a seamless working with assets that do rely on transparency. Use-case: FPO Renditions for InDesign Asset Link are OOTB only available as JPGs.This file format does not meet the needs of modern print media production workflows, since images rely more heavily on transparency settings instead of cutting paths. This change is not very new and i have seen companies made that switch from cutting paths to transparency back in 2010. This makes JPG a suboptimal choice for FPO renditions since this format is not capable of containing transparent pixels. The picture would be flattened on a white background. Current/Experienced Behavior: FPO is simply not an option on every asset that has a transparent background. This goes for pretty much every single product picture within our AEM.Since the setting is applied via Folder setting, we have to manualy delete the FPO renditions on

Request for Feature Enhancement (RFE) Summary: Currently when applying filters, filters should be selected individually (filter select -> result loads -> and another select another filter and so on). This takes a lot of effort and time lag.  Use-case: Place apply all button to select all filters at once Current/Experienced Behavior: Filters applied individually Improved/Expected Behavior: Apply all button to select all filters Environment Details (AEM version/service pack, any other specifics if applicable): AEM Asset CS Customer-name/Organization name: LG Electronics Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The OOTB Services and Servlet responses does not take care of link mapping for outbound URLs. As result of which , components such as Search Suggest and Search Results , Sling Model Exporters still contain long URLs . There should be some Link Rewriter Transformers or sling filters written for such cases to pass through these URLs via ResourceResolver.map(String resourcePath) .  Use-case: SEO Improvements - Hide /content/project-name from Search results Current/Experienced Behavior: The URLs returned contain long URLS like /content/project-name/ Improved/Expected Behavior: The URLs should be rewritten using some transformer or link rewriter or Sling Filter before returning response back  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS  Customer-name/Organization name: ODFL / Publicis Sapient Screenshot (if applicable):   Code package (if applicable): Th

Request for Feature Enhancement (RFE) Summary: When moving an asset/folder via the Move action, we want this page to sort the folders alphabetically, instead of by creation date. The creation date sort is confusing to users as many do not know when a folder was created, making the desired folders difficult to find in the list. Use-case: Users should have the ability to sort while using the Move functionality Current/Experienced Behavior: Users can move asset but no feature to sort folders alphabetically it is last modified Improved/Expected Behavior: Users have ability to sort folders alphabetically  Environment Details (AEM version/service pack, any other specifics if applicable): AEMAACS Customer-name/Organization name: Epsilon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Either enable copying the path to an asset within the AssetLink file details page or jump straight to the asset in AEM by clicking the path. Use-case: This feature would unlock all the information stored with the asset right from Asset Link.  Current/Experienced Behavior: path can neither be highlighted and copied nor clicked Improved/Expected Behavior: as described above 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):  

機能改善要求（RFE）概要： Improve Replication Queue not to block other queues when "Blocked Replication Queue" occurs ユースケース： When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone.With this limitation, we'are facing a critical challenge in our operation such as;- when a block occurs on weekends or at midnight, there is no one who can remove the blocked queue, so any pages and/or assets cannot be published until next business day.- when a block occurs on a Brand A's site, that also blocks other replication queues for Brand B.   Can you please change the behavior? such as skip the error queue instead of blocking all queues after an error occurs? 現在／体験した動作： When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone.Notification is sent from Action Center, so that someone in administrator c

Request for Feature Enhancement (RFE) Summary: Please increase the upper limit of the number of workflows that can be executed simultaneously Use-case: There are cases where many workflows (No. 1, No. 2) occur simultaneously. 1.Publishing process Approval flows may occur simultaneously to publish multiple products at the same time on the same date and time. 2.Back processing Cyclic processing for linking with other systems (once/5 minutes) Approval flow in production work (movement, deletion approval)   As a result, there is an issue of delays in publishing products with specified dates and times Current/Experienced Behavior: Insufficient increase in the number of workflows that can be executed simultaneously Improved/Expected Behavior: Increase the number of workflows that can be executed simultaneously. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.5.16461.20240524T172309Z Customer-name/Organization nam

Request for Feature Enhancement (RFE) Summary: Introduce a one-click configuration that syncs AEM DAM with Dynamic Media for asset deactivation and deletions Use-case: Today when an asset is unpublished from AEM, author has to manually unpublish from DM also using Tools --> Assets --> CDN Invalidation. Second, if asset is deleted from AEM, it NEVER automatically deletes from DM. Second asset in same name appends -1 numerals in DM urls. This forces developers to write custom implementations to maintain sync between AEM and DM.  Current/Experienced Behavior: Asset unpublished / deleted from AEM does NOT unpublish / delete corresponding assets from DM. This causes flux, unsync between AEM and DM Improved/Expected Behavior: Create a DM configuration that can sync AEM with DM. So unpublish/delete from AEM should automatically perform same actions from DM as well. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely a

Request for Feature Enhancement (RFE) Summary: Introduce a one-click configuration that syncs AEM DAM with Dynamic Media for accepted formats.  Use-case: Today we have a AEM DAM delivery folder that is synced with DM. This DAM folder accepts ALL AEM compatible formats. But they fail to upload into DM, since DM allows only restricted formats. We found after certain assets failed in production. Now adding extra implementation to reject  DM incompatible formats in AEM. Current/Experienced Behavior: AEM accepts more asset formats than Dynamic media. This causes AEM assets succeed at AEM, but fail at Dynamic media.   Improved/Expected Behavior: Introduce a one-click config, when enabled, AEM should also reject DM incompatible asset. Reduces maintenance overhead.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (

Request for Feature Enhancement (RFE) Summary: Extend the "Explain Query" tool to capture graphql queries and suggest optimizations over gql queries  Use-case: We are running multiple graphql queries on AEMaaCS and works in Production. Periodically some queries run longer time and sometimes heavy queries crashes the server. Current/Experienced Behavior: No tool to analyze and suggest optimizations for GraphQL queries.  Improved/Expected Behavior: Build a tool similar to "Explain Query" for JCR queries that can suggest optimizations for graphql queries. Provide insights on execution time and cost for traverse and reference. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Custom Metadata Schemas and fields developed in AEMaaCS should be visible in Assets Essential console as well. Use-case: Currently we are not able to see any of the custom buttons or menu along with the metadata schemas designed in AEM in the Assets Essential console. Current/Experienced Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console are not visible in the Assets Essential console. Improved/Expected Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console should be visible in the Assets Essential console. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Credera (Formerly TA Digital) Screenshot (if applicable): N.A Code package (if applicable): N.A Original Query Link - AEM Assets Essentials (Experience Manager Assets) vs Experience Manager - Custom UI Handling

Request for Feature Enhancement (RFE) Summary: Locked pages should prevent other users from editing the content; however, it should allow the content to get copied because the content can still be viewed. A locked page should Only restrict other users from editing the page. Use-case: We have Toolkit area which guides our Authors on how each component works. Additionally, we provide many samples to help authors come up with ideas for building new pages. All of those pages — which we refer to as Toolkits. As we have locked all these pages to protect from any unauthorized changes, it also prevent our Authors to copy those samples or examples. Therefore, it will be good if locked pages only prohibit users from ed

Request for Feature Enhancement (RFE) Summary: Heap Utilization Warnings and graphs on Reporting console should match the heap memory usage on servers Use-case: The Cloud Manager Portal - Reports displays a System Monitoring stat for all the environments and servers in terms of Host, Network, Storage and Application. Sometimes it displays in warning "Heap size is 85% of the allocated memory"If you check the server in question, mostly the figures don't align - For instance in the publish server for which the warning was flashed the usage was around 35-40% which is way off the warning limits.Ideally there should be a strong co-relation between these 2 figures. Current/Experienced Behavior: The overall heap memory usage in /system/console/memoryusage does not align with the Reporting console in Cloud Manager. Improved/Expected Behavior: The overall heap memory usage in /system/console/memoryusage should align with the Reporting console in Cloud Manager. Environment De

Request for Feature Enhancement (RFE) Summary: This RFE proposes integrating AI capabilities into AEM to assist content creators with curation and content suggestion functionalities. Use-case: Content creators often spend significant time searching for relevant assets and information to build compelling content pieces. This can be particularly challenging when managing large content repositories. Current/Experienced Behavior: Content creators rely on manual searches and browsing through folders and tags to locate relevant assets. This process can be time-consuming and inefficient, especially for complex content structures. Improved/Expected Behavior: Integrate AI-powered content suggestion features within the AEM authoring environment. As a content creator drafts their content, the AI suggests relevant assets (images, text snippets, related articles) based on the current context. The AI considers factors like keywords, themes, content type, and past user behavior to deli

Request for Feature Enhancement (RFE) Summary: Request to add "find location of asset" feature in search results in Brand Portal which is already present in AEM DAM. Use-case: 1. We login to Brand Portal 2. We do a search for lets say "Truck" keyword in search bar. 3. Lets say, 25 assets show up in the search results. 4. Now, we want to navigate/go to the location/folder of any of one of these 25 assets. 5. Need an option to go to the location/folder of the asset. Current/Experienced Behavior: Currently we can only see the path of the asset like /content/dam/ Improved/Expected Behavior: The user can directly go to the location of asset. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a cloud service 2024.4.15860.20240410T113939Z-240300 Customer-name/Organization name: NA Screenshot (if applicable): Need the same option in Brand Portal as AEM DAM reference as shown below:         &nb

Request for Feature Enhancement (RFE) Summary: Request to improve behaviour for View in Admin button during page editing. Use-case: When user clicks “View in Admin” he or she expects that the same page will be opened in sites admin. Usually pages have many children, so it takes time to find edited page again. Current/Experienced Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin”   Opened parent page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience Improved/Expected Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin”   Opened edited page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten Environment Details

Request for Feature Enhancement (RFE) Summary: Instead of free form field when adding a content fragment variation, provide authors a pre-populated list of variation titles to choose from. Use-case: Content Fragment Variation titles are often used across an application. Current/Experienced Behavior: Author must type in correct variation title Improved/Expected Behavior: Allow developers to provide a list of variations for authors to choose from Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Customer-name/Organization name: UHG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enhancing Search Feature of Connected Assets with Path based search to Remote Assets in AEM 6.5 Use-case: Authors uses Assets finder in Media Library by using search features such as Keyword,Path,Tags etc. Whereas in Connected Assets 6.5 we just have search by Keyword|Tags but its not supporting Path based search which is a big degradation in author experience when they switch to use connected assets from AEM Assets Current/Experienced Behavior: AEM Author when using Connected Asset to fetch an Asset from Remote Asset unable to search Asset bu Path similar to Asset finder in media library Improved/Expected Behavior: Include Search feature similar to Asset Finder of Media Library Which is path based search in AEM 6.5.I hope this feature is available in CaaS. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP17 Customer-name/Organization name:   Screenshot (if applicable): &nbsp

Request for Feature Enhancement (RFE) Summary: This is an outcome of support case - E-001180834. The support team determined that when the content copy tool is run for AMS linked cloud manager the tool fails if there were any modifications in the copy source Use-case: The tool is used frequently to downstage the content from prod back to the lower environments. It is not practical to pause all activities in the environments to perform the stage down Current/Experienced Behavior: Content copy tool breaks in cases if the server content is updated Improved/Expected Behavior: Content copy should run independent of system usage Environment Details (AEM version/service pack, any other specifics if applicable): AMS - AEM 6.5.16 Customer-name/Organization name: Philip morris international Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enhancing the IP Allow Lists functionality in Adobe Program Overview for Experience Manager Use-case: Providing users with IP Whitelist access to specific domains Current/Experienced Behavior: Recommendation 1 -  Improve how environments are applied for an IP Allow List Name. Currently, you have to go into the specific environments and add the IP for all relevant segments (author, publish, preview).     Recommendation 2 -  When adding an IP Allow List Name to the dispatcher/publish environment, there is no warning that this will stop all other users from viewing this environment. This can sometimes be an easy mistake with a significant impact.   Improved/Expected Behavior: Recommendation 1 -  Improve how environments applied are adding for a IP Allow List Name. Allow admins to add/remove environments in IP Allow List view provided below.     Recommendation 2 -  Add an alert for this

Request for Feature Enhancement (RFE) Summary: Cloud Manager - Table view - Order table data by column Use-case: Example:"Cloud Manager" -> "Services" -> "Domain Settings".We have round about 100 Domains configured in "Domain Settings".The Domains are listed in a table view with pagination function at the bottom.The latest Domain entry is alway on top of the table.We would like to have a function to order the table data by each column (Domain Name; DNS Record; SSL Certificate attached; Environment applied) Current/Experienced Behavior: You can't change the order of the data in any table view within cloud manager to get a better overview Improved/Expected Behavior: You can order table columns in all cloud manager views Same feature would be helpful on all other table views within cloud manager to be able to order table data Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: B. Braun SE Scre