Advanced Document Templating

Overview

This plugins allows to generate DOCX files from a DOCX template and an XML data model from Appian. It also allows to convert a DOCX into PDF through an opensource (with limited capabilities) library.

Key Features & Functionality

  • Smart Service to Generate a DOCX from a DOCX Template and an XML data model
  • Smart Service to convert DOCX to PDF through an opensource (with limited capabilities) library
Anonymous
  • Hi,

    when we generate a word document with an image example:

    {logo: CONS!APP_IMAGE} works perfectly, but when I have more than one image in the template.

    For example logo2 and I call the smart service as follows {logo: CONS!APP_IMAGE, logo2: CON!APP_IMAGE2} I get the following error:

    freemarker.core.NonSequenceOrCollectionException: The value you try to list is an extended_hash+string (fr.opensagres.xdocreport.document.images.ByteArrayImageProvider wrapped into f.e.b.StringModel), thus you must specify two loop variables after the "as"; one for the key, and another for the value, like <#... as k, v>). ---- FTL stack trace ("~" means nesting-related): - Failed at: #list logo as logo [in template "fr.opensagres.xdocreport.document.docx.DocxReport@7f2dbfc!word/document.xml" at line 4, column 6773]

    CV list logo as logo2.docx

    ---- Plugin: Advanced Document Templating Version: 1.1.0 Smart Service: DOCX From Dynamic Template

  • Hi,
    I'm using the "DOCX From Dynamic Template" component from your plugin and I would like to know if is there any way to attach other file type files than images please ?
    (example : pdf, docx,... inside the main generated docx file)

  • PDF from DOCX smart service is unable to convert foreign language Japanese or Chinese using the document generated from the DOCX from Dynamic Template smart service. 

    We have a requirement to collect some application data and to convert to pdf. Our data has Japanese, Chinese and multiple languages. The DOCX from Dynamic Template is successfully generating documents in given languages but when we use the PDF from DOCX / PDF from single DOCX (with fonts) / PDF from multiple DOCX smart services, either other that english characters are skipped or # is used in place. We have updated both Advanced Document Templating and Dynamic Document Generator to the latest version.

    Please can you help with how to get PDF from DOCX that has multiple languages.

  • Hi mandark52, We you able to solve this issue?

  • v1.1.0 Release Notes
    • Updated API usage and license file

  • Plugin: AdvancedDocumentTemplating Version is: 1.0.7
    This plugin is present in Appian Version 21.4.1205.0, we are planning to upgrade Appian version to 23.2 will this plugin with Version: 1.0.7 is supported or need to install any specific version?

  • Hello!

    I've been using the plugin, and everything is fine, but this time, I need a table to be displayed only when it contains information. I've tried using an IF statement within Word, but it seems that when the Appian process model is executed, it doesn't recognize the IF and displays the table.

    Code WORD: 

    { IF "{ MERGEFIELD ${doc.project.showTable}  \* MERGEFORMAT }" = "true" "Table" ""}

  • Leo, were you able to downgrade?

  • I have raised this issue with Appian Support, who advised me to log this here to inform the developer(s) so that a fix can be produced.

    After upgrading to the latest version of this plugin (1.0.12), we found that PDF documents produced by the plugin were being generated with text that overlaps other text fields, making the document unreadable.  We downgraded back to the previous version of the plugin (1.0.7) and found that this was no longer happening, therefore we can only assume that this is an issue within the latest plugin version.  Could you please investigate and resolve?

    Many thanks,
    Jeff

  • In the 23.2 release, Appian introduced modernized file management APIs that offer a cleaner abstraction layer for easier file handling within Appian. We simultaneously announced that we are deprecating some older APIs. We are aware of the utilization of deprecated APIs within some AppMarket plug-ins that work with documents. As part of our commitment to ensuring compatibility, we anticipate all Appian-authored plug-ins currently using deprecated APIs to be updated for API compatibility by the 24.1 General Availability (GA) release. We also proactively work with Partner plug-in authors to ensure all AppMarket plug-ins have optimal performance and functionality. 

    If you have any questions or require AppMarket assistance, please don't hesitate to reach out by sending an email to appmarket@appian.com.