Overview
Contains multiple Smart Services and Functions for interacting with PDF Documents.
Key Features & Functionality
Smart Services:
Functions:
Hi,
I am getting below error when I use the getpdftext function.
An error occurred while evaluating expression: pdfText:getpdftext(pv!rulesforInclusionpdf) (Expression evaluation error at function 'getpdftext': Error: Header doesn't contain versioninfo) (Data Outputs)
PDF document referenced in the function is generated from docx using pdf from docx
Any help is much appreciated. Thanks!
Hi, thanks for the reply! Unless there is another way to check in Appian, if there is the PDF is formed correclty, exactly that could be a good behavior.... A null might be fine. A null should mean that the function could not get any fields from the PDF. If the function response is null, it means there is no metadata and should mean that something is going on with that PDF and it is invalid.
Hi mikel,tbh this will be hard to maintain properly. I mean we are talking for a reason about "corrupted PDF". And if you dont have a valid PDF, how can the function be working on a reasonable level as "PDF tool" function?What would be your expected behavior? No error?kind regards, Richard
Hi! We have a problem when we use getpdfflieds on a corrupted PDF. Sometimes our users upload this kind of PDF documents and we don't know how to control it. Would it be possible that this implementation exists in the current plugin and at least the function doesn't fail? It would be enough for us to throw a null. Thank you!
Common issue with .docx templates with fields which are being merged like the following in the final PDF conversion.
[SOLUTION] Ensure spacing is removed for all paragraphs:
[EXPLANATION] It appears that adding custom spacing throws off the PDF converter and merges fields in an unpredictable way, resort to using simple newline characters.
@naeemm3619 were you able to resolve this?
https://docs.appian.com/suite/help/23.3/Product_Release_History.html18.1 is not supported any more
hi, are you still on 18.1. in year 2023 ?
In the 23.2 release, Appian introduced modernized file management APIs that offer a cleaner abstraction layer for easier file handling within Appian. We simultaneously announced that we are deprecating some older APIs. We are aware of the utilization of deprecated APIs within some AppMarket plug-ins that work with documents. As part of our commitment to ensuring compatibility, we anticipate all Appian-authored plug-ins currently using deprecated APIs to be updated for API compatibility by the 24.1 General Availability (GA) release. We also proactively work with Partner plug-in authors to ensure all AppMarket plug-ins have optimal performance and functionality. If you have any questions or require AppMarket assistance, please don't hesitate to reach out by sending an email to appmarket@appian.com.
as we will have a setup with this plugin as key peace, i raised it with some appian folks :)