Adobe Experience Manager

In Adobe Experience Manager (AEM), performing a rollout from a blueprint currently requires the initiating user to have at least read access to all live copies associated with that blueprint. If the user lacks access to even one unrelated or newly created live copy, the rollout operation fails—even when the user has full permissions on the blueprint and the intended target live copy.This behavior creates significant operational challenges in large, multi-site or multi-tenant environments where: Editors are intentionally restricted from accessing unrelated live copies New sites are frequently added under the same blueprint Permission models are designed to enforce strict content isolation As a result, editors are blocked from performing legitimate rollouts, while administrators can perform the same action successfully. This forces teams to either over-provision permissions, rely on admin intervention, or introduce service-account-based workarounds, all of which increase operational

!--startfragment>I want to use the AEM List Folder module in Workfront Fusion to fetch subfolder data. However, while creating the connection I keep getting a 400 error.To troubleshoot, I went to the Adobe Developer Console, created a project, and added the AEM Assets Author API. But when I try to configure authentication, there is no option available for Server-to-Server OAuth.Because of this limitation, I am unable to connect the module.Could you please advise how to solve this problem, or if there is any alternative solution to connect Fusion with AEM Assets for listing folders?!--endfragment>

adaptTo() turns 15 in 2026. From 28–30 September 2026, we’ll meet in Berlin for three days of developer talks and discussions focused on AEM and the underlying open-source stack.Details, tickets, and Call for Papers:https://adapt.toTickets are now available. Loyalty Tickets are available for returning attendees, and Early Bird pricing runs until April 12, 2026.The Call for Papers is open until 5 April 2026 — submit your talk!Please note: This year we’ve adjusted the schedule to allow arrival on Monday morning without missing content.Registration starts Monday at 11:00.Conference begins Monday at 12:00.– adaptTo() Conference Team

 I'm excited to recognize ​@Tad_Reeves as our AEM Champion of the Month for February! 🤩 👏Over the past two years, Tad has made a meaningful impact within the AEM Champion Program—and even further across the broader AEM ecosystem. From sharing expertise on the mainstage to showing up consistently for the community, his contributions speak for themselves (many of them powered by countless miles on two wheels 🚴🏼‍♂️).Please join me in congratulating Tad on this impressive achievement.

Date: Wednesday, February 25, 2026Time: 10am ET | 4pm CESTLink to register: https://aem-augs.adobe.com/aem-assets-dam-global-user-group/ Interested in learning how to double-down on your AEM Assets + Marketo integration? Check out our upcoming AEM User Group meeting, hosted by 4 Adobe Champions - ​@mbartlett, ​@Avinash_Gupta_, ​@coreybay, and ​@mariacruz !In this panel discussion, Adobe Experience Manager and Marketo Champions will share real-world guidance on integrating AEM Assets with Marketo to drive efficiency, consistency, and better campaign outcomes.The conversation will explore topics such as: Best practices for syncing and activating assets across AEM Assets and Marketo Governance, permissions, and approval workflows for marketing teams Common integration challenges and anti-patterns—and how to avoid them Tips for maintaining brand consistency while enabling speed and flexibility Real-world use cases and lessons learned from production environments Attendees will leav

