Adobe Experience Manager Sites

Request for Feature Enhancement (RFE) Summary: Remove "Download" button for Viewer Presets Use-case: Based on the current behaviour of AEM as a cloud service, when users open the assets and select Viewers section, a download button is available so the users try to download the viewer but an error message is shown. Current/Experienced Behavior: "Download" button is available for the feature Viewer Preset but it 's not possible to download them because no content is there. Improved/Expected Behavior: "Download" button should be disabled/hidden after selecting viewer presets to avoid confusion in the users. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.10.18175.20241010T124406Z-240900 Customer-name/Organization name: Jet2 Screenshot (if applicable):     Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enhance the view settings for the list view so that you can select the alias (sling:alias property) next to the options which are available currently. Use-case: If you want to localize the URL's of your web pages, the way to go is to keep the name of the page in English and use the alias value for the translation. E.g. if you have a page about history, you would create a page with name history in AEM and set the alias of this page to geschichte (which is the German translation). So at the end you will get .../geschichte.html as external URL.   Current/Experienced Behavior: The alias value is hidden in the page properties of the page. So, from all views which are available in Sites console, you don't see this important value at one glance. If you have an external localized URL and want to figure out which page in AEM is behind, you need to open page properties of the pages in the folder in question. This is not really efficien

Request for Feature Enhancement (RFE) Summary: Introduce a search box to find completed workitems by model under Workflow Archive  Use-case: Currently workflow archive tab lists ALL completed workitems. We have a Post-processing auto-assign workflow which fires 5000+ times everyday. Making really difficult to find specific other workitems completed daily. We couldn't sort/filter by model or find interested workitems of specific model. Current/Experienced Behavior: Workflow archive tab only lists ALL completed workitems. No ability to sort/filter/find specific workitems Improved/Expected Behavior: Introduce a sort button on Model column to sort by models. Introduce a "Search by Model" searchbox that ll filter the workitems based of selected model. The search box can be typeahead that prompts models which user can click.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/O

Request for Feature Enhancement (RFE) Summary: Hi, I'm writing this because we would like to have the name of the initiator of the Workflow instead of the "workflow-process-service" name in the "Published by" field. Any ideas if we can do that? Or is it a new Feature Request? Thanks Fabio Use-case: When publishing pages with the rollout options, it displays "workflow-process-service" in the "Published by" field. Current/Experienced Behavior:  When publishing pages with the rollout options, it displays "workflow-process-service" in the "Published by" field. Improved/Expected Behavior: Instead of the "workflow-process-service" name, we would like to have the name of the initiator of the workflow in the "Published by" field. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.6.16799.20240614T073455Z Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: We propose a User Activity Dashboard within Adobe Experience Manager (AEM) to track recent user interactions, enabling administrators to view active users and their activity within the AEM Author environment. This feature would display user interactions over defined time intervals (e.g., 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day), providing insights into both current and historical usage trends. Use-case: Outage Communication: During system outages or maintenance windows, administrators can quickly identify and proactively inform active users of the disruption. This can reduce the number of support tickets, emails, or inquiries related to unexpected access issues. Performance Monitoring: By understanding the volume of requests by user or group, teams can better anticipate peak usage times and address potential performance issues. This data could help identify when system resources are under strain due to high

Request for Feature Enhancement (RFE) Summary: Front-end pipeline (FEP) configuration can only be set at root level of the site in content hierarchy. Also, the sling:configs can be added directly under /conf and not a node beneath. Use-case: We have grouped our sites and are looking for separate front end pipelines per site.  e.g. /content/group1/site1, /content/group1/site2, /content/group2/site1, /content/group2/site2 Similarly for sling:configs: /conf/group1/site1, /conf/group1/site2, /conf/group2/site1, /conf/group2/site2 Current/Experienced Behavior: Front-end pipeline (FEP) configuration can only be set at root level of the site. i.e /content/group1 - FEP1 or /content/group2 - FEP2 Similarly for sling:configs: /conf/group1, /conf/group2 Improved/Expected Behavior: Front-end pipeline (FEP) configuration can be set at multiple levels within the content tree. i.e /content/group1/site1 - FEP1, /content/group1/site2

Request for Feature Enhancement (RFE) Summary: The AEM RTE Table plugin currently generates tables without <thead> and <tfoot> tags, which can negatively impact accessibility and SEO. Use-case: We are enhancing our site's Accessibility and also need to integrate third-party libraries that support sorting and filtering but we found <thead> and <tfoot> tags in table (generated through rte plugin) are missing . Current/Experienced Behavior: Table generated through AEM RTE Plugin doesn't have options to add tags like <thead> and <tfoot> Improved/Expected Behavior: By incorporating <thead> and <tfoot>, the AEM RTE Table plugin can significantly improve its accessibility and SEO, providing a more inclusive and effective experience for users and search engines. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 Customer-name/Organization name:   Screenshot (if applicable): NA

