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
Parents
  • 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.

Comment
  • 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.

Children
No Data