Adobe Experience Manager

Missing keys/keyrefs used to generate specific “filler” content in the PDF: Key definition for "{keyrefName}" not found in the DITA map. With our upgrade to v5.1.1, this filler content no longer generates in the PDF and instead nothing generates to indicate any missing keys. Was this intentional? Is the only wayt to find missing keys to preview on-screen and look for red?

A third-party penetration test flagged that PDF files downloaded from our AEM publish instance contain embedded metadata revealing software version information (e.g., Adobe InDesign 19.5, Adobe PDF Library 17.0, Adobe XMP Core 9.1). The security team requires this metadata to be stripped before the file is served to end users.We are requesting Adobe's official confirmation that AEM as a Cloud Service does not modify or strip metadata embedded within the binary content of uploaded DAM assets, and guidance on the recommended approach. What We Tried 1. Removed XMP metadata properties from the JCR metadata node2. Deleted the entire metadata node

Hi,We have installed AEM 6.5 on C drive and due to some disk space issue, we need to move the installation to E drive on Production. Its is a on premise AEMIs it safe to copy the entire AEM folder from C to E by stopping and then starting after the files are copied to E drive on production.Are are any internal references to C location within the application, once its installation and running.Appreciate any assistance here. Thank you.  

Hi,When trying to create an Edge Delivery Services site via https://da.live/start, I get this error after entering my AEM GitHub repo URL:“You are not authorized to create this site in the corresponding DA organization.”I’m logged in with an Adobe ID that has AEM Author access, and I have access to the GitHub repository.Steps FollowedOpened https://da.live/start Entered my AEM codebase GitHub repository URL (example: https://github.com/<org>/<repo>) Clicked GoEnvironment DetailsAEM as a Cloud Service Edge Delivery Services Universal Editor enabled Logged in with my Adobe ID (has AEM Author access) GitHub repository is accessible to meWhat I’ve Already CheckedGitHub repo access ✅ Logged into the correct Adobe account ✅ Edge Delivery is enabled for the program ✅Questions:What permissions or roles are required to create a site via da.live/start? Does the user need to be explicitly added to a DA / Edge Delivery organization in Adobe Admin Console? Is this controlled by IMS org,

Environment:AEM as a Cloud Service using Edge Delivery Services (EDS). Authoring through the Universal Editor (UE) and standard AEM Sites console. Translation Provider: Out-of-the-box (OOTB) Microsoft Translator.Requirement: We need an automated "zero-click" translation process.Source Language: English (/content/gmr/en) Target Languages: Multiple (tr, fr, es, ja, etc.)When an author modifies English content, it should automatically trigger a translation to all target languages and update the language copies for EDS delivery.Current Issues:Missing Rollout Option: The standard "Push to Translation" rollout configuration is not available in our AEM Cloud instance. Launcher Failures: We have configured a Workflow Launcher on Node Modified to trigger the WCM: Translate Language Copy workflow. The workflow instance starts but remains in the "RUNNING" state indefinitely. The setup works perfectly when triggered manually via the "References" panel, but the automated version hangs. MSM Integr

I have a section of my site on EDS while the majority of it is on AEMAACS. My question was on how to include launch script to my EDS pages, since they are environment specific?

A recruiter called me last month.She had an open AEM Product Manager role. Been open for 3 months. Plenty of applicants. But none of them understood the new AEM.Here's what changed —AEM isn't just a content management system anymore.Adobe just launched MCP Servers inside AEM — meaning developers can now use AI tools like Cursor, Claude Code, and Visual Studio to write, debug, and deploy AEM code without leaving their editor.They also launched LLM Apps — a capability that lets brands build experiences that live directly inside AI interfaces like ChatGPT and Gemini.Think about that.Your website content... delivered inside an AI conversation.AEM is quietly becoming the backbone of how brands show up in the AI era.But most hiring managers are still writing job descriptions for 2022.The AEM talent market hasn't caught up yet. The candidates who understand this new AEM? They're rare. And they know their worth.If you're hiring AEM talent right now — the bar has moved.Are your job descriptions

