Adobe Experience Manager

I am creating forms in Indesign with specific font styles to export into interactive pdfs to be used by non-designers for in store signage. Certain elements are not available to set in the forms window such as leading and creating centered or flush left or right text. I need help from someone who know how to do this. I can’t find documentation to make this work.

I want to create a Time Bound Date of Birth Component, may be by extending the datepicker aem form core component, where user is allowed to select a date between a specific date range, so once i have created this component then i want to use it inside the adaptive form, but how can i do this, i dont see any AEM forms core components under /apps/core/fd…., i am trying to install the latest service package and the forms add on package my instance is breaking, Kindly help here

 I am currently migrating AEM Classic Forms to AEM as a Cloud Service (AEMaaCS) and need to generate PDFs using an XDP template and XML data.I attempted to use the Output Service API as described in the documentation:Generate PDF documents using output service | Adobe Experience ManagerHowever, I am encountering import/package resolution errors when deploying my bundle to the local AEMaaCS SDK.Current Dependency (not working in AEMaaCS)<dependency><groupId>com.adobe.aemfd</groupId><artifactId>aemfd-client-sdk</artifactId><version>6.1.152</version></dependency>From my investigation, this dependency is intended for AEM 6.x (on-prem/AMS) and is not compatible with AEM Forms on Cloud Service.Proposed ApproachIt seems that for AEM Forms CS, the correct dependency should be:<!-- Source: https://mvnrepository.com/artifact/com.adobe.aem/aem-forms-sdk-api --><dependency><groupId>com.adobe.aem</groupId><artifactId>aem-

We are using the trackingfeature attribute in HTML file  like this:<coral-card trackingfeature="aem:tracking:test">In older AEM versions this works fine, but in AEM 6.5.2 LTS, the value is not getting set when it contains a colon (:). If we remove the colon (for example aem-tracking-test), it works correctly.Why is the colon value not working in AEM 6.5.2 LTS, and what is the correct way to use values like aem:tracking:test while keeping the colon?

We have a requirement involving seven different templates in AEM. For each template, we want to allow the Experience Fragment component, but with a restriction: the Experience Fragment should only allow the components that are specifically permitted for that template.In other words, each template has its own set of allowed components, and the Experience Fragment should enforce those rules so that authors cannot add components outside the template’s defined scope.We would like to understand: What is the best possible solution to achieve this scenario? Are there recommended practices or configurations in AEM to enforce template-specific component restrictions within Experience Fragments? Any guidance or examples from the community on how to implement this in a scalable and maintainable way would be greatly appreciated.

Adobe DITAWORLD 2026Join us for Adobe DITAWORLD 2026Three days. One global stage for the future of technical content.Join us at Adobe DITAWORLD 2026 for three days of inspiration, ideas, and innovation — featuring a stellar lineup of speakers from the world's leading brands. From real customer success stories to the latest in AI-powered authoring and structured content, there's something here for every technical communicator, content strategist, and CCMS leader.Why you won't want to miss it:Hear how global enterprises are scaling content with Adobe Experience Manager Guides Explore the role of Generative AI in technical communication — from drafting to delivery Discover best practices in structured content, DITA, and omni-channel publishing Connect with peers, partners, and the Adobe Technical Communication teamRegister for freeCan't attend live? Register to receive the recording.

We're doing a POC for a multi-tenant SaaS application that integrates with Adobe Experience Manager as a Cloud Service to enable bulk asset import functionality. Our application uses OAuth Web App authentication to access the AEM Assets Author API on behalf of authenticated users.Core Requirement:Our application needs to:Browse AEM folder structures List assets within selected folders Retrieve asset metadata (title, description, tags) Download original asset binariesCurrent Setup (Successfully Completed):✅ OAuth Web App credential configured in Adobe Developer Console ✅ Scopes: openid, AdobeID, aem.assets.author, aem.folders ✅ Client ID allowlisted via api.yaml deployed through Cloud Manager Config Pipeline ✅ User assigned to "AEM Assets Collaborator Users" Product Profile with "AEM Assets API Users" service enabled ✅ OAuth authentication flow working (successfully obtaining access tokens) ✅ Able to list folders using: GET /adobe/folders Issue - Unable to List Assets:adobe/assets?limit

