Adobe Experience Manager Guides

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?

Complete Guide: AEM System User & Service User Mapping System users in AEM are used by backend services to access the repository securely without using an admin session. They are commonly used with the Sling ResourceResolverFactory to obtain a ResourceResolver.Using system users is a recommended security practice in modern AEM development.1. What is a System User in AEM?A System User is a non-login user used by services or backend code to access resources in the repository.Key Characteristics Cannot log in to AEM UI Used by backend services Has specific permissions (ACL) Works with Service User Mapping Why System Users Are ImportantOlder versions of AEM allowed: resourceResolverFactory.getAdministrativeResourceResolver()This method is now deprecated for security reasons. Instead, system users should be used.2. Architecture of Service User AccessTypical flow: AEM Service / Servlet / Scheduler↓ResourceResolverFactory↓Subservice Name↓Service User Mapping↓System User↓Repository A

Hi Team,Can we deploy AEM Guide in AEM RDE environment Thanks

We have an instance of AEM 6.5.12. with Guides 4.6 UUID running on a server and we want another instance of the exact same thing on another server that we will use as our “development server.” This is not an upgrade. We want the 2 instances to be identical.On our new server I have installed the exact same AEM 6.5 with the same service pack and same 4.6 release guides.  All we need is the repository from the first instance. I cannot use package manager to do this because we must preserve the version history of all of our DITA topics.  From the documentation I’ve read it seems the best way to do this is with ther CRX2OAK tool.I’m not experienced with migration and would appreciate any steps or advice you might have. First, is the CRX2OAK tool the  best way to accomplish this? How do I get one repository to connect with another? Should the crx-quickstart folder from the target server be on the same server as our first AEM installation?  If so, what is the best way to move the crx-quicksta

Hello,We’re in the process of setting up our AEM Guides instance and have that link to our Workfront projects. I’ve noticed that the Workfront tasks list of AEM Guides has a limited number of columns. It would be helpful to our users to see the task percent complete, start dates, and predecessors on this view. Is it possible to add more columns to this view either through the native connector between the two or through Fusion?

I am searching for the question/answer series titled “Translations - Latest source language version of the map was not sent out”. I’m not seeing it in the AEM Guides group and it wasn’t listed under my account within the list of questions I had posted. Were some posts lost in the move to this new URL/interface?

Hi All, I am new to AEM Guides and tried my hand at importing an existing DITA project from https://github.com/DITAWriter/pilot_training_mitchell_bomberThis is a DITA-fied version of the Pilot Training Manual for the Mitchell Bomber B-25 I installed the package - com.adobe.fmdita.uuid-6.5-4.6.1.5886.zipI was unable to install the package com.adobe.fmdita.uuid-6.5-SP due to dependency com.adobe.fmdita:com.adobe.fmdita.uuid-6.5:5.0.0.211I created a folder in my DAM project and dumped .dita files from the above repo in it. When I tried to access the same in Guides editor window I get the below -  If I try to go into “Preview” mode I get the “Loading preview...” overlay which doesn’t go away -   Can anyone help point what am I doing wrong here? Thanks,Nagesh

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

Hi,I am using AEM cloud and we have Guides, when we select an asset (dita), we are able to see a Open in Framemaker button which when clicked opens the asset in FM. Do we have anything as such for Adobe illustrator, if Yes how do we enable it?If No, how to we build one which works just like the Open in Framemaker button??  This is how to enable the Open in Framemaker button:ThanksSandeep

I’m facing an issue with AEM Guides on AEM as a Cloud Service while generating Sites output from a DITAMap that references Markdown topics using this documentation: https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/knowledge-base/kb-articles/authoring/webeditor/markdown-in-dita-and-aem-guidesWhat I’m seeing: The DITAMap → Site generation runs Site pages do get created Page properties (sourcePath, UUIDs, map references, etc.) are all set correctly along with the hierarchy of nodes. However, the content is missing - the “injected-container” on the page is empty This preset works for normal dita topics. Error in logs:Markdown resource cannot be read as an XML Document org.xml.sax.SAXException This happens during the NodeJS-based publishing workflow, specifically while Guides is extracting dependencies / DTD rules. From the stack trace, it looks like the Markdown file is being attempted to be read as an XML document.Pages are created but the Markdown conten