Request for Feature Enhancement (RFE) Summary: Extend the Cloud Manager events to include Audit related events Use-case: I want to be able to monitor changes to environment variables, domains, ip whitelisting etc... Current/Experienced Behavior: There is no audit trail of changes by users Improved/Expected Behavior: Events are to provide the user, change area, previous value, new value and time of change Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Customer-name/Organization name: Spark New Zealand Screenshot (if applicable): Not applicable, not currently provided Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Implement a mechanism to ensure that user accounts are created simultaneously on all pods. This will eliminate delays in availability and ensure consistent user data across the system. Use-case:   Current/Experienced Behavior: Its take up to 200 to 500 ms in syncing pod Improved/Expected Behavior: User get created in all pods simultaneously Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Munich Re Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Proposal to Establish Integration Between AEM DAM and AEC Assets Use-case: Establishing a seamless connection between Adobe Experience Manager (AEM) Digital Asset Management (DAM) assets and Adobe Experience Cloud (AEC) assets to enhance user workflow and efficiency. Current/Experienced Behavior: Currently, there is no direct integration between AEM DAM assets and AEC assets, requiring users to manually transfer assets between the two platforms, leading to inefficiencies and potential errors in asset management. Improved/Expected Behavior: Proposing an integration solution that enables users to seamlessly sync and access assets between AEM DAM and AEC, facilitating unified asset management, enhanced collaboration, and improved content personalization capabilities. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Dam /cloud Aseet and AEC Cloud Customer-name/Organization name: TO THE NEW

Request for Feature Enhancement (RFE) Summary: Provide the ability to specify the flags for RegExp in content fragment models for custom validation regex.   This can be a mulit-select combobox offering the following flags:   global insensitive multiline single line (dotall) unicode sticky (screenshot attached, add combobox under custom regex with these options, that would simplify the regex and enable new possibilities) Use-case: We have 2500+ clients that we serve using multi-tenancy. We are using content fragments and headless to deliver that content. We have contractual obligations with a major client that requires us to provide a completely white-labelled experience, from logos to copy. This means that there can be no mention of my company name anywhere in the content. Violations carry a $5M fine. Current/Experienced Behavior: Today, it is not possible to specify these flags, so handling things such as case sensitivity is unmanageable, and matching patterns

Request for Feature Enhancement (RFE) Summary: Format the HTML removing return carriages and white spaces Use-case: Minimize page loading and file system cache disk usage Current/Experienced Behavior: The page loading is affected and more disk space is needed for the cache. Improved/Expected Behavior: Less disk size is needed and pages are faster Environment Details (AEM version/service pack, any other specifics if applicable): ALL the AEM, premise and cloud Customer-name/Organization name: This page is AEM based: view-source:https://www.miles-and-more.com/row/en.html   This is NOT AEM based: view-source:https://www.iberia.com/   do your math... Screenshot (if applicable):   Code package (if applicable):  

  Request for Feature Enhancement (RFE) Summary: Ability to Search for CQ Tags from the Tagging Console Use-case: 1. From the AEM Start page, navigate: Tools > Tagging.2. Attempt to search for a existing cq tag (using the title or description) Current/Experienced Behavior: The search results do not include (the expected) cq tags. Improved/Expected Behavior: The search functionality should return tags that match the provided keywords in the tag title or tag description. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.19 Customer-name/Organization name: Verizon Screenshot (if applicable):   Code package (if applicable):  

In the Environment Configuration area (https://experience.adobe.com/#/@nos/cloud-manager/environments.html/program/XXXX/environment/XXXXX -> Configuration), i't will be nice if we could complement the table with a description field and allow this field to be filterable, this would allow those who have several sites to filter the variables by site (for example).It would also be nice if you could sort the fields alphabetically.

Request for Feature Enhancement (RFE) Summary: Enhance AssetCompute microservice to accept altText Use-case: Today AssetCompute microservice, helps to upload asset. If the asset has associated `altText` or additional metadata, the code has to wait until processing complete event. And then update `altText` and metadata. If the microservice itself supports updating additional metadata to asset, can help saving second trip to update.  Current/Experienced Behavior: No ability to update asset metadata during create Improved/Expected Behavior: API supports ability to update (limited) metadata during create itself.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Automating the Creation and Edition of Front-End Pipelines via: 1) API https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#tag/Pipelines and/or 2) aio cli https://github.com/adobe/aio-cli-plugin-cloudmanager Use-case: As DevOps we want to automate the creation and edition of front-end pipelines within Adobe Cloud Manager. This involves setting up a process where pipelines are instantiated without manual intervention whenever new code is ready to be deployed. Without this feature we can't fully automate onboarding new sites and it generates unnecessary costs of manual work. Current/Experienced Behavior: Methods are now available only in CM private backend API (https://cm.adobe.io/). Improved/Expected Behavior: Methods to create and edit front-end pipelines available in public API ( https://cloudmanager.adobe.io) Environment Details (AEM version/service pack, any other specifics if a

