Dynamic Document Generator

Overview

This version is for Appian 23.2 and above. Cloud customers on a lower version of Appian that want to install this plugin should open a support case. Self-managed customers can find the latest jar for Appian 23.1 and lower version in the folder pre-23.2

Convert, merge and generate DOCX, PDF and XML files automatically in an Appian process

Key Features & Functionality

  • PDF from single DOCX with Fonts
    • Convert multiple DOCX files into a single PDF. Please note that the translation from DOCX to PDF is not always 1:1. The template may need to be tweaked or simplified to achieve the desired results.
  • PDF from DOCX without Fonts
    • Convert multiple DOCX files into a single PDF. Please note that the translation from DOCX to PDF is not always 1:1. The template may need to be tweaked or simplified to achieve the desired results. This will not support fonts.
  • PDF from XSL-FO Transformation
    • Uses XSLT to convert an XML to XSL-FO which is then converted to PDF
  • PDF from HTML
    • Converts an HTML document into a single page PDF.
  • PDF from HTML Transformation
    • Uses XSLT to convert an XML to HTML which is then converted to PDF
  • Text Doc from XSLT
    • Uses XSLT to convert an XML to a plain text document (such as HTML, another XML doc, etc).
  • DOCX from XHTML With Styling
    • Converts a valid XHTML file into a DOCX, allowing you to provide your own template file for style reference. Useful for creating dynamic documents that are editable
  • DOCX Merge
    • Merges one or more DOCX files together. If a header or footer exists in any document, they will be removed during the merge process.
    • A configurable separator can be specified: none, line break or page break

Function: xsltransform - Transform source XML using XSL Transform

Anonymous
  • Am currently using the PDF from Single DOCX (with Fonts) smart service of Dynamic Document Generator 1.8.5 versions on cloud Appian version 24.2, We have a requirement to increase indent (white space) before starting of the sentence. But this is not working during the conversion because the spaces are trimmed. Below is the image of word document and the converted PDF document for reference.

      

    Can you please guide me if am missing something to achieve the result?

    Thank you!

  • We have a requirement to convert a DOCX with Japanese characters. 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. 

    Thank you!

  • v2.2.2 Release Notes
    • Fixed issue with PDF From HTML smart service. Security patched commons-io library

  • I'm trying to use DOCX Merge smart service merge 2 or more DOCX files. When I run my process model, the smart service doesn't run into any exception or error and it runs successfully but the merged docx file will have only which is the first docx file. I can't find any alternative except the aspose licensed version. Can someone please help me with this? Thanks in advance.

  • Bullet points getting skip or replace with # when we use any "PDF from single DOCX with Fonts" or "PDF from DOCX without Fonts" . could you please help us in this.

  • v2.2.1 Release Notes
    • Applied security patch

  • Hello,

    We are using the DOCX from XHTML plugin to convert an XHTML file to a DOCX. The source XHTML file (which actually has a .html extension) contains the following html:

    <tr style="background-color:green">

    All the content from the entire HTML document is coming through as we would expect, including the content of the table, except for the background color of this <tr>. Background colors come through via <span> tags, but not via the <tr> tag. We also tried CSS in a <style> tag, but that didn't work either, nor is it a feasible solution for this purpose.

  • Hi all - 

    Our team uses the DOCX Merge and saves the final document to send out in an email (Send E-mail smart service) as an attachment. Some emails are not sending while some are. For both instances, there is no forced exception/error stopping the process models, and they go through the DOCX merge and process model that sends out the email fine. PauseOnError is set to True. For reports that are not sending, the merged file saves successfully into the folder as set in the SaveInFolder input, and there is no error message from the ErrorText output, however, the final document that should be saved into the NewDocumentCreated output is not saving. I assume this is why the email is not sending as well - but I am not sure about this, I am still researching.

    What are the exceptions that the error messages should catch? I am not sure how to solve this problem because there is no error message that presents. I am able to download and view the attachments that should send from the Folder.

  • Hi Team,

    Working on "HTML Doc from Template" smart service to generate a HTML page and "PDF from HTML" smart service to generate PDF, HTML to PDF conversion is working fine when there are few records but when I have tested for around 2500 records, server crashed and there were logs with message "server's heap running out of memory".

    Appian version is 23.4

    So, I went with another approach, where I will be splitting the data based on a category and generating multiple PDF's and merging them with "Merge PDF" smart service.

    Could you please let me know all the limitations related to smart services "PDF from HTML" smart service and "Merge PDF"


    Thank you
    Madhu

  • For the PDF from HTML smart service is there a known limit to the amount of data this node can handle? We are experience application server crashes when attempting to send approximately 2500 records worth of data to this node.