I am trying to migrate existing unstructured FrameMaker documents (.fm and .book) to DITA following the official documentation here: Migrate unstructured FrameMaker documentsHowever, I am unable to proceed because the Map to DITA (or Convert to DITA) button is missing from the Assets toolbar when I select my .fm file. When I open the file, I only see options to generate PDF, HTML5, and EPUB (as shown in the attached screenshot), but no option for DITA migration.Steps to Reproduce: Upload an unstructured FrameMaker file (.fm) to an AEM Assets folder. Select the file. Look at the top toolbar and the Output Presets panel. Actual Result: The Map to DITA button is not visible. Only standard Asset options and Generate (PDF/HTML5/EPUB) are visible. Expected Result: The Map to DITA button should appear to initiate the migration workflow using the .sts file. Environment: Adobe Experience Manager (2025.11.23385.20251113T172403Z) aem-guides (2025.10.0.278)  

I'm trying to install Adobe Experience Manager 6.5 on Windows Server 2022 on command with the following command C:\AEM\Author>java -jar AEM_6.5_Quickstart.jar -r author -p4502However the installation keeps getting stuck on "Press CTRL -C to shutdown the Quickstart Server:Loading quickstart properties: defaultLoading quickstart properties: instanceLow-memory action set to forkUsing 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]The JVM reports a heap size of 2048 MB, meets our expectation of 1024 MB +/- 20Setting properties from filename 'C:/AEM/Author/AEM_6.5_Quickstart.jar'Setting 'sling.run.modes' to 'author' from command line.Verbose option not active, closing stdin and redirecting stdout and stderrRedirecting stdout to C:\AEM\Author\crx-quickstart\logs\stdout.logRedirecting stderr to C:\AEM\Author\crx-quickstart\logs\stderr.logPress CTRL-C to shutdown the Quickstart server...Java version installed is 21.0.9.Any idea

When using a custom post-generation workflow in AEM Guides Cloud, the UI notification becomes stuck on "In Progress - Generating <output>..." indefinitely. In my case, I was using a Native PDF output preset. Even though the success message "hangs," and the PDF is generated successfully, and the workflow completes without errors.I'm using AEM Guides as part of the cloud service.SymptomsPDF generation completes successfullyCustom workflow executes and completes (verified in logs)FinalizePostPublish step runs successfullyPDF file is created in /content/dam/fmdita-outputs/pdfs/BUT: UI notification stays stuck on "In Progress..." foreverNo success notification or download link appears Root Cause AnalysisAfter investigation, I discovered that the output history node shows two different status properties:Location of output history: /var/dxml/metadata/outputHistory/ <id> / <id> With Custom Workflow:cloudStatus: "Finished" outputStatus: "Post-Publishing" <--&

We need to update the DITA-OT that is included with AEM Guides to get a newer version of FOP. I have managed to migrate our custom PDF plugins to the new OT (4.3.4), but the AEM Sites output is not working. The files are processed properly by the DITA-OT, but are not getting handed over to Guides to create the site. I notice differences in the log output when publishing with different DITA-OT versions. I need a few hints on how to get the job-helper.xsl working in the newer DITA-OT. Working DITA-OT:copy-flag-check:copy-flag:[job-helper] Processing /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/.job.xml to /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/flagimage.list[job-helper] Loading stylesheet /opt/aem/launcher/profiles/ditaot--3922c171-076c-7dd5-4b4b-9b4f895be1bd/DITA-OT/plugins/org.dita.base/xsl/job-helper.xsl New DITA-OT:copy-flag-check: copy-flag: Thanks,-Huntley

I have created a custom property and added it to the file properties (Metadata Schema Form Editor)The custom property list was added to /libs/fmdita/config/metadataListThis made the list available in the Map Console > Advanced > File Properties dropdown.I selected each of the property from the dropdown and generated an output.However, this selection does not seem to have any impact on the metadata that is available in the output. The list is simply not picked up! Can you help me understand the behaviour? And also, help me with the any configuration that needs to be set to get the custom metadata tags propagated to the output? 

I am exploring native PDF publishing with AEM. Is there a way to modify the content using XSLT before the PDF is created? Or before the intermediate HTML is created? Thank you.

 When clicking the 3 dots in the repository I have the option to download the topic as a PDF. Where are the settings for this option and where in the DAM does the generated PDF get saved? 

