Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary:   Use-case: Editors need the possibility of moving folders and removing in case of making a mistake. Current/Experienced Behavior: Folders in the new Content Fragment Editor can be created. They cannot be moved, copied, cut or deleted. Improved/Expected Behavior: Folders can be moved, cut, copied and deleted by editors.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Assa Abloy Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： Regarding the replication process when a page is locked and a deletion process is executed ユースケース： If the deletion process is executed while the page is locked, the replication process (private) is not executed, and the page is deleted in the Author environment, while the page remains published in the Publish environment.From the user's point of view, the deletion process is considered private, so it appears as if the process has ended normally, and errors caused by locks cannot be detected.   Can you please improve the behavior so that the deletion process on Author cannot also be executed when locked? 現在／体験した動作： An event occurred in which a page was not actually private, even though we thought we had deleted the page and made it private.Upon investigation, it was determined from the log that this was due to the fact that the page was locked. 改善／期待される動作： The deletion process on Author cannot be executed while locked. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細

Request for Feature Enhancement (RFE) Summary: This ticket addresses issues with the AEM asset timeline and revision tracking not displaying all changes, focusing on understanding limitations and potential solutions. Use-case:   Karen Barton (AWC Librarian) reported that asset overwrites by Jeff Hess were not shown in the timeline, causing tracking frustration. Sainikhil Reddy (Bounteous Dev) explained AEM timeline shows workflow/publication events but not all low-level edits without custom versioning or audit listeners. Sarah Scalia (Bounteous) noted implementing such custom workflows in AEM as a Cloud Service is complex, estimated as a 15-point effort. The asset metadata like "Modified" and "Modified By" is visible in column and list views but not in card or insight views. Current consensus is that timeline limitations are due to AEM core behavior; custom solutions would require significant development effort. Current/Experienced Behavior: timeline does not show all l

Request for Feature Enhancement (RFE) Summary: Users should not be able to download the assets from Brand Portal, if they have reached expirationDate. Use-case: To maintain consistency and compliance. Current/Experienced Behavior: Currently its not blocked in brand portal Improved/Expected Behavior: Non admins should not be able to download assets from brand portal, if it has reached expiration date. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Signify Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable Full PDF Preview in Brand Portal "Link Share" Mode Use-case: Brand and Creative teams frequently share CI guidelines and marketing documents with external agencies, vendors, and regional partners using Brand portal share link. Current/Experienced Behavior: Manually resending files or explain partial previews which in results in: * Slower collaboration and review cycles * Suboptimal brand experience for external stakeholders * Inconsistent experience between internal and external user Improved/Expected Behavior: Providing a complete in-browser preview of multi-page PDFs is critical for: * Ensuring brand consistency without needing to download files * Reducing redundant back-and-forth communication * Avoiding re-sharing or clarifying partially visible content * Maintaining a seamless, professional experience for partners Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets

Request for Feature Enhancement (RFE) Summary: Multiple domain support for Manage Publication Preview Use-case: My customer APG would like to be able to preview the website in AEM that contains links to multiple domains. The Publication Preview functionality is not following the externalizer configuration to be used properly (screenshot of externalizer domains used below).     Current/Experienced Behavior: It is possible to set multiple domains in the externalizer configuration, but only 1 domain is respected in the Publication Preview functionality, resulting in errors in the links when previewing the website (see 'part 2' screenshot below).     The impact of multiple domains not being support in the Publication Preview functionality is that it is impossible for APG to properly preview their websites and use this feature properly to identify potential issues. Improved/Expected Behavior: An out of the box solution to support multiple domains for links

Request for Feature Enhancement (RFE) Summary: Cloud Manager Deployment: Enabling Rollback from Previous Build Snapshots Use-case: The customer is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much

Request for Feature Enhancement (RFE) Summary: Publish all content fragment live copies in one go Use-case: Currently we are able to rollout a fragment 300+ Live copies but to publish the same fragment we have to go to all 300+ live copies and manually publish which makes impossible to do.  Current/Experienced Behavior: Currently we are able to rollout a fragment 300+ Live copies but to publish the same fragment we have to go to all 300+ live copies and manually publish which makes impossible to do.  Improved/Expected Behavior: An option to publish content fragment similar to rollout. Environment Details (AEM version/service pack, any other specifics if applicable): AEMasCSAdobe Experience Manager 2024.9.17689.20240905T073330Z-240900 Customer-name/Organization name: Bread financial Screenshot (if applicable): NA Code package (if applicable): NA

