Overview
This version is for Appian 22.3 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 22.2 and lower version in the folder pre-22.3
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
Hello, we're attempting to use the "Word Doc from Template" Smart Service on a Merged document, but the smart service only replaces the placeholder from the first document that was merged.
For example if we have 3 docs with placeholders, merge them, then run the Word Doc from Template Smart Service the output document will only have the placeholders in the content from the first document replaced in the final merged version. We've checked all of the formatting of the placeholders and everything looks correct.
Any idea what might be causing this?
If Apache FOP is running in a so-called "headless" environment then SVG rendering will fail. That is the problem I bet.
Hello, I try to use "PDF from HTML" smart service ,but it crop the html data in PDF, And doesn't show all table as photo
Can help me please?
Hello, per Appian Technical Support, the 22.3 Upgrade may impact custom plug-ins that use javax.mail. After doing a quick scan it appears that this plug-in does use this library.
Will an updated version of this plugin be provided to address this issue?
Hi, Has anyone been able to resolve the issue with Arabic fonts not working? If so, can you please share the resolution?
I've run apache fop 2.5 locally against my xsl-fo and xml and I get my pdf with an embedded svg image but using the same xsl-fo and xml using Appian and this plugin results in a generic java error "An error occurred in executing an Activity Class." When will this bug be fixed so we can host svg embedded images?Also, is there a way to configure fop to not use strict-validation?
Hello, try to use PDF from Multiple DOCX (No Fonts) with version 1.9.1 we get the following error:
org.docx4j.openpackaging.exceptions.Docx4JException: Exception exporting package
Is there anything we can try out?
Hi, have you seen any update to this problem? Because we are seeing it in versione 1.9.1
Using "PDF from single DOCX with Fonts" for "Arial" font, the pdf is still using "Times New Roman" font even though I specify "Arial" in "Font Documents" in the smart service, can anyone please let me know if you were able to resolve this issue?