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
Do you know why the iText library is no longer bundled with this plugin? The missing iText library has broken the 'DOCX from XHTML with Styling' Smart Service. Can this library be added back to this plugin like it was for version prior to 1.8.6? We have successfully fixed the broken smart service by creating a custom version of this plugin where the only change is adding iText 2.1.7. Additionally, we've had success with the latest version of OpenPDF (https://github.com/LibrePDF/OpenPDF) which should serve as a sufficient substitute for iText, assuming that iText was removed due to changes in it's licensing
Post upgrading to 21.4 we are getting errors during the startup of the Dynamic Document Generator Plugin. Does anyone have faced similar issues?
2022-04-15 15:12:04,009 [localhost-startStop-1] ERROR com.atlassian.plugin.manager.DefaultPluginManager - There was an error loading the descriptor 'TextDocFromXslt' of plugin 'DynamicDocumentGen'. Disabling.com.atlassian.plugin.PluginException: com.appiancorp.suiteapi.type.exceptions.InvalidTypeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: Unsupported type [Lcom.appiancorp.ps.xmlfo.types.XslParameter; (APNX-1-4047-000)
Hi Raza,
We are using the Docx from XHTML service under the latest version of this plug in, and as mentioned below we are receiving the following error message in the logs:
Exception in thread "ThreadPoolTaskExecutor-50668" java.lang.NoClassDefFoundError: com/lowagie/text/DocumentException
at org.docx4j.org.xhtmlrenderer.docx.DocxRenderer.<init>(DocxRenderer.java:160)
at org.docx4j.org.xhtmlrenderer.docx.DocxRenderer.<init>(DocxRenderer.java:85)
at org.docx4j.convert.in.xhtml.XHTMLImporterImpl.getRenderer(XHTMLImporterImpl.java:271)
at org.docx4j.convert.in.xhtml.XHTMLImporterImpl.convert(XHTMLImporterImpl.java:538)
at com.appiancorp.ps.xmlfo.ss.DocxFromXhtml.runSmartService(DocxFromXhtml.java:49)
Is there a patch for this issue?
Hi,
We have requirement for converting hebrew language DOCX Document to PDF Document.We have tried to convert using "PDF from Single DOCX (with Fonts)" Smart Service. But Hebrew Language content is replaced with ### symbol in created PDF Document using this smart service.So we created constant, added two hebrew ttf document ("NotoSansHebrew-VariableFont_wdth,wght.ttf","NotoSerifHebrew-VariableFont_wdth,wght.ttf") and added as Font Documents in that Smart Service.But still we got the same PDF document with replaced ### symbol.
Could you please suggest, what kind of font document we need to upload for hebrew language to get original Hebrew Language PDF Document?
Yes unfortunately, but it didn't seem to work
We are using the PDF from HTML smart service and are needing to show/hide some sections conditionally. However, it does not seem that the HTML style="display: none" is supported.
Do you know of any other possible ways to show/hide that is supported?Thanks in advance.
Have you tried the convert Docx to PDF smart service and provided the fonts as inputs?
Hi Raza
We are using the Appian version 21.3 and we have trouble converting DOCX and HTML to PDF when it contains Greek characters. They just appear like this ########. Is there a solution to that?
Hi Raza.mir,
We are using plugin version 1.8.6, where we encountered issue with smart service "DOCX from XHTML", this smart service is failing with below error. When i checked node duration it is almost running for 4 and half days.
"The amount of time allocated for the completion of an unattended activity was insufficient to allow the activity to complete."
FYI - Appian version - 21.2
The older version works as expected(1.8.2), could you please look into this.
Thanks