I want to use conkeyref to add values for elements in the prolog, for eample, prodname or category. I have created the required keys and bound it to the map/topic. I am able to add the conkeyref in the content of the topic, say within a <p> tag, but not with the Prolog. The key list is displayed, but upon selection of a key, the Update button in the dialog box is displayed. So, I used the source mode, and added the conkeyref. It picks up as conkeyref within the prodname or category is DITA valid.  In short, here is the observed behavior:The Attributes panel in Web Editor does not allow updating conkeyref on elements inside <prolog>.Even using “Insert → Reuse Content” or moving the conkeyref to a dedicated attribute on <prodinfo> does not enable the Update button in this context.Is there a configuration that I am missing? OR is this an out-of-the-box behavior in AEM Guides. There’s no configuration to get the conkeyref working for Prolog from t

I have created a subject schema; here is the sample code:  <subjectScheme><title>Subject Schema Definition</title><!-- 1) Permissions (for prolog@view) --><subjectdef keys="permissions"><subjectdef keys="perm_internalonly"><topicmeta><navtitle>InternalOnly</navtitle><shortdesc>Only visible to internal staff</shortdesc></topicmeta></subjectdef><subjectdef keys="perm_lix_experiment"><topicmeta><navtitle>LIX_experiment</navtitle><shortdesc>Experimental LIX audience</shortdesc></topicmeta></subjectdef><subjectdef keys="perm_lix_control"><topicmeta><navtitle>LIX_control</navtitle><shortdesc>Control group for LIX experiments</shortdesc></topicmeta></subjectdef></subjectdef><enumerationdef><!-- bind to prolog@view --><elementdef name="prolog"></elementdef><attributedef name="view

I published a DITA map using the AEM Sites output preset in AEM Guides. However:The navigation panel is missing in the generated output.The links that are visible in the generated output are not rendered on the published page. Kindly advise. Thanks

I need to be able to assess the different types of risk associated with our documentation. Think things like Business Risk, Reputational Risk, Compliance Risk, Operational Risk, Country Risk, etc. Currently we have several risk-related attributes that are used to calculate a risk rating.  What would be the best way to solve for this in Guides? I was thinking using tags for all of the dita objects (topics, maps, etc.) could cover the requirement of what type of risk, but I also need to be able to calculate a risk rating based on that data. Is using tags even the right approach? How could we use Guides for calculations like this? Thank you for your help.

When I work on the watermark processing test in the following codes: Document mergedDoc = mock(Document.class);Document mockOutDoc = mock(Document.class);Document ddxDocMock = mock(Document.class); based on the following pom.xml: <!-- Testing --><dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter</artifactId> <version>5.10.0</version> <scope>test</scope></dependency><dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-commons</artifactId> <version>1.10.0</version> <scope>test</scope></dependency><dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-launcher</artifactId> <scope>test</scope></dependency><dependency> <groupId>org.mockito</groupId> <artifactId>mockito-co

The last time I looked, the only instructions I found just said to download the ZIP file from the CRXDE, make changes, and reupload the ZIP file. There were no instructions on how to pick an output option from within the list of outputs, not how to copy the output files into a folder (similar to how the Native PDF Publishing does it) so that you can make incremental changes to the default outputs until you got to what you wanted, etc. For example, I am going to need to generate a tri-pane Windows help file eventually. I know the DITA-OT has such an output because we used it in SDL. Do any instructions exist to help me implement such an output within AEM Guides? And whatever happened to that default ePub output that never worked? It is still listed in the Output Presets in the Folder Profiles, but seems to have disappeared from the selectable default outputs.

Is it expected behavior that if we insert an image from outside the UUID Guides repository (from the AEM/Marketing side of the repository) and apply a condition to that image, that the PDF generation fails? If we do not apply the condition, PDF generation (Native PDF Publishing) works fine. The PDF generation only fails if we apply a condition to the image. (We're trying to consolidate duplicate images between AEM and AEM Guides.) Thanks. AEM 6.5.21 (on-prem installation (21 Dec 2024)AEM Guides v4.6 (UUID, on-prem installation (21 Dec 2024)

I have two question I'm hoping someone can help, thank you in advance. 1. How do I request to update to the latest license version. We are running version 6.5.22 ( will upgrade to 6.5.23) but the product displays 6.2.0. We need to have 6.5.23. Please see attached screen shot. 2. How to I request entitlement to open a ticket for future support.