Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: As of now AEM author session is getting logout either user is active /inactive.is it possible to add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work  Use-case: it is useful for author to get notified to save their work. Current/Experienced Behavior: As of now AEM author session is getting logout either user is active /inactive. Improved/Expected Behavior: To add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work  Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 cloud Customer-name/Organization name: Shell Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently asset management is interlocked with site management, i.e. moving assets in the asset module requires republishing of pages in the sites module instead of just updating the asset references in the affected pages, especially on Publish. Use-case: We have dedicated asset and site managers. When an asset manager moves an asset the site manager is required to republish the page(s) with this asset to update its references on the page. This can become a hassle when page(s) with the asset are being reworked. These pages are not ready to be republished. Due to this dependency asset and site managers cannot work independently. Current/Experienced Behavior: When assets are being moved, affected pages need to republished Improved/Expected Behavior: When assets are being moved, asset links on affected pages should be updated without the need to republish the page Environment Details (AEM version/service pack, any other specifics

Request for Feature Enhancement (RFE) Summary: Enhance the publish/unpublish process on blueprint pages with a warning if the rollout configuration "Activation on Blueprint activation" or "Deactivation on Blueprint deactivation" is in place. Use-case: To efficiently manage large website the ootb rollout configs "Activation on Blueprint activation" and "Deactivation on Blueprint deactivation" are available, see: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/msm-sync If you have set this up for e.g. on livecopy root page there is no indicator available which shows the editor, maintaining the blueprint page, that with publish a blueprint page or unpublish this action takes also place on the livecopy. So, it could happen that accidentally a livecopy page goes on or offline. Current/Experienced Behavior: No hint for the editor once he publishes or unpublishes a blueprint page that on the connected livecopy page the sa

Request for Feature Enhancement (RFE) Summary: Our system currently sends out automated emails to an uploader when an asset they uploaded expires. Would like to have the ability to this email to go out to more than just the uploader? Use-case: A team to have the ability to see when an asset has expired instead of one person. Current/Experienced Behavior: Our system currently sends out automated emails to an uploader when an asset they uploaded expires Improved/Expected Behavior:  A group of AEM members to have the ability to see when an asset has expired instead of one person. 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: Move/Copy of Context-Aware Configurations when a page is moved/copied Use-case: Pages with special CAC's (like header, footer ...) are moved/copied and all the CAC's have to be manually set again in the destination tree. Current/Experienced Behavior: When a page with specific Context-Aware Configs (set below it) is moved or copied then all the CAC's (below /conf) remain in the same place so the editors have to redo the configurations every time. Improved/Expected Behavior: It would be easier that when page (or complete tree) is copied or moved that also it's related CAC's (/conf) are also copied/moved. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.4.16145.20240430T082417Z Customer-name/Organization name: Pictet/One Inside Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently for deploying code to RDE, developers have to use aio rde plugin and don't have a provision for configuring a pipeline to directly deploy through a branch. Also, huge packages of content need to be moved either through aio or via package manager. User should have a provision of deploying code through quick pipelines which are meant for simply deployment and should also have a provision for quick content movement from DEV/Stage/PROD environments to RDE. Use-case: Quick deployments to RDE Current/Experienced Behavior: time consuming process for making a RDE in complete working state Improved/Expected Behavior: Quick deployments to RDE Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: GSPANN Technologies Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Update the data type of the Tags field within the GraphQL schema from String to Tag Use-case: Fetch the Tag Title using GraphQL query for AEM Headless Current/Experienced Behavior: _tag: [String], tagPropertyName: [String] Improved/Expected Behavior: _tag: [Tag], tagPropertyName: [Tag] Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.x & AEMaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Page Move rollout config should not only adjust links in referencing pages but also should re-publish them if editor does not decides against Use-case: For managing multinational and multilanguage websites with AEM, we use MSM with blueprint/livecopy to maintain it in a efficient way. Also, as we want to have also structure every time in sync, we are using Page Move Rollout configuration to ensure that also page moves are applied in the livecopies through the rollout. See chapter "To fully realize a page move ..." here: https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/administering/introduction/msm-best-practices.html?lang=en#structure-changes-and-rollouts Current/Experienced Behavior: Let me give you a most simple example: Imagine you have two pages, page A and page B. Page B has a link to page A. Both pages are rollout out to a livecopy and are published. Livecopy has page move and standard rollout co

Request for Feature Enhancement (RFE) Summary: Ability to synchronize CF updates to multiple Live copies from CF Edit UI Use-case: MSM for Content Fragments Current/Experienced Behavior: To synchronize changes to a live copies, we need to synchronize them one-by-one from References panel Improved/Expected Behavior: Ability to synchronize CF updates to multiple Live copies from CF Edit UI Environment Details (AEM version/service pack, any other specifics if applicable): AEM July 2023 Cloud release Customer-name/Organization name: Abbott Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: We create a new page under /content/soucedcode/language-masters/en called home . Within this page, we will drag in an Experience Fragment Component with the XFPath. In this scenario, we have XFPath = /content/soucedcode/experience-fragments/language-masters/en/button/masterWhen we language or live copy pages, the XFPaths should be updated as expected, but it is not. Now let's continue with the scenario.   Please note that we have the entire structure of the XF created - /content/soucedcode/experience-fragments/language-masters/en/button/master - /content/soucedcode/experience-fragments/language-masters/fr/button/master- /content/soucedcode/experience-fragments/language-masters/es/button/master - /content/soucedcode/experience-fragments/ca/en/button/master - /content/soucedcode/experience-fragments/ca/fr/button/master- /content/soucedcode/experience-fragments/us/es/button/masterNow after when the new page is created in la

Request for Feature Enhancement (RFE) Summary: Experience Fragments' variations are subjects of Manage Publication flow Use-case: Apply Manage publication feature (as it works now for sites) to Experience fragments variations, so Author users are able: to see button Manage Publication on panel   to use first step of Manage Publication with Options:   Publish/Unpublish, Now/ Later (with specifying date) to use second step of Manage Publiction with Scope: Add content button on panel that opens EF folder   Include children (that adds EF variations in case EF chosen) Include language copies (that adds language copies of EF variation) Remove selection Published references      Current/Experienced Behavior: Manual selection of Experience Fragments variations Manage Publication is overlay applied to sites Improved/Expected Behavior: Manage Publication is OOB feature available to Experience Fragments' variations Environment Details (AE

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): AEM SDK v2023.1.10912 Customer-name/Organization name:   Scree

  Request for Feature Enhancement (RFE) Summary: This request is about the Content Transfer Tool, which can be improved for insufficient disk cases. Use-case: AMS instance with the S3 Data Store has been prepared for the very first initial extraction. Extraction started with about 400GB asset content. After about 1 hour, it failed. The logs forwarded to the Adobe Support.   They noticed the following statement on top of the output.log, see attached zip file :   Check Size results: Migration Set size: 381.247 GB Node store size: 2.202 GB Data store size: 379.045 GB Node count: 20,764,479 Free disk space (crx-quickstart dir): 24.398 GB You do not have enough disk space in the crx-quickstart subdirectory of the source AEM instance to perform this extraction. You need to increase disk space by 51.486 GB or reduce the migration set size. Current/Experienced Behavior: CTT tried to run all extraction steps, until a failure occurred for the obvious root cause. Impr

Request for Feature Enhancement (RFE) Summary: Currently the Tags Console (/ui#/aem/libs/cq/tagging/gui/content/tags.html) just provides column view. User can not handle large amounts of tags efficiently. To get information about publication status you have to select each tag - there is no way to get it at one glance for all. An option to switch to a list view would help here. Also, sorting option would be automatically be available. Use-case: As a user I want to have a quick overview about my large number of tags in terms of publication status without checking each item. Also, I want to sort by name to find a certain quicker. Current/Experienced Behavior: Today, with only column view being available, no overview is provided. You need to invest a lot of time to get the information you need. Improved/Expected Behavior: Provide a list view for tagging console similar to the one in Sites console. Also, keep an eye on old CUI which supported the editor much better here providing a

Request for Feature Enhancement (RFE) Summary: Request to have a feature to purge AEM cloud OOTB CDN cache using cloud manager. Use-case: Currently, we use CURL to clear cache using the x-aem-purge-key provided by Adobe for each environment. Can we have an interface in cloud manager to purge the OOTB CDN cache of URL's/ entire domain for each environment in AEM cloud. Current/Experienced Behavior: Using CURL to purge the cache Improved/Expected Behavior: To have this feature in Cloud Manager Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: If an editor decides to have a sorting by a column and he clicks on a column header therefore, this setting should be kept until be changes it. Use-case: As an editor I often have the need to sort the item by e.g. last modified date to find currently updated pages much faster. Current/Experienced Behavior: Currently if you click on a column header in order to sort by this one and afterwards open a page properties of a page and cancel or save&close, this one the set up order in the list view is gone. This is annoying for editors. Improved/Expected Behavior: If editor decides to have a sorting by a specific column this should be kept until he changes this. Please compare to CUI - here it was the case and it was for a good reason! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if appli

Request for Feature Enhancement (RFE) Summary: We are using multi tenancy. In the cloud configuration can't able to see any child tenants if we are not configuration any cloud configurations in the root folder. Use-case: We are using multi tenancy. In the cloud configuration can't able to see any child tenants if we are not configuration any cloud configurations in the root folder.   Current/Experienced Behavior: In the cloud configuration can't able to see any child tenants if we are not configuration any cloud configurations in the root folder. Improved/Expected Behavior: In cloud configuration need to able to see all child tenants if we are not configuration any cloud configurations in the root folder. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Allianz Screenshot (if applicable): Attached Code package (if applicable):  

  Request for Feature Enhancement (RFE) Summary: Please provide an ootb feature to create reports for Sites within AEM. Currently there are Asset Reports (Tools > Assets > Reports) available in AEM which provides some very helpful ootb reports which can be generated by the user. The same I would really like to have for Sites as editors often have the request to provide information about their websites, especially about the web pages and their status (unpublished, published). Basically the Publish Report that is available for Assets would be perfect. Use-case: As an editor I need to provide an overview to my stakeholder about my websites. They want to know how many pages they contain of and if they are published/unpublished. Similar to Publish report that is available under Tools > Assets > Reports Current/Experienced Behavior: Unfortunately no ootb AEM feature available which can be used. Improved/Expected Behavior: Provide a Publish report for Sites (under To

Request for Feature Enhancement (RFE) Summary: We've created several smart crops that are applied to an image on upload. For a specific image these smart crops can then be changed and saved - for that image only.   Use-case: If we then create an additional new smart crop to be applied to all images on upload from then on, we run Dam Update Asset or Dynamic Media:Reprocess assets to update existing images so they too have this new smart crop. Current/Experienced Behavior: However, we've found that after running either of these w/flows - any changes that were made to a specific image (as described above) are lost. Any images run thru the w/flows get the new crop - but lose any specific changes that may have been made to the existing crops. Improved/Expected Behavior: Changes to smart crops for specific images should NOT be overwritten if the image is re-processed.   Or at least the option to save/overwrite should be given Environment Details (AEM version/ser

Request for Feature Enhancement (RFE) Summary: Enable Preview for referenced content in AEM as Cloud Service Use-case: Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and there is no option to Push to Preview for Assets, Tags, etc. Current/Experienced Behavior: Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and author has to use Add content option to include Referenced assets, tags, etc. The only option to do this in Bulk is to use a Workflow but that does not allow author to selectively distribute content. Improved/Expected Behavior: Page and all referenced content associated with the page should automatically get pushed to Preview or at least author should get an option to select the references and decide whether to push those. Environment Details (AEM version/service pack, an

Request for Feature Enhancement (RFE) Summary: Please enhance the information which is displayed if you hover on the publish date with exact time of publishing Use-case: As editor I maintain a lot of pages per day. And, I also publish them. The UI provides me just the date of publication, even on hover it shows me not the time when publication took place - it just provides the weekday which is pretty useless at all. For investigation reason it is a lot of effort to mark the page and check timeline in left rail to get the information about the publishing time. Current/Experienced Behavior: Currently if you hover on the publish date just the weekday is displayed in addition to date. Improved/Expected Behavior: On hover the exact time should be displayed as well like it was the case in Classic UI. This should be an easy task! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (i

Request for Feature Enhancement (RFE) Summary: Enhance External Link Checker page Use-case: As en editor I want know about broken external on my website which I'm responsible for and want to fix the links efficiently. Current/Experienced Behavior: Under /etc/linkchecker.html you get a list which but you can not export it to a csv. Imaging you have a lot of editors working on AEM instance each responsible for different subtrees reflecting different business groups. Now it is hard to figure out the error for specific paths in order to fix this. It is even harder if error occurs not just on a single page but in blueprint page and the connected livecopy pages (imagine 20 livecopies) - here the column get's flooded (just very long comma separated list) and hard to retrieve the information out of that.   Link to documentation: https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/administering/operations/external-link-checker.html?lang=en#external-link-ch

Request for Feature Enhancement (RFE) Summary: Our system has some DAM folders with more than 1000 PDFs in a single folder.  We are encountering an index error when using the default Assets interface. Use-case: This should occur in an AEM system with no custom code, provided that some DAM folders have huge numbers of assets in them. The user opens Assets and traverses the system using various views. Some folders may fail to open in certain views. Current/Experienced Behavior: This appears in the log: *WARN* [10.240.32.86 [1693910873433] GET /mnt/overlay/granite/ui/content/tree.0.html/content/dam/document-library/corporate-pensions HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where ischildnode(a, '/content/dam/document-library/corporate-pensions') order by [jcr:created] desc /* xpath: /jcr:root/content/dam/document-library/corporate-pensions/*

s Request for Feature Enhancement (RFE) Summary:  in pipeline process choices, enhance a choice to Stop/Terminate after stage installation the pipeline beside current choices of "Ask every timeFail ImmediatelyContinue Immediately" Use-case:   Current/Experienced Behavior: only these three options of Ask every timeFail ImmediatelyContinue Immediately Improved/Expected Behavior: add option of Stop/Terminate after stage installation  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Pipelines | Cloud Manager (adobe.com) Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: I would like you to modify it so that hyphens are not automatically converted to underscores. Use-case: When creating a folder in XF, I entered a hyphen in the title (required) and saved it, but the name (optional) was automatically converted to an underscore. Current/Experienced Behavior: When creating XF settings, hyphens entered in the title are automatically converted to underscores. Improved/Expected Behavior: When creating XF settings, Hyphens entered in the title are not automatically converted to underscores. Environment Details (AEM version/service pack, any other specifics if applicable): 2024/3/8version Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):