Expectation is if Native Publishing can print table of contents (toc) automatically like DITA-OT option does. Currently native publishing doesn't have that feature.

@AswiniLakshminarayanan  topicmeta metadata works when topicmeta tags are directly child nodes put under map. Something like this.   <map product="Sample Product"> <topicmeta >  <keywords>     <keyword>Product Keyword 1234</keyword>  </keywords></topicmeta> </map>   It is not working if it is under ...

Using AEM Guides on Cloud AEM 1. Created a sample ditamap 2. Tried to generate a PDF using a sample preset created having a Hi-Tech OOTB template did not create a PDF with TOC   Does it need more settings? Or this is an issue?

As you have already confirmed it works fine in local publisher (it means you have enabled post method in servlet class and felix config also). I believe your servlet path is /bin/pdf/view and in filters.any it is allowing only GET method in your screenshot. Just allow post method for the same path.

@AswiniLakshminarayanan  Thank you for the explanation. A few questions around this   1. We are not using bookmap where we can define bookmeta tags.  Can we using keydef tags keyword and map attribute 'product' value as well in the plain map (not bookmap)? If yes what is the expression to access the...

As explained here https://experienceleague.adobe.com/docs/experience-manager-guides-learn/tutorials/configuring/config-native-pdf-publish/design-page-layout.html?lang=en#add-fields-metadata it is mentioned we can also add metadata information as variables or fields in your page layout. This metadata...

@VivekKumar  1. First question: Its good to hear the all the map dashboard features are being added to current side where native PDF publishing is available. But currently native publishing presets are available only for that map. It is not feasible solution for authors to create presets for every m...

How do we use the metadata it in Native PDF publishing? Provide example with a code syntax. This links https://experienceleague.adobe.com/docs/experience-manager-guides-learn/tutorials/configuring/config-native-pdf-publish/design-page-layout.html?lang=en#add-fields-metadata talks about how to create...

Why this issue happens custom pages? In we-retail pages it works, because cq.shared library is included as part of the page itself in the one of the scripts for ex: (/libs/wcm/foundation/components/basicpage/v1/basicpage/basicpage.html). To fix the issue, copy the same the below lines code in any of...