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
Function: xsltransform - Transform source XML using XSL Transform
We are experiencing an issue when using this plugin to generate DOCX where blank pages are being inserted after large amounts of text around grids. Is this the expected behavior for this plugin?
We are also experiencing this issue. It looks related to the newer versions of Word. We found that if we simply save an existing document that had no prior issues with the newer version of word (after version 2407) and then reupload that we get the issue.
It also seems like it only affects the first template being merged. If the first template being merged was saved with a newer version of word then the document will produce this error. If that newer template is not the first in the list and the first template was saved with the older version of word, then the final document will not be corrupted
Is there an example HTML document I can use to test the HTML to PDF?
I tried below but receive a null pointer exception (using version compatible for pre-23.2):
<html> <body> <table> <tr> <td>Val1</td> <td>Val2</td> <td>Val2</td> </tr> </table> </body></html>
I am also seeing this pop up and will not be able to leverage the plugin even though it appears to be doing what it should after I click through it. Any assistance would be greatly appreciated.
Appian AppMarket
Support
Appian Solutions
Hi Appian Support Team,We are also getting same pop up while we generated documents by using DOCX Merge smart service.
Getting below error while trying to open downloaded document from Appian after merging with smart service DOCX Merge:
Error:
Word found unreadable content in "test 1.docx". Do you want to recover the contents of this document? If you trust the source of this document, click Yes.DOCX Merge smart service is working correctly, before merge we are able to download and open the single generated word doc without pop up. After merge of documents we are able to download it but while opening getting the pop up error. Below is the screenshot for reference:
Please let us know if any fix available for this pop up issue. Let us know for more details. Regards,Sandeep
I had the same issue when I used the PDF from single DOCX with Fonts smart service where Japanese and Chinese characters would return hashtags. I ended up getting the characters to show by using the Microsoft Yahwei font in my docX template and including the MS Yahwei font file in the Fonts parameter. I don't have experience with the HTML to PDF smart service but you could consider switching to the PDF from single DOCX with Fonts smart service or there might be a way to configure fonts with the HTML to PDF within your html template
We have an issue converting Japanese characters using the module that converts HTML to PDF. All of the Japanese characters are converted to "####################################". I see that the same issue was reported by another user 2 months ago for the conversion from DOCX.
HI,
We are using this plugin to generate word documents. there is no issue with generating the document, after generating the document we are getting popup message every time so business users reporting this issue. could you please help us to get rid of this issue. please find below screenshot for your reference.
Hi, have you tried passing a font document that supports both English and Japanese with pdf from docx from single docx with fonts? Something like simsun or ms ya hei?
We are having a weird issue where we are using this plugin to convert docx to PDF. The plugin is working fine in lower environments but making the text bold in the converted PDF in the production environment. We tried deleting and reinstalling the plugin but nothing seems to work. Anyone has any idea how to fix it?