Hi everyone, we are encountering an issue after updating the Dynamic Document Generator plugin to the latest version from AppMarket (from v2.2.2 to v3.0.3)
*******************Issue Summary: When generating a PDF using the “PDF from Single DOCX with Fonts” Smart Service, text formatting such as bold and italic is no longer applied in the resulting PDF.
Current Setup:- HTML Doc from Template Smart Service - HTML → DOCX via XHTML Smart Service - DOCX → PDF via PDF from Single DOCX with Fonts Smart Service - Fonts provided via constant as Appian Documents (Font folder includes Source Sans Pro (TTF and OTF))Observations: - The generated DOCX file correctly shows formatting (bold and italic) - Inspecting the DOCX XML confirms formatting tags: - <w:b/> for bold - <w:i/> for italic - However, the PDF output renders all text as regular (no bold/italic)Troubleshooting Performed We attempted the following with no success:1. Updated style rules and changed font family from Appian Open Sans to Source Sans Pro 2. Updated the Font Documents input of the “PDF from Single DOCX (with Fonts)” Smart Service - Used folder containing OTF files for Source Sans Pro 3. Updated the Template Document used in the “DOCX from XHTML” Smart Service - Switched to the most recent version created via Microsoft Word 4. Recreated both DOCX from XHTML and PDF from Single DOCX (with Fonts) nodes - Replicated configuration from original nodes 5. Previously tested: - Multiple fonts (Arial, Source Sans Pro) - TTF and OTF formats - Reduced font sets (regular, bold, italic, bold italic only) - Verified fonts are correctly referenced in DOCX (w:ascii="Arial" / Source Sans Pro) Key Finding The issue appears to occur specifically during the PDF rendering stage, as: - Formatting is preserved in DOCX - Formatting is lost only in PDF output
****************
Has anyone experienced this after updating the plugin?
Is there a new requirement for font mapping/configuration?Or is this a known regression in the latest version?
Discussion posts and replies are publicly visible
Looks like the issue is definitely in the PDF rendering step, not your pipeline—since DOCX keeps bold/italic correctly. After the upgrade, the Smart Service may not be mapping font variants (bold/italic) properly, even if the files are present. I’d double-check internal font names and how variants are linked.
Also, this kind of small formatting break can really affect the final experience—ran into a similar polish issue while working on Space Waves UI. Tiny details, big impact