Request for Feature Enhancement (RFE) Summary: Adding a warning about the impact of making changes to the "Edit Product Profile" feature Use-case: Changing the Product Profile name to a more user-friendly in the "Edit product profile" feature Current/Experienced Behavior: Changing the Product Profile name to a more user-friendly name impacted the permissions in each environment. Since the group did not exist, certain features became unavailable to users. This issue has been escalated in Case - E-001332537. Improved/Expected Behavior: Add a warning that changing the Product Profile name may impact the actual environment permissions. Alternatively, consider implementing a more robust solution, such as blocking the option to change the profile name and using the display name field (if filled in) to show the name in product/profile listings. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization

Request for Feature Enhancement (RFE) Summary: Adobe provides New Relic One access for observability but does not use it for customer alerting or internal operational alerting. Request is to support setting up these alerts to get notified of any potential downtime or issue with the AEM PODs.  Use-case: Adobe provides New Relic One access for observability but does not use it for customer alerting or internal operational alerting. Request is to support setting up these alerts to get notified of any potential downtime or issue with the AEM PODs.  Current/Experienced Behavior: Adobe provides New Relic One access for observability but does not use it for customer alerting or internal operational alerting. Improved/Expected Behavior: Adobe should provide New Relic One access for customer alerting or internal operational alerting. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Latest release Customer-name/Or

Request for Feature Enhancement (RFE) Summary: Based on the current behaviour of AEM as a cloud service, when someone tries to download assets with licences you get a page that requires you to agree or disagree downloading the asset. This page is: /dam/gui/content/assets/licensecheck.external.html. So, when you click "agree" and then the "download" button, you get the download pop up. If, though, you press cancel to the pop up, the download button of the asset is disabled and you need to switch the options to make it available again. Use-case: Based on the current behaviour of AEM as a cloud service, when someone tries to download assets with licences you get a page that requires you to agree or disagree downloading the asset. This page is: /dam/gui/content/assets/licensecheck.external.html. So, when you click "agree" and then the "download" button, you get the download pop up. If, though, you press cancel to the pop up, the download button of the asset is disabled and you need to

Request for Feature Enhancement (RFE) Summary: Create a new Java library that does same functions of aio-lib-state like AdobeState.get(), .put(), etc Use-case: This is a suggestion after my previous posts on allowing AssetCompute microservice to accept altText and another problem. Will be nice if AEMaaCS can have a fast state persistence layer (not JCR). aio-lib-state works well leveraging cosmos. Extend its abilities to java world as well. Current/Experienced Behavior: No library similar to aio-lib-state for java. Cant share data between aio-runtime-action and AEM java Improved/Expected Behavior: Extend aio-lib-state to support java SDK.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Confirmation of successful installation in AEM Forms Add-on Use-case: When installing for example AEM Forms 6.5.<version> Add-on for Windows, it would be nice to get a message in the error.log at info level when the installation is done, just as you have in the service pack. Current/Experienced Behavior: There is no message when installation is done, so you have to just wait for the loggs to stay still for a while Improved/Expected Behavior: The developer will see a message of done installation so we will know when the instalattion is done. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Forms 6.5.<version> Add-on for Windows Customer-name/Organization name: Kristian Franzén/Arbetsförmedlingen Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: In AEMaaCS can push AEM, Dispatcher, and CDN logs to Splunk, but not the Deployment logs. Use-case: As an Architect/Developer, I would like to receive alerts when new warnings/errors appear in my releases/deployments. The only way to perform proper log analysis and set up alerting in AEMaaCS is through Splunk. Current/Experienced Behavior: The only way to analyze Deployment logs in AEMaaCS is by manually downloading them from Cloud Manager. Improved/Expected Behavior: By pushing the Deployment logs to Splunks, Adobe would enable clients to set up custom queries, reports, dashboards, and alerts to monitor their releases. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.9.17964.20240924T170544Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ability to re-organize tabs in the metadata schema editor Use-case: When we want to change the order of the tabs in the metadata schema editor, we will need to delete and create the whole tab page Current/Experienced Behavior: AEM metadata schema editor does not allow to re-arrange the header tabs. This is a pain point especially if there are already a lot of changes done in the metadata schema, and we just want to re-arrange the tabs.  Improved/Expected Behavior: Ability to drag and drop the header tabs to easily arrange them in the order that we want.  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: Translation of content like custom XF on Editable Template Use-case: We have a custom XF within an editable template. However, when creating a language copy for a page using that template, its XF content (or any other template content) is not translated. This necessitates either manually translating and authoring the XF content or developing a custom script for the translation process. of XF. Current/Experienced Behavior: Currently when we translate a page in aem in another language its template content doesn't get translated a the reference to the template Is not given by default. Improved/Expected Behavior: if any user is translating a page content in other language its template  content should also be replicated. Environment Details (AEM version/service pack, any other specifics if applicable): version:  All versions Customer-name/Organization name:   Screenshot (if applicable):   Code pack

機能改善要求（RFE）概要： In the current UI, the sidebar cannot be expanded horizontally, preventing the full display of query names. I would like to have the ability to see the full list of query names, perhaps by allowing the sidebar to be expanded horizontally. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM Release: 2024.7.17098.20240711T134106Z スクリーンショット（ある場合）