Adobe Experience Manager Guides

Hi All,   We are pleased to announce that the 4.0 Release for the XML Documentation Solution has been marked GM. The build has been certified with AEM 6.5 SP9, SP10 and SP11 and will be certified with SP11 in a couple of weeks. Please find the other relevant information below:   Compatibility matrix: Oxygen compatibility matrix XML Documentation Release Oxygen Connector - win Oxygen Connector - mac Open in Oxygen Button 4.0 Non UUID 1.6.8Link 1.6.8Link 1.5Link 4.0 UUID 2.3.8Link 2.3.8Link 2.2Link   FM/FMPS compatibility matrix XML Documentation Release FMPS 2020 (Publishing) FMPS 2019 (Publishing) FM2020 (Authoring) FM2019 (Authoring) 4.0 Non-UUID 2020.2 onwards* 2019 2020.3 onwards 2019.8 (latest update) 4.0 UUID 2020.2 onwards* Not compatible Not compatible Not compatible *Also supports publishing with baselines and conditions created in AEM   Download link: The build has been uploaded on t

The DITAMAP loads the topic references in the DITAMAP dashboard very slowly, sometimes it hangs when there are a lot of topic references.We have segregated by creating smaller DITAMAP's and referencing those into the parent DITAMAP, but still, some of the content has a lot of articles where it fails to load the topic references and hangs frequently.Is there any recommendation on how many topic references can a ditamap have? Also, is there any recommended limitation to generating a website with such huge content or creating pages at individual ditamap's is a better suggestion? Appreciate your help in advance! Thanks,Sudheer

Documentation indicates that the relationship tables works with the topics/concepts/tasks, I am trying to check, if there is any option that we can use the relationship tables with the regular assests like pdf/word assets in the DAM along with other topics.  My scenario is as below:Topic 1 is having a relationship with Topic 4 and Topic5 and as well as can be linked to a DAM asset like PDF documents, once the AEM webiste is created, expecting the relationship nodes to be created for both Topic 4, 5 and assets linked in the relationship table. Is this possible? Appreciate your help in advance! 

AEM Instance:AEM 6.5 + SP7 + SP8 + XML Add On v3.8Query:We have a requirement to get the additional attributes (format, topic, chunk) added to the auto generated ditamap (from an uploaded index.html). While I was able to get these to reflect by making changes directly to /etc/fmdita/html2dita/toc2map.xsl. What would be the right approach to override this file? I tried an override at  /apps/fmdita/config/html2dita/toc2map_extended.xsl but that didn't quite work. 

3.8.5  Release for the XML Documentation Solution has been marked GM. Certified AEM VersionsNon UUIDAEM 6.5 SP9 and SP8AEM 6.4 SP8AEM 6.3 SP3UUIDAEM 6.5 SP9 and SP8The build has been uploaded on the software distribution portal and can be downloaded from one of the below links: Non -UUID-AEM 6.5 XML 3.8.5  - Download linkAEM 6.4 XML 3.8.5  - Download linkAEM 6.3 XML 3.8.5  - Download link UUID AEM 6.5 XML 3.8.5  - Download link Important links -The latest Non-UUID user guide for 3.8.5 is available here  .The latest  UUID user guide for 3.8.5 is available hereThe Release Notes are publicly available here . 

Use this thread to ask any questions related to the "Getting Started with XML Documentation" course on Experience League: https://experienceleague.adobe.com/?recommended=ExperienceManager-U-1-2021.xmldocs   Experts are monitoring this thread to ensure your questions are answered.

Hi Team,Our requirement is to generate pdf technical documents with part of content (for example product name) to be dynamic with rest of the content being same for all products. Is there a way to pass product name as a parameter while generating pdf output for a ditamap? If yes, can you please point me to a resource that I can refer. cc: @divrajsingh @tg_explorer ThanksSrikanth

I am trying to wrap any <table> elements within an <ol> or <ul> element with an <li> element. I am not having much success. I tried to copy the OOTB template and apply it to my h2d_extended.xsl, but I am not seeing my results. Here is my code from my h2d_extended.xsl file. Any help would be appreciated. For context, I am not seeing the wrapping <li> or the added <p>hello world</p>. AEM Instance:AEM 6.5 + SP7 + SP8 + XML Add On v3.8  <!-- Table inside of ol or ul --> <xsl:template match="ol/table|ul/table" mode="convert-to-cals" priority="9"> <xsl:variable name="num-cols"> <xsl:choose> <xsl:when test=".//col"> <!-- take col definitions --> <xsl:value-of select="count(.//col[not(@colspan)]) + sum(.//col/@colspan)"/> </xsl:when> <xsl:when test="./thead"> <!-- take first ro

Issue:Each time I define a table of content in an index.html  and try a HTML document migration it ends up creating a topic .dita instead of the expected .ditamap .AEM Instance:AEM 6.5 + SP7 + SP8 + XML Add On v3.8Issue Description:Followed the steps from Migrate XHTML documents section of the document https://helpx.adobe.com/content/dam/help/en/xml-documentation-solution/3-8/XML-Documentation-for-Adobe-Experience-Manager_Installation-Configuration-Guide_EN.pdf. According to the docs here, to generate the ditamap you need to include the index.html inside a zip file, which includes links to the other files. Also, define the <ul> and <li> tags with attributes as per recommendation.However, the dita file that finally gets created from the index.html is a DITA topic with an extension of .dita.