Hi Experience League Community,   We are troubleshooting an issue with AEM Universal Editor in an Edge Delivery Services project.   The copy/paste functionality for components between pages was working before, but it recently stopped working. Authors can open and edit pages in Universal Editor, but when they try to copy a component from one page and paste it into another page, the paste action does not complete as  expected.   We have started reviewing Author logs and browser network traces, but we are not yet sure which area is most relevant to investigate.   We would appreciate guidance on what else to check, for example:   1. Universal Editor component definitions, models, or filters  2. Edge Delivery Services Configuration Service settings  3. Site/repository/branch configuration  4. Author permissions or access restrictions  5. Browser/network requests involved in copy/paste  6. Known limitations when copying components across pages or language/site branches  7. Any relevant Autho

Learn how Direct Counts Configuration in Oak helps improve AEM query performance by reducing expensive repository traversal and optimizing query result counting for trusted service users.#AEM #AEMaaCS #ApacheOak #AEMPerformance #QueryOptimization #OSGi #AdobeExperienceManager  Read More :- https://www.aemcq5tutorials.com/tutorials/how-direct-counts-configuration-improves-aem-performance-and-reduces-node-validation-overhead/ 

Hi ,  looking for guidance on a Scene7 + asset publish flow.We have a custom workflow where:We programmatically trigger the Scene7 workflow to generate renditions.Once processing appears complete, we publish the asset.After publish, we call an API on the Publish instance to retrieve asset details.Since Scene7 processing is asynchronous, we added an event listener to monitor the Scene7 status as publishComplete , before triggering publish.However, we are still seeing inconsistent API responses from Publish, which makes us think there may be a timing/replication/indexing/cache gap somewhere in the flow.One recurring issue we’ve observed:The asset shows “Publish Complete” status on AuthorBut the same asset appears with “ReprocessStart” status on PublishWe’re trying to understand why this discrepancy occurs and what the recommended integration pattern is for ensuring Scene7 processing is truly complete before publish/API consumption. We have already enabled the OOTB Scene7ActivationJobCons

I want to exclude assets from AEM Dam search if value is set searchable=false.can I do this by customizing damAssetLucene index. I can exclude a path from search but how can I do based on a property.

Curious how enterprise AEM Cloud teams are evolving Content Fragment modeling strategies as AI-driven personalization and multi-channel delivery become more common.Historically, many content models were designed primarily around page rendering and headless delivery needs. But with increasing AI-assisted content generation and dynamic experience orchestration, the modeling requirements seem to be changing rapidly.Interested in perspectives around:reusable fragment design metadata strategy AI-friendly taxonomy structures personalization scalability GraphQL performance considerations and governance for large content ecosystemsWould love to hear how teams are preparing their content architecture for more AI-driven experience delivery models.

