Overview
Version 1.0.0 - Accepts inline and internal styles and also adds images in the PDF if they are publicly hosted. Based on content, multiple pages will be created in the PDF. The Smart Service will accept HTML files with properly closed tags including <br> and <img> tags otherwise the node will be errored out.
Version 2.0.0 - Everything with Version 1.0.0 and ability to generate PDF from HTML with landscape orientation.
Key Features & Functionality
Inputs
Outputs
HiAndrei Iordache,
Thanks for reaching out. We will look into this behavior and provide an update.
Regards,
Praveen Santhosh.
Hello,The new version of this plugin now contains a timeout but there are cases where it still fails and the conversion thread does not appear to be terminated correctly when the timeout is reached and continues running indefinitely blocking the engine. Unblocking the thread can be solved only with the restart of the application server.
Could you please check this issue?
If anyone else has this issues, the fix is to use data-docid instead of appianDocId, until a fix is released.
We are having issues with images not displaying in the pdf when using the smart service "HTML to PDF (Page Number and Custom Fonts)".
The same images display fine when using "HTML to PDF" smart service.
Hi Team,
Unable to display images in the PDF, we tried new version but it's not working.
Hi safeth.habibija.personifyhealth ,
This issue has been addressed in V3.0.1 of the plugin which is currently in review.
Hi team,
we also have an issue with the PDF conversion once we updated the plugin from 2.1.12 to 3.0.0.
The document generated is displayed as empty, even the file is not 0 size.
We also utilize a font document and an HTML template with an included image.
Hi Vuram team,
After upgrading from version 2.1.1 to version 3.0.0, we are observing an issue with generating PDFs with the plugin with the following conditions:
1) A font document is passed to the smart service
2) An image is included in the HTML
Version 2.1.1 of the plugin supports this, so this appears to be a regression. Are you able to check if a bug was introduced in the latest version and provide a fix? I'm happy to provide a simple HTML file that we're using to reproduce the issue.