I'm developing an Adobe App Builder integration to sync product data present in Salsify to AEM Content Fragments via the OpenAPI in my RDE environment. IMS OAuth authentication is working correctly (I'm obtaining tokens with the correct scopes: aem.fragments.management,aem.folders), and I've added my OAuth Server-to-Server credential to the "AEM Sites Content Managers - Author" product profile in Admin Console.However, when my App Builder action calls the Content Fragments API (GET /adobe/sites/cf/fragments), I receive a 403 Forbidden error with: "IMS Client ID not allowlisted. Allowlist the Client ID using the Configuration Pipeline."How do I properly configure my RDE environment to allow this OAuth Client ID to create and manage Content Fragments?Specifically:(1) What is the correct method to allowlist the Client ID in an RDE  environment (2) Should I add the OAuth credential to any other product profile instead of "Sites Content Managers"?(3) Is there additional RDE-specific configu

Hello,Since enabling some of the beta capabilities in Content Hub, we’ve noticed significantly slower load times than before. Are others experiencing this as well? If so, have you found any ways to address it?Thank you!

Go to https://da.live/, navigate to your site, update the organization permissions, and then publish the page from the console.

In the hierarchy the root object’s properties are no longer available to make changes to the settings.  This makes the pages objects under it unavailable in to the settings of the Pagination window.  Without these settings being usable then pages can’t be assigned to masterpages.

What are the best practices for managing graphics and ensuring the most recent copy uploaded to the repository is the current VERSION, not just a working copy?All documentation on version control I’ve found for Guides is specific to the DITA files, not graphics objects.When we upload/copy an updated graphic, the popup windows asks us if we want to create a version of the EXISTING working copy. It does not ask about creating a version for the correction we are uploading. It looks like whatever we last uploaded remains a working copy, not an actual version, which means graphics sent out for translation may not be the most recent and correction file.Does this mean any time we upload a corrected graphic, we have to drag/drop twice. Once to upload and force the system to create a new version of the existing working copy and the new graphic become the existing working copy. Then a second time to force that correction to be the newest version?I’m seeing graphics that I know have been changed/

Hi everyone,After a successful Kick-off to AEM User Group Benelux chapter —We’re looking for speakers for our next session!Whether it’s a short demo, a case study, or lessons learned from your AEM projects. If you’re interested in sharing, we’d be happy to support you and feature you in one of our upcoming Quarterly user group events.It will be a wonderful opportunity to share your thoughts with fellow AEM practitioners, and inspire their thinking to explore what’s possible with AEM.Your session will also be recorded and hosted on a closed YouTube channel to benefit other AEM enthusiasts and practitioners.What topics would you find most valuable? Are there challenges, use cases, or ideas you’d like to explore in future sessions?Feel free to email me at: shruti.damle@deptagency.com or connect with me on LinkedIn to share your thoughts or ideas.Looking forward to shaping the next session together!Cheers,Shruti Damle, AEM User Group - Benelux Chapter Leader

Hi,We are trying to syn asset metadata schemas from AEM Assets Old UI to the AEM Assets New UI, but we are facing several issues and need clarity on the expected behavior of the new UI.When importing metadata schemas from the Old UI, the schemas are created successfully but are not applied to any asset folder. In the New UI, there is a option to assign the imported schema to a folder but failing to add it to the folder. Even after creating a new metadata schema directly in the New UI, we are unable to apply it to an asset folder. We would like to understand whether folder properties can be viewed or managed in the New UI, and if so, how? Unable to delete the schema in the new ui.Could someone please clarify the intended behavior of metadata schemas in the AEM Assets New UI and share any relevant guidance if any configuration is missing our end.  referrence:https://experienceleague.adobe.com/en/docs/experience-manager-assets-essentials/help/metadata#metadata-forms