Request for Feature Enhancement (RFE) Summary: Enhance AEM Desktop to detect new files from local cache and bulk upload new files within a downloaded folder Use-case: When creative users work on product creation. It is usually at a folder level, where they have multiple files within a folder. This complete folder would be treated as a single entity.The users work on multiple files within the folder, also creating new files. Users generally use save as feature on their creative Apps (  Applications for creating assets) to save/export to a particular format. The desktop app currently tracks only the existing files which are synced from AEM cloud to desktop. The newly added files even though are available on same hierarchy on their local cache is not displayed within the desktop App and the users have to manually drag and drop from local cache space to desktop app for uploading. The new file in the local cache is not even shown within the desktop app.A feature which can show som

Request for Feature Enhancement (RFE) Summary: Having an editorial feature to configure mapping of JSON fields Use-case: To decouple SPA deployments from Adobe Experience Manager (AEM), Having an adapter layer that facilitates dynamic mapping of JSON fields between AEM components and frontend SPA components. This approach ensures that changes in frontend development require minimal configuration in AEM, promoting a more agile and independent deployment process.  Current/Experienced Behavior: SPA deployment has to align with AEM deployments whilst mock data mapping in place. Improved/Expected Behavior:  Realtime testing in pre-prod environments before hand. Also, helps in productivity by reducing dependencies in wider teams(Infra Dev and QA) Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: PremierLeague Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently, the list of available languages displayed in the Language Copy dropdown is sourced from the out‑of‑the‑box definitions located in /libs/wcm/core/resources/languages. To add or customize languages (such as adding Kazakhstan using ISO code “kk” or “kk‑KZ”), customers must overlay this resource to /apps/wcm/core/resources/languages. This enhancement proposes introducing a configurable authoring dialog (or admin interface) that allows administrators to manage the languages list in the Language Copy feature without the need to overlay OOTB files. Problem Statement: Current Behavior: The list of supported languages is static and defined in the repository under /libs/wcm/core/resources/languages. Customizations require creating an overlay (/apps/wcm/core/resources/languages), which is manual, error‑prone, and requires technical expertise. Impact: Customers who need to add or update language definitions (for exa

Request for Feature Enhancement (RFE) Summary: Request to make paraformat options configurable for Richtext field in content fragment in AEM 6.5.20  Use-case: Ability to author H4 to H6 in richtext field in content fragments in AEM 6.5.20 Current/Experienced Behavior: Richtext field(sling:resourceType=dam/cfm/admin/components/authoring/contenteditor/multieditor) in content fragment supports paraformat options from H1 to H3. If we have to add H4 to H6, it needs overriding of OOTB file /libs/clientlibs/granite/richtext/core/js/plugins/ParagraphFormatPlugin.js which should not be the case Improved/Expected Behavior: Please make the paraformat options configurable / make all the standard header options (H1 to H6) available OOTB Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.20 Customer-name/Organization name: NRG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: I often find my self in difficulty while comparing properties of a node in AEM CS instance, where crx/de is not accessible. So for accessibility purpose this will be a very good enhancement for Repository Browser in AEM CS. Use-case:   Current/Experienced Behavior: Repository Browser in its current form, is not having property type option as it used to be in CRX/DE so it is often confusing where it is String or Long or Boolean for some of the value. Though it is provided "[]" for array type but which type of array it is. Some time we just need to compare number of property, since there is no numbering for each property we need to count one by one property this is very problematic. Improved/Expected Behavior: Type column for property and serial number for the same should be there. Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Organization name: NA Screenshot (if

Request for Feature Enhancement (RFE) Summary: On our application, due to member firms structure, non-ISO locale are used (e.g. DE-DL Germany Legal). OOTB  "JcrResourceBundleProvider" implementation doesn't recognize non-ISO code and returns the default value instead of locale specific translated value. A support ticket was created [1] and got a confirmation that non-ISO codes are not supported.   I am raising this enhancement request to recognize the non-ISO locales as there many sites with this format.   [1] https://experienceleague.adobe.com/home?lang=en&support-tab=my-cases&case-id=E-001650678&org-id=BEAD1EB7647ED25F0A495C7C%40AdobeOrg#support Use-case: Same as above Current/Experienced Behavior: non-ISO locales are not recognized by i18n (JcrResourceBundleProvider), due to this expected translated value is not returned Improved/Expected Behavior: expectation is to get the value of non-ISO locales Environment Details (AEM version/service

Request for Feature Enhancement (RFE) Summary: Add a “View as Published” button directly in the Site Content View for each page, without needing to open the page in the editor Use-case: Content authors and reviewers frequently need to preview how a page will appear on the published site. Currently, they must: 1. Go to the AEM Sites Content View. 2. Select the page node. 3. Click Edit to open the page. 4. Then click View as Published from the editor toolbar.   This process is repetitive and time-consuming, especially when reviewing multiple pages Current/Experienced Behavior: “View as Published” is only accessible from within the page editor. Users must load the page in editor mode just to preview a page. Improved/Expected Behavior: A “View as Published” option should be available directly in the Site Content View, perhaps as a button in the toolbar for selected pages. This allows quick and efficient access to the published view without entering the editor, improving

  Request for Feature Enhancement (RFE) Summary: Introduce the Apache mvnd (Maven Daemon) wrapper in Adobe Cloud Manager so that the build step can reuse a long-lived JVM, parallelise module compilation, and dramatically cut cold-start overhead. This change targets only the build phase; the deploy phase likely remains untouched. Use-case: Large, multi-module AEM as a Cloud Service projects (often 10 + modules) can spend several minutes just starting Maven and resolving plugins for every pipeline run. In busy CI/CD setups (feature branch builds, frequent merges, scheduled quality gates) these wasted minutes quickly accumulate, slowing feedback loops and consuming CI minutes. Current/Experienced Behavior: Cloud Manager invokes the stock mvn CLI in a fresh container for each build. Each invocation spins up a new JVM, scans plugins, and builds modules sequentially. Typical build duration for a representative 10-module project: 9–11 minutes, of which ~1-3 minutes are Mave

Request for Feature Enhancement (RFE) Summary: Request to have read-only fields in Context Aware Config to protect the integrity of the data Use-case: Sometimes we tend to store API keys or secret keys in context aware configurations for different markets to be used. So if we can create read-only fields in the CA config, then we can prevent someone from accidentally modifying it.  Current/Experienced Behavior: Currently we can use String fields which are editable via authoring Improved/Expected Behavior: String fields with read only behaviour Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.2+ and cloud Customer-name/Organization name: Ramkumar Pandian Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： We would like to be able to set the SameSite=None,Secure=Yes options for the saml_request_path (Cookie) configured in the "Adobe Granite SAML 2.0 Authentication Handler" ユースケース： I am performing SAML integration with the following configuration, but the value of saml_request_path (Cookie) cannot be obtained, so I am moved to the default destination after logging in. ・Uses "Adobe Granite SAML 2.0 Authentication Handler"・Configures two sets of Dispatcher-Publisher・Logs in on the IDP login screen after a period of time・Returns to the Dispatcher that did not send the request 現在／体験した動作： Cookies that do not specify the samesite attribute will become samesite=lax a few minutes after the cookie is generated.Therefore, saml_request_path (Cookie) created by another Dispacher cannot be read. 改善／期待される動作： Set SameSite=None Secure=Yes to always read saml_request_path (Cookie). 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM6.5(SP19) 顧客名／組織名 TDEN スクリーンショット（ある場合）   コードパ

Request for Feature Enhancement (RFE) Summary: Ability to disable the Publish functionality on Assets View Use-case: When using AEM Assets with Dynamic Media with OpenAPIs, the 'Publish' functionality is not relevant anymore as assets are published by 'approving' the asset. Current/Experienced Behavior: In an architecture based on Assets View and Dynamic Media with OpenAPIs, users see a Publish option, which is not supposed to be used. The Publish prompts occurs upon asset upload, which is confusing for the users. Improved/Expected Behavior: Ideally, there should be a configuration option to enable or disable the Publish feature depending on the the architecture needs. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service - Assets View interface. Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently we are not able to configure external github repositories to a Configuration deployment pipelines. When we add non-adobe github repo, it throws error  `An external repository is not yet supported for this type of pipeline.` Use-case: We were migrating from internal TFS repo to enterprise github repository. We to point other pipelines: Code Quality, FullStack, Front End pipelines to external Git. Just the configuration deployment pipeline alone is blocked. Sounds like temporary limitation, it is intentionally blocked.  Current/Experienced Behavior: When changing repository to external non-adobe, it is throwing error    Improved/Expected Behavior: Configuration pipeline should allow external non-adobe github repositories Environment Details (AEM version/service pack, any other specifics if applicable): 2025.3.20133.20250325T063357Z Customer-name/Organization name: SouthernGlazers Screenshot (

Request for Feature Enhancement (RFE) Summary: Introduce a built-in visual debugging tool in AEM Author to detect and highlight failed ClientLibs loading (eg. 404s, category mismatches). Use-case: AEM pages often break in layout or functionality due to missing or incorrectly loaded ClientLibs, especially during template development or after dispatcher/CDN deployments. Authors and content editors face difficulties identifying these issues quickly without browser dev tools expertise. Current/Experienced Behavior: Missing ClientLibs result in broken layouts, JS errors, or missing styles/scripts - but no warnings are visible to non-technical users on the page itself. Only browser dev tools or logs reveal these issues, making root cause analysis slow. Improved/Expected Behavior: AEM should highlight missing ClientLibs visually on the page, or provide a debugging overlay or console warning for authors. This should include category mismatch detection, permission issues, and HTTP er

Request for Feature Enhancement (RFE) Summary: Provide a restore functionality for Assets Console Use-case: As an editor, if I have accidentally deleted one asset from the Classic Assets Console (/aem/assets.html) in AEMaaCS or even a folder with hundreds of assets, I would like to have an easy way to restore the deleted item(s). Current/Experienced Behavior: Currently, I have no chance to restore them. The only option is to do a "Restore content" via Cloud Manager, done by the admins which would restore the whole instance and with that changes, which have been done in the meantime, will be gone.I do not understand why a enterprise CMS does not offer such a basic functionality like a trash folder for asset! Improved/Expected Behavior: Provide a trash folder for the Asset Console were deleted items first end up after deletion. From there they could be restored. Of course some purge task should clean up here after a certain time which should be configurable.The new Assets UI has

Request for Feature Enhancement (RFE) Summary: Scheduled Copy content activities to lower environments from Prod environment Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable the capability of scheduled copy content activities to lower environments from Prod environment. This feature would allow DevOps/Support teams to trigger content copy activities to lower environments on specific dates and times through GenAI-based workflows in a scheduled manner.   Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of Copy content activity , Greater efficiency and reduction in the waiting times during monitoring ( incurred by the support team while content is being copied in Stage and Dev ). Aut

Request for Feature Enhancement (RFE) Summary: Reducing Stage/Prod deployment Pipeline execution Time Using GenAI Models in AEM Cloud Manager Use-case: We are requesting for the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to reduce the execution time required for stage and production deployment pipelines in AEM Cloud manager. This feature would fast-track regular deployment tasks in the Adobe Cloud pipeline using GenAI models , including Unit Testing, Code Scanning, Image Building, Product Functional Testing, Custom Functional Testing, Custom UI Testing, and Experience Audits. Key Benefits: Accelerated Deployment: GenAI models optimize and expedite deployment tasks, significantly reducing the overall pipeline time. Enhanced Efficiency: Automate routine tasks such as unit testing and code scanning, allowing for faster and more reliable deployments. Predictive Analytics: Utilize GenAI to predic

Request for Feature Enhancement (RFE) Summary: Scheduled Stage and Production Deployments Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable scheduled Stage and Production deployments ( at the time as scheduled by the DevOps team ). This feature would allow DevOps/Support team to trigger stage and production deployments at specific times through GenAI-based workflows. Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of deployments , and reduction in the waiting times ( incurred by the support team while code is being deployed in Stage and Prod ). Automated Scheduling: Application teams can set precise deployment times, ensuring updates occur during optimal windows, such as off-peak hours