Hi, We have a requirement to render PDF from Adaptive form on AEM 6.5.The rendered PDF should have the data from the Adaptive form as well. Currently I am using the below code window.guideBridge.getDataXML( { success: function(result) { var formData = new FormData(); formData.append("dataXml",result.data); var url = "servletpath?data=" + result.data + "&path="+path;to fetch the formdata from the adaptive form. This script is trigged on clicking a button in Adaptive form.A custom servlet is called from this script, which uses formservice.outputservice to render static PDFs along with data. The issue that we are facing is that the application is placed behind SI proxy and the request is then redirected from SI proxy server to AEM load balancer. In this case, the SI prxy server is appending url /abc/def/ to access all the pages on AEM.As a result, the AF are available on <SIProxydomain>:

Hi Team,When I tried to generate xdp letter from my local AEM cloud, getting the below error in error logs. Can anyone suggest on this?Java version - 17SDK - aem-sdk-2025.8.21994.20250818T175115Z-250700Forms addon - aem-forms-addon-2025.08.31.00-250900.far *ERROR* [[0:0:0:0:0:0:0:1] [1770809309168] POST /bin/fc/fmcc-ssd-daas/v2/generate-document HTTP/1.1 585c44b2-bf28-4fda-a01f-c0ec56500bd5] com.adobe.forms.xfanative.sdk.impl.XFANativeServiceImpl Error resolving templatejava.lang.IllegalStateException: Error getting shared temp directory, check whether the SDK started successfully.    at com.adobe.forms.xfanative.sdk.impl.XFANativeServiceImpl.resolveTemplate(XFANativeServiceImpl.java:389) [adobe-lc-forms-xfanative-sdk:10.0.378]    at com.adobe.forms.xtg.impl.XMLFormServiceImpl.$anonfun$resolveTemplateCacheGen$2(XMLFormServiceImpl.scala:211) [com.adobe.aemfd.adobe-lc-forms-core-common:2.0.144]    at com.adobe.forms.logging.PerfLogger.measure(PerfLogger.scala:61) [com.adobe.aemfd.adobe-l

After upgrading to the latest LTS version of AEM, we have encountered an issue with the Rich Text field using the resource type cq/gui/components/authoring/dialog/richtext. When saving any sentence containing two consecutive curly braces {{, the data is not being stored correctly in CRX. Specifically, the double curly braces are being replaced with {<!-- -->{, which causes problems when the final HTML is generated.Steps to Reproduce:Open a dialog with a Rich Text field (cq/gui/components/authoring/dialog/richtext).Enter the following content:<p>{{someData['someData']}}</p>Save the dialog.Check the value stored in CRX.Expected Result: The data should be saved as entered:<p>{{ContentBlock['chaseContactUsFooter']}}</p>Actual Result: The data is saved as:<p>{<!-- -->{someData['someData']}}</p>This unexpected replacement of {{ with {<!-- -->{ is causing issues in the rendered HTML and breaking our templating logic.This issue occu

Join the conversation as part of the AEM - Benelux User Group, expertly managed and hosted by ​@shrutidamle and Harsha Booravalli!This is your chance to connect with AEM professionals virtually and in-person in the Benelux region. Whether you're just starting out or a seasoned expert, this group offers a space to share experiences, explore best practices, and grow your network. Join a community of like-minded individuals who are just as passionate about AEM as you are. The kickoff meeting is coming up soon! Join the chapter and then register for the meeting:Date: Wednesday, March 18Time: 4pm CETLocation: VirtualJoin the AEM - Benelux User Group Chapter here: https://aem-augs.adobe.com/aemug-benelux-chapter/

Geo-based redirects are a common technique used to route users to regional content (for example, redirecting / to /us/ or /ca/).In Adobe Experience Manager as a Cloud Service (AEMaaCS), these redirects are often implemented at the CDN layer, before requests reach Dispatcher or Publish.While technically effective, this approach can introduce unintended SEO side effects if not carefully designed.Why this mattersSearch engine crawlers do not behave like end users: Crawling locations are limited and inconsistent Geo signals may not reflect real user geography CDN-level redirects can be applied uniformly to both bots and users When geo-based redirects are enforced unconditionally at the edge, crawlers may: Index an incorrect locale Fail to discover alternative regions Encounter redirect chains that reduce crawl efficiency These issues often appear without visible errors in AEM logs or monitoring tools.AEMaaCS-specific considerationsIn AEMaaCS, the mandatory CDN layer plays a critica

Adobe Experience Manager as a Cloud Service (AEMaaCS) introduced a stricter and more explicit approach to configuration management. Configuration is no longer a runtime concern but a core part of application architecture, deployment, and governance.This overview summarizes the primary configuration models available in AEMaaCS and their intended use cases. For a deeper explanation, architectural guidance, and practical examples, see:https://medium.com/@konstantyn.diachenko/making-sense-of-configuration-in-aem-as-a-cloud-service-7f2fc567e58dOSGi ConfigurationOSGi configurations define technical and behavioral aspects of code execution, such as: Service wiring Feature flags External integrations System thresholds and limits In AEMaaCS, OSGi configurations are: Immutable at runtime Deployed through CI/CD Parameterized using environment variables where needed Use OSGi configuration when values are developer-owned and affect application behavior.Context-aware configurationContext-A

 Index Traversal in AEM: A Common Source of Performance Issues by @daniel-strmecki IntroductionIndex traversal is one of the most common and most misunderstood causes of performance issues in Adobe Experience Manager (AEM). It rarely appears during local development or early project phases, but tends to surface once a system goes live, content volumes grow, and real user traffic starts hitting authoring and delivery workflows. What makes index traversal particularly dangerous is how easy it is to introduce. A single custom JCR query, a reporting feature, or an authoring UI enhancement can quietly trigger queries that scan tens or even hundreds of thousands of nodes. At first, the impact may be barely noticeable. However, over time, content grows, and queries accumulate, increasing CPU usage, slowing down AEM Author, and in the worst cases, destabilizing entire environments.Because traversal warnings are logged rather than surfaced as functional errors, they are often ignored or misunde

Dear AEM Community,Happy New Year 2026!Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for January 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS

Hi everyone,I’m working with the Search Panel Explorer in the AEM Editor interface, based on the documentation below:https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/user-guide/author-content/work-with-editor/editor-interface-features/search-panel-explorerWhat I’m doingI’m adding custom search filters using the ui_config.json approach, similar to the solution described here:https://experienceleaguecommunities.adobe.com/adobe-experience-manager-guides-11/aem-guides-search-customization-not-working-as-documented-14210?postid=435242#post435242Using this method: I’m able to successfully add new filters to the Search Panel The custom Tags filter appears and functions correctly Issue I’m facingFor the custom Tags filter, I’m not able to restrict or configure the tag root path.Even after setting the desired root (for example /content/cq:tags/products), the Tags field still shows tags from the entire global tag tree instead of the expected subtree.My questions When

🎉 The AEM Champion Program is thrilled to announce our inaugural AEM Champion of the Month for January, ​@KatieJu1!Katie has been an incredible asset to the AEM Champion Program for the last 2 years. A seasoned AEM expert, she has shared her insights via The Skill Exchange sessions, articles on Experience League Perspectives, webinars, Adobe User Group meetings, and more. She is also a joy to work with - speaking for myself and her peers.The Champion of the Month initiative aims to recognize and celebrate an AEM Champion each month who has exemplified exceptional thought leadership and engagement through the program. We are elated to be rolling out this program to recognize a member of our 2025-2026 AEM Champion cohort each month.Please join us in celebrating Katie for this remarkable achievement. Thank you, Katie, for your leadership! 

Greetings,We have a strange issue with our etc mapping structure, our project has a lot of domains and all of them are under etc/map, the recommendation for a better structure was to follow this guide/etc/map/         https/                 www.example.com.443/                           rulenodes But this approach makes it so the domain disappearsleaving https: //matchedPathWe do not know how to format the sling:internalRedirect and sling:match properties in order for the rules to work like they do under just etcAny help would be appreciatedBest Regards,Daniel

 Stop Guessing: Visualize AEMaaCS Editor Activity with Splunk by @daniel-strmecki IntroductionWhen we talk about performance optimization in AEM as a Cloud Service (AEMaaCS), we usually focus on Dispatcher caching, CDN configuration, frontend performance, query indexing or backend refactoring. What often gets overlooked is the actual editor activity on the Author environment. Knowing how, when, and how intensely editors use AEM Author is critical operational information. Heavy editorial activity can significantly impact Author performance without proper optimizations in place, especially during peak hours. Conversely, periods of low editor activity present ideal windows for running content cleanup jobs, bulk imports, reindexing, or maintenance tasks that would otherwise degrade the editor experience.In this post, we’ll walk through how to build a Splunk dashboard to gain clear visibility into editor behavior on AEMaaCS Author. The goal of the dashboard is simple: to understand editor u

Hi everyone,I am migrating an AEM Forms (ICC) project to AEM as a Cloud Service. My bundle is failing to start and remains in the "Installed" state due to a dependency conflict.The Error: Looking at the bundle status in the Cloud console, I see the following mismatch:The Server provides: com.adobe.aem.forms.ic.print.api.PrintChannelRenderService My Bundle requires: com.adobe.fd.ccm.channels.print.api.service.PrintChannelServiceThe Blocker: I need to update my Java code to use the new com.adobe.aem.forms package names. However, I am unable to find the correct Maven dependency/library to include in my project. I have tried adding aem-forms-sdk-api to my pom.xml, but Maven returns a "Not Found" error for the artifact in the Adobe public repository (https://repo.adobe.com/nexus/content/groups/public).Questions:What is the correct Maven dependency and version to use for AEM Forms Cloud Service to access the com.adobe.aem.forms.ic.print.api package? Is there a specific repository I should be

See below for the schedule of AEM User Group meetings for February:💜 [IN-PERSON] February 11 @ 1pm ET: "What You Missed While Watching AI : Edge Delivery Edition" with the AEM - Midwest chapter💜 [VIRTUAL] February 12 @ 5pm IST: "Optimizing AEM Delivery: Dispatcher vs. CDN in Modern Architecture" with the AEM - India chapter💜 [VIRTUAL] February 18 @ 11am EST: "Sites Optimizer Overview & Panel" with the AEM - Champion Office Hours💜 [VIRTUAL] JUST ADDED - February 24 @ 12:30pm EST: "Architecting for Speed: How Splunk Migrated to Adobe Edge Delivery Services (EDS) in 80 Days with 100% Core Web Vitals" with the AEM - Southwest Chapter💜 [VIRTUAL] February 25 @ 10am EST: "Optimizing the Content Supply Chain: AEM Assets + Marketo" with the AEM - Global DAM Chapter💜[VIRTUAL] JUST ADDED - February 26 @ 1pm EST: "Agentic AI in AEM — From Hype to Practical Workflows" with the AEM - DMV area ChapterWhether you're a Developer, Architect, Product Owner, etc, this is the program for you!Regi

 Leveraging AI Translation Tools in AEM: Example using DeepL? by @daniel-strmecki IntroductionAI-powered translation has undergone significant improvements over the past few years. What once produced awkward, literal results has evolved into language output that is often remarkably fluent and context-aware. For many use cases, modern AI translations are already close to perfect.Still, close to perfect is not the same as ready to publish. Brand tone, domain-specific wording, legal nuances, and SEO considerations mean that manual review is still required before publication. The real breakthrough of AI translation is therefore not full automation, but the speed gains. Modern AI translation tools enable teams to generate high-quality drafts in seconds instead of days, shifting human effort from translation to review and refinement.For Adobe Experience Manager (AEM) projects, especially large multi-language enterprise websites, this change has a massive impact as it can save significant tim

Currently, if you delete an asset via new Assets UI [1] this will end up in the trash folder. From here, you are able to restore it easily.Although CF are stored below /content/dam this functionality is not there for CF! Why is that. CF are holding same important content (maybe more if delivered to different channels) like an asset. Why does Adobe not offer the function? Please implement the restore functionality for CF!  

Dynamic Page Publishing in AEM Edge Delivery with BYOM and App Builder   by Lars Auffarth Introduction Bring Your Own Markup (BYOM) is a powerful feature of Adobe Experience Manager (AEM) Edge Delivery Services that allows you to programmatically generate HTML pages from a dynamic HTTP endpoint. Rather than relying on authored content or documents, BYOM enables automated page rendering from APIs, product databases, or other backend systems - while still using the same semantic blocks and styling shared across your AEM site. In this post, we’ll explain how BYOM works, how it fits into the AEM Edge Delivery Services rendering pipeline, and how to integrate it cleanly using Adobe App Builder. Key Points BYOM is ideal for building dynamic, API-driven pages in AEM Edge Delivery Services - without sacrificing performance or consistency. In this post, we’ll walk through: What BYOM is and how to think of it as an “HTML API” How BYOM fits into the Edge Delivery Services publication fl

Hi Community, I want to define a rule in the cdn.yaml using the origin selector as described in the documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-configuring-traffic#origin-selectors that would route the traffic for a particular path to an external website (www.website.com).Something similar to originSelectors: rules: - name: blogs when: allOf: - reqProperty: tier equals: publish - reqProperty: domain equals: <our domain> - reqProperty: path matches: "^/en-us/prefix/.*"However, prior the routing I want to manipulate the path, so the /prefix part is eliminated and for the /en-us/prefix/page path it would send a request to www.website.com/en-us/page.We have this logic working at the dispatcher tier using the ProxyPass directive. I am trying to understand if the same logic can be handled at the cdn level. Regards,Rustam 

I created a graphql endpoint for my content fragment and it is working fine in author/publisher/dispatcher. Now I am trying to setup cache rule for the  AEM persisted query. I followed below doc and setup the dispatcher config. But the cache is not happening at dispatcher level. Note this is AMS (AEM 6.5.22) https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/deployments/configurations/dispatcher-filtershttps://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/deployment/dispatcher-caching Add the variable to the Dispatcher file global.vars:Define CACHE_GRAPHQL_PERSISTED_QUERIES /src/conf.dispatcher.d/filters/dexa_publish_filters.any/0152 { /type "allow" /method '(GET|POST|OPTIONS)' /url "/graphql/execute.json*" } src/conf.dispatcher.d/cache/dexa_publish_cache.any/0000 { /glob "*" /type "allow"}/0003 { /glob "/graphql/execute*.json" /type "allow"}## Don't cache csrf lo

EXPECTED RESULTA new project OOTB that has Content Fragments enabled would allow an admin user to create language copies for Sites and Assets ,and create language copy of assets using the DAM Language Copy workflow would work by default. A custom translation project should not have to be created, nor should translation automation be required for assets. ISSUEI have created a new project and noted that I am not able to see / access the create language copy button for assets.  Observe that the option is missing from the menu by default as shown in image.  User then attempted to use the OOTB workflow to create the language copy, and user encountered an error message (see below). What is somewhat ODD is that these failures do not show up in the folder "Workflow Failures" Assumption is that there is a permission based issue that is potentially causing this issue, but user has not been able to locate any incremental permission(s) that would logically result in t