After upgrading to ACS Commons 6.15.4, ACS Commons pages are no longer editable via editor.html as they were in 4.x (for example, Dispatcher Flush and Adobe League pages now appear read‑only). Is this expected behavior? Do we have any supported workaround to retain the old page‑based editing model, or is using an older ACS Commons version the only option?https://xxxxxxxxx.dev.xxxxxxx.adobecqms.net/editor.html/etc/acs-commons/dispatcher-flush/test-lts.html  

Hi all,I'm working on an AEMaaCS workflow and would like to implement a custom Participant Step dialog with dynamic data coming from a previous Process Step.Here is my use case: An editor starts a workflow on a Content Fragment Editor receives a notification and completes the first task A custom Process Step collects all referenced nodes under the Content Fragment and stores them into workflow metadata like below: item.getWorkflow().getWorkflowData().getMetaDataMap() .put("discoveredNodePaths", collectedPaths.toArray(new String[0]));   In the next Participant Step: Editor opens the task from Inbox A dialog should display all discovered node paths as a checkbox group Editor selects some nodes and clicks "Ok" The selected nodes should be saved back into workflow metadata Next Reviewer step: Reviewer opens task and sees selected nodes Can approve or reject If approved, a Process Step publishes all selected nodes My questions is about step4: How can I customize the Participan

We can share the ideas, suggestions, bottle necks , do and don’ts, any known issues on projects with Eds + universal editor. We can meet in person and talk more about this share the knowledge.

Hi Team,Question 1I am using cloud SDK and experiencing jcr:title and jcr:description is not getting sync when I use OOTB rollout from master to live copies.anywhere I can look into custom configuration and add these properties.How to add them if they are not added ? Question 2I have checked libs/msm/wcm/rolloutconfigs and could not find anything related to these properties such as exclude node. I checked in apps/msm and could not find a custom configurations either so that meant we are using OOTB configuration only ? in that case do we need to raise a adobe ticket for this ?

 Hi Team,We are facing an issue on a multi‑locale AEM site, where some users from the EU region are seeing broken/distorted pages.SymptomsBrowser console shows errors indicating that CSS files are not loading properly In the Network tab, we see a 301 redirect happening for a ClientLib CSS URLExampleOriginal ClientLib URL:https://domain.com/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssRedirected URL:https://domain.com/de/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssSince /de/etc.clientlibs/... does not exist in AEM, the redirected request ends in a 404, which results in the page breaking.ObservationsThe same behavior is reproducible using a curl request (301 redirect observed) There are no references to /de/etc.clientlibs/...: Not in AEM configuration Not in Dispatcher Not in rewrite rules The only place where this URL appears is in CDN logs, where it shows cache=pass We are not caching an

Description:We are working on customizing the AEM Translation Project workflow to simplify the project creation experience.Requirement:The goal is to reduce unnecessary fields and configurations in the Translation Project creation dialog and project overview.Specifically:Remove unused properties from the Project Initialization Dialog Set a default translation language Restrict project templates and pods to only translation-related ones Ensure removed properties are not visible later in the Project Summary/Overview Only the Translation Project template should be visible during project creation. After the project is created, in the Add → Translation Job option, only the source languages "en" and "de" should be available for selection. What We Tried:Attempted overlay of:/libs/cq/core/content/projects/templates → /apps/cq/core/content/projects/templates Manual overlay via CRXDE Lite (facing errors) Verified permissions and access Compared configurations across environmentsFinally:     1. I

Hello, I have a user who seems to have all-but-Admin rights to AEM Assets, and has access to Content Hub. He is however unable to share Collections. When he creates a Collection, the only option for who has access is “Only you and admins can view and edit”. He says he has previously been able to create a collection and give public access, but this was only to one Collection. We’ve not been using Content Hub for too long so not sure what I might be missing!Thank youLana 

Hi,I have an requirement to convert the non-pdf to pdf documents, the AEM server installed is linux version. As per the Adobe documentation, Installed the openoffice and run the SRT. The response is nill. Also when checked with Adobe they are telling that there could be openoffice installation issue.I tried to reach openoffice team but there is no much use. can somebody help me here or guide on resolving this issue