AEM Multi-tenant Website: Restrict cq:tags for User Groups   by SourcedCode.com (Brian Ka Sing Li) Overview Of most common multi-tenant websites, user groups are used to determine what AEM content authors can make changes to. The most popular requirement for a multi-tenant website is the ability to only edit tags for a specific brand. In this case, the way you can achieve this is by permissions. In this blog, we will ensure that all “WKND Members” will be able to create, read, update, and delete nodes under /content/cq:tags/wknd-shared, while these members will not be able to read any other tags listed under /content/cq:tags/*. Click here to learn more: https://sourcedcode.com/blog/aem/aem-multi-tenant-website-restrict-cqtags-for-user-groups  

We are excited to announce our Adobe Experience Manager Champion of the Month for May, ​@VidyR​!  Vidy was a clear choice for this recognition, as she truly embodies the spirit of the Adobe Champion Program. Not only does she actively raise her hand to support key initiatives like speaking on our upcoming Champion Application webinar, writing articles on Perspectives, and sharing feedback with our AEM Assets Product teams, but she regularly attends AEM Champion social events and fosters relationships outside of programming. She is a rising star in our community, and the program wouldn’t be the same without her bright personality. Thank you, Vidy, for your leadership and commitment to the Champion Program!  

Congratulations to ​@Wilson-Faure for your recognition as our AEM Champion of the Month for April! 🙌 🤩Wilson has one of the most loyal fan bases of any AEM expert I know. On top of being wicked smart with Adobe Experience Cloud products, his generosity with his time and kind personality make him a true force within the community. As a Champion, he always goes the extra mile by hosting a User Group meeting, sharing best practices with customers, and, dare I say, "stealing the show" at the karaoke bar?!Wilson, thank you for being you. We’re so happy to have you as an Adobe Champion! 👏  

Hi,I am seeing an issue on trying to load a custom js on Adaptive form (edit/preview mode) on AEM author instance, but the same custom js is loading fine on AEM publisher.Adaptive form in created on AEM 6.5.24 and using foundation component.The custom js is located here: /apps/<project_name>/clientlibs/clientlib-adaptive-forms/custom.jsI want to initiate this custom.js on a button click on adaptive form.So in the rule editor for the button, I see an error, on trying to search for the custom function within custom.js. It shows as undefined variable. The reason is that, the custom.js is not loading on both edit/preview mode.All the files within this /apps/<project_name>/clientlibs is not loading on AEM author, but the it loads fine when the adaptive form in published on aem publisher?Any suggestions please? 

Hi All, I am trying to use OOTB Archive extraction process step with launcher, but when zip file is having nested folder and files , launcher is not able to extract it properly wheras with manual triggering workflow works as it is triggered by admin.With launcher I am getting below error org.apache.sling.api.resource.PersistenceException: Can't create valid output path    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.getValidPath(UnzipServiceImpl.java:206) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.validateFilePath(UnzipServiceImpl.java:220) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.handleFile(UnzipServiceImpl.java:211) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.processZipEntry(UnzipServiceImpl.java:159) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.processEntries(U

I have ran Best Practice Analyzer and found Content Area Violation on some of the shared fields across the project. The path: /apps/project-1/component/granite/ui/components/coral/color-picker/variations/ violates content areas override final path: /libs/granite/ui/components/foundation/form/select  and the content.xml for the component  is having as below   <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"     jcr:primaryType="sling:Folder"     sling:resourceSuperType="granite/ui/components/foundation/form/select"/>   How to resolve this Content Area Violation?

AEM as a Cloud Service now supports agentic translation powered by Azure OpenAI - replacing segment-level machine translation with an LLM that understands context, tone, and brand voice. I wrote a step-by-step guide covering the full setup: from creating an Azure OpenAI resource in Microsoft Foundry, to connecting it to AEM's Translation Integration Framework, to uploading brand style guides that generate enforceable translation rules. The article also covers what's not yet available (glossary and TM support) and where this is heading next. 📖 Full walkthrough: https://medium.com/@vorajineet/aem-meets-generative-ai-configuring-agentic-translation-with-azure-openai-11c4e617e2cf

I have a requirement to add a custom column to the list view along with the other OOTB fields in Adobe Experience Manager (AEM) Cloud instance. Could anyone guide me on how to achieve this? I want to add a column with header Content-Type that will fetch the value from jcr:content/metadata/content-type.I could achieve this with the reorder.jsp file pointed here: https://experience-aem.blogspot.com/2019/10/aem-6520-aem-assets-add-custom-metadata-columns-in-assets-console-list-view.html but this does not work in AEM Cloud.Again, this URL also explains in another way : https://experience-aem.blogspot.com/2019/08/aem-6510-adding-custom-metadata-columns-in-list-view-of-assets-search-console.html but again this conflicts with OOTB behavior and breaks the search functionality in AEMaaCS.Any concrete solution that works on cloud?

Hi, we are using AEM Guides Native PDF for publishing PDFs, and I wanted to check if others have encountered issues with table break behavior.Current behavior:Tables that begin and end on the same page render correctly. When a table spans across multiple pages: The portion on the next page starts directly with the table header. The table continues from where it was split, without any indication that it is continued. Expected behavior:Tables that begin and end on the same page should continue to work as expected. When a table spans multiple pages: The table portion on subsequent pages should display a label such as:"Table #: Table Title (continued)" This should be followed by the table header and the remaining table content. Example image: