Overview
Contains multiple Smart Services and Functions for interacting with PDF Documents.
Key Features & Functionality
Smart Services:
Functions:
When you say "able to edit", what exactly does that mean? Are you talking about fillable fields still being fillable when opened normally (which i had thought "flatten" might take care of), or do you mean like you're able to open it in Adobe Acrobat (the full version with editing capabilities) and still switch to "Edit" mode? If it's the second one, I'm not sure what the solution is, though you might need to look into a way to LOCK pdf's.
Update: this deployment issue has now been fixed, per the comment below by Michael C. I've confirmed in my own environment that it allows the upgrade now.
Michael Chirlin fyi:
Image Compression smart service is working as normal, both before and after updating PDF Tools to 2.8.2
PDF Tools 2.8.2 still fails to produce usable files when running the PDF to Image(s) smart service -- the output continues to be an unnumbered array of output files with zero file size. Are you saying this should be fixed by another environment restart? I want to make sure before asking Support to restart us again, since the last restart (on 2.8.1) didn't actually fix it.
Appian Support reverted me back to 2.8.1 last night then performed a restart after I was done with work for the day - testing out the PDF to Image smart service (back in the 2.8.1 version) this morning, it still has the "generates array of blank image files" issue.
I will now:
Have tried with "Fill PDF" with the parameter "flatten" as true. But no luck able to edit the PDF. Even tried smart service "Readonly PDF Converter" but issue still persists.
Fixed now, should be able to deploy 2.8.2 from the admin console. Let me know if you still have errors with the other smart services after a restart and I'll take a look.
Not sure, but I've gotten around this before by either using "Fill PDF" with the "flatten" property set to true, and/or the "Merge PDF" node and just passing in a single source PDF (and taking the output which is at least somewhat flattened and maybe read-only).
happening to me now too. let me know if you come up with a fix (it seems like there's a possibility a site restart would do it, at least since that seems to be the fix for some other recent issues, but not sure.)
Hold off on deploying this, it seems to be erroring from the admin console. I have a ticket looking into it.
ok, thanks - will a site restart also take care of the "plugin failed to deploy" error i'm now getting for 2.8.2? (it happens whether i'm trying to update from 2.8.1 or after reverting to 2.5.2)