PDF Tools

I'm having an issue when using FillPDF to populate fields in a LiveCycle document.  First I need to offer kudos that it works at all - the LiveCycle file format is pestersome and in my experience has been hard to work with.

My issue is pretty straightforward: when I fill in a field in-process, and view the resulting document either in the Appian preview field, or previewed directly within Chrome, the filled-in value appears seemingly correctly.  But if I download the generated document and open in Adobe Reader, the field is apparently still empty.  If I open the file in a text editor, I'm able to find the value that had been inserted... but when I enter the value directly in Adobe Reader then save, the desired value shows up in additional places within the binary (again, viewed within a text editor).  I don't know what the exact issue is here, however it's preventing me from using Fill PDF to fulfill a use case of ours, which the older PDF from Template smart service fails at (in a worse way).  If anyone's able to offer some insight into this, I'd appreciate it.

I'm having an issue when using FillPDF to populate fields in a LiveCycle document.  First I need to offer kudos that it works at all - the LiveCycle file format is pestersome and in my experience has been hard to work with.

My issue is pretty straightforward: when I fill in a field in-process, and view the resulting document either in the Appian preview field, or previewed directly within Chrome, the filled-in value appears seemingly correctly.  But if I download the generated document and open in Adobe Reader, the field is apparently still empty.  If I open the file in a text editor, I'm able to find the value that had been inserted... but when I enter the value directly in Adobe Reader then save, the desired value shows up in additional places within the binary (again, viewed within a text editor).  I don't know what the exact issue is here, however it's preventing me from using Fill PDF to fulfill a use case of ours, which the older PDF from Template smart service fails at (in a worse way).  If anyone's able to offer some insight into this, I'd appreciate it.

sorry i never saw this reply before (community doesn't bother send notifications of general replies in these threads, for whatever reason) - the "pdf fields" parameter can just be passed a list of dictionary data where each dictionary has parameters named "name" and "value", where "name" will match the PDF fillable field's internal "name" parameter, and "value" is generally any text value. 

I agree the documentation for this plug-in is a little vague as to how that works, though you can get a good idea by looking at the definition for the "PdfField" data type on page 13 of the documentation PDF.

Michael Chirlin - thanks, any chance Appian might come up with a remedy for this issue on the plug-in side?

FYI i didn't see your reply initially since Community apparently doesn't want to notify me for basic replies here.

Hi Mike, 

Can you please tell me how do I configure fill PDF tool pluggin ? I need to create an editable form. Users will fill that pdf form with required values and submit. After submitting , we  can download that newly edited  pdf. 

We are using the PDFBox library to insert the fields into the PDF. 

You may be running into this issue:

stackoverflow.com/.../form-field-values-set-with-pdfbox-not-visible-in-adobe-reader

Druva Kota just in case you see this..?