Issue/Query:Why does XML Add on v3.8 not support DITA 1.3 base element topic/div? For a migrated HTML document, the target topic .dita does not have any <div> tags.AEM Instance:AEM 6.5 + SP7 + SP8 + XML Add On v3.8Issue Description:Followed the steps from Migrate XHTML documents section of the document Installation and Configuration Guide The .dita file that gets created after the import is stripped off of any and every <div> tags. Confirmed from the h2d.xsl that this is indeed the case.<!-- divs: if we can base transform on a class, do so. --><!-- generic divs will fall through with no associated transform --><xsl:template match="div"><xsl:template match="div"> <xsl:apply-templates select="*|text()|comment()"/></xsl:template>  Is there a planned/available hotfix to fix this issue?@divrajsingh  

Hi, we are planning on extending the UI of AEM, especially in the XML Documentation area.We want to show additional UI elements in the sidebar. Can you please let me know, which APIs / Extension Points exist to achieve this? Thanks,Daniel

The toolbar in web-editor is completely customizable, there are many customizations that you can achieve, few use cases would be : Add/Remove toolbar options. Examples : Add a button to make the text bold or remove the insert multimedia option from the toolbar as it is not used frequently. Add a custom button in toolbar to define a custom action. Customize toolbar for map and topic separately. The XML Documentation Solution provides an easy way to customize the web editor toolbar. Below are the high level things that would help in customization: There is a ui_config.json file which has the configuration for the toolbar icons. The default one can be downloaded from 'Global Profile' under Tools-->XML Documentation-->Folder Profile-->Global Profile-->XML Editor Configuration. You can customize the toolbar for map and topic separately (also edit and preview mode). For example - All DITAMap specific configurations can be found with label as 'DitamapEdit'. Refer below co

Problem Statement: Are you facing issue on author instance where preview of DITA asset is not rendering correctly and this happens on asset details page ? Do you see the html encoding rather than actual page UI - Refer the the screenshot below.     Precondition: Do you have dispatcher set up on your author instance? If yes, the below solution can help you in resolving this issue.    Remedy: It could be because of the missing configuration. You should need to enable the mime type for DITA files.  Here are the additional details:   Ditamap and Dita topics shown in Assets UI have to be rendered with Content-Type “text/html”. So to have this work correctly in case a Dispatcher is setup in front of Author, please do following: Connect server via ssh and browse to httpd.conf and check the path for file “mime.types” file (it could be in /etc/mime.types or /conf/mime.types) Edit mime.types file and Search for “text/html” the default value string for this w

AEM creates additional version of a media assets when you revert between different versions of the asset. This is functionality as design, as the system: expects that the image version that is currently active may have some work in progress changes and may require saving those before moving to another version so it creates a branch version before moving to the selected version   In case this behavior is not desired, you have following options: Option 1: update the “XML Writeback Process” step of “DAM Metadata Writeback” workflow to turn off version creation – refer [1]. Use this option if you don't need the version creation only, but do need other metadata writeback features Option 2: Disable the launcher for workflow “DAM Metadata Writeback”, refer [2]. With this option the metadata writeback is turned off, use this option in case none of the features of writeback are required to know more on why this workflow is required refer this link and to

Easiest way is to make use of translation=no attribute. Authors can insert the additional attribute as 'translation=no' on the paragraphs that they do not want to translate. The translation vendor needs to be informed and they can do configuration at their end to ignore the text with this attribute. The OOTB machine translation (with trial Microsoft Translation connector) showcase the same behavior. Here are few screenshots and steps that would help in better understanding:  Testing with Microsoft Translation : if you define translate=no attribute at paragraph level then it doesn’t translate the complete paragraph. This attribute can be defined at any element and the content inside that element will not be translated. Example : Source Content   Translated Content in Spanish  

Hello Team, I am currently working on how to customize bookmap metadata elements using AEM, I am trying to append/insert user given template form data to book map metadata elements eg:<bookpartno>MN-1234-56</bookpartno> etc. Please find the below mentioned requirement and the image file for better understanding of the use case: Existing functionality : In the Assets Console,Whenever an author creates a DITA Topic or Map using the OOTB DITA templates,the user given template form value of Title field,gets automatically inserted to the <title></title>tag and the title is rendered on the web editor. Analysis on OOTB Functionality,from where this title is being fetched:The value of the title attribute is getting saved in the XML original rendition when the asset is created for the very first time and is always being read from there, the xml original rendition like [1] Below is the analysis on the backend process that happens while creating DI

