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
Hello,
Did you find a solution for this issue?
Hi gents,
We are trying to use the PDF from Single DOCX (with Fonts) Smart Service to cater to the word document's Arabic language.
Even with different font files, we weren't successful; the Arabic sections only show hash symbols instead of the actual text. We are not sure what the issue is; we are using the font files specified in the template document from Windows and attaching them to the smart service.
Can you please provide support to check which Arabic font files are supported by the smart service?
Thanks,
Jean
As a follow up...do you know if there are any special characters or formatting the conversion might not like?
I have upgraded our DEV environment to version 2.1.0. I was hoping the new version would help with an issue we currently have in all environments. We are currently on version 23.1. We are using the PDF from Multiple DOCX (no fonts) and it attempts to convert the file but on the output there is no file, we are getting this error:
org.docx4j.openpackaging.exceptions.Docx4JException: Exception exporting package
I'm using docxncolumntable to generate a table for a word doc. The table that gets created is too narrow to fit the page and requires manual readjustment of the table.
The parameters for the function do not appear in the help screen. I checked the documentation provided with the plug in but there's no mention of the parameters used by docxncolumntable. Is there a way to get a list of the parameters supported by this function in order to adjust the table?
Thank you.
After utilizing OWASP dependency-check, we have identified the following vulnerabilities (outlined below). Are there any plans in place to mitigate these CVEs?
I can confirm at least in version 2.0.4 Arabic Letters can be displayed, if you provide a proper Font Document as an input