My current query with predicate type=cq:Page does not finds property from subNode but only finds till node level propNode / jcr:content / comp-par / component / section / propNode / subNodeCurrentQuery:-------------------fulltext=Search Termgroup.p.or=truegroup.1_path=/content/proj/sub/usgroup.1_group.type=cq:Pagegroup.2_path=/content/dam/proj/sub/usgroup.2_group.type=dam:AssetBut when i remove the "group.1_group.type=cq:Page" then below fulltext query looks under entire depth and fetch all nodes containing the termUpdatedQuery:-------------------fulltext=Search Termgroup.p.or=truegroup.1_path=/content/proj/sub/usgroup.2_path=/content/dam/proj/sub/usgroup.2_group.type=dam:AssetWith this nodes containing search term are returned while we expect the cq:page to be returned as in previous query.Do we know what controls the depth for fulltext search with type=cq:Page. fulltext query without the type looks under entire depth.And how can we get only cq:Page in se

I have a topic that is reused in about 200 sites. I want to update the topic, and then generate and publish in all the sites. Any ideas on how to do this?

The steps to add a custom DITA-OT are documented in the section "Use custom DITA-OT plug-ins" of Installation and Configuration Guide   On a high level the steps are: Get the basic DITA-OT If you want to obtain copy of out-of-the-box DITA-OT from XML Documentation, download it from path "/etc/fmdita/dita_resources/DITA-OT.zip" If you want to obtain a different version then you can download from dita-ot repo Make changes into DITA-OT like adding new plugin, or customizing existing plugins (refer example in related links section below) Upload DITA-OT.zip received to /apps/<project-folder>/dita_resources (create a custom project folder is a recommended approach) Add DITA Profile through Tools > Guides > DITA Profiles (use the DITA-OT path where the custom DITA-OT is uploaded, refer screenshot below)       More Reading Customizing DITA-OT plugin samples

We are pleased to announce that the 3.8 Release for the XML Documentation Solution has been marked GA.   The 3.8 release has been certified on: AEM 6.5 SP8 and SP7 AEM 6.4 SP8 and SP7 AEM 6.3 SP3   The build has been uploaded on the software distribution portal and can be downloaded from one of the below links:   AEM 6.5 XML 3.8  – https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/software-distribution/en/details.html/content/dam/aem/public/aemdox/3-8/com.adobe.fmdita-6.5-3.8.166.zip   AEM 6.4 XML 3.8  – https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/software-distribution/en/details.html/content/dam/aem/public/aemdox/3-8/com.adobe.fmdita-6.4-3.8.166.zip   AEM 6.3 XML 3.8  – https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/software-distribution/en/details.html/content/dam/aem/public/aemdox/3-8/

We are closing the service RR in the finally block still we get the unclosed RR in logs for below method.This post has additional logic as a workaround to manually close the ResourceResolver after processing the query result. Ques1) Do I need to do this extra workaround code for my method below.Please find method below with additional workaround, currently stuck with converting node to a resource. Ques2) Do we know how we can convert node to a resource  Resource closeableResource = adapterManager.getAdapter(closeableNode, Resource.class); // gives null resourceSample code from method below:import javax.jcr.query.Query; import javax.jcr.query.QueryResult;ResourceResolver resolver = null;try { resolver = getResourceResolver(ServiceUser.READ_ONLY_SERVICE.toString());final Session session = resolver.adaptTo(Session.class);final Query query = session.getWorkspace().getQueryManager().createQuery("/jcr:root" + nodePath + "/element(*,nt:base)[sling:resourceType='p

Currently, AEM lists the ditatopic and ditamap version history with the first version at the top and the last version at the bottom.  When a ditatopic or map has a lot of versions, you have to scroll way down to find the lastest version.  Would prefer the order to be reversed so that the most recent version appears at the top.

Hi all, I am using aem 6.5I have a requirement for converting aem page nodes to json.Previously I used jsonItemWriter.dump method which converts data directly.But this method is deprecated.And second thing is in multifield we get data as item0,item1 in jsonobject format.But my requirement is to convert this multifield to JsonArray. Kindly guide for same

Hello, I don't think there's a way to post an idea to this sub forum yet, but my team has the following feature request: Request for Feature Enhancement (RFE) Summary:The Search and Replace feature only allows writers to search and replace content in the author mode. However, this does not resolve use cases where XML tags must be replaced across multiple files. Use-case:The writer needs to replace a product name, which is in plain text, with a <keyword>. Current/Experienced Behavior:Search and Replace only works in author mode. Improved/Expected Behavior:Search and Replace can work in either author mode or source mode. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name:Broadcom Inc. Screenshot (if applicable): Code package (if applicable):  

3.8 Release for the XML Documentation Solution will be the last supported version for AEM 6.3 and AEM 6.4. Any release post this would be only supported on AEM 6.5. What does this mean? This means that All new features on the product will be available only for AEM 6.5 and cloud services No feature will be backported to AEM 6.3 or AEM 6.4 You will continue to receive service packs for AEM DoX on AEM 6.3 and 6.4 which would be some bug fixes for next 6 months Any bug (no feature) which is a blocker or a critical for your implementation will be prioritized for an upcoming service pack What do we suggest? Please plan the move to AEM 6.5 at the earliest