I need to create a pdf so that all the responses got in google form should be present in that pdf.
What I did
I clicked on response tab of google-form then clicked on print all responses which generated pdf for all responses but I don't like the format of that pdf.
Then I used Document studio add-on for google spreadsheet (which contains the responses for each user) but it generates pdf for each user rather than all responses in single pdf.
What I need
Is there a way that creates pdf for all responses in a custom format just like Document Studio?
Related
I am not sure how to phrase this question. We have code that creates a PDF that is PDF/A compliant, we put in some xml data into the metadata section. We then display the PDF in a preview window where the user can download the PDF. As part of our users process they open up the PDF in a text editor and search for one of the xml tag, "vendor" while all the data is encrypted, the tag value of "vendor" is still visible, such that the search would work. And then the users submit these files to US Courts that export the data.
I am on a Mac and I follow this process and it works perfectly.
The issue we have is that on Chrome/Windows users when they download the PDF and try to search for "vendor" it doesn't work. The search fails. If the user opens up the document in Adobe Acrobat Pro and then just hit Save, then open it in their Text editor it then works. The problem is our users are now complaining about having to do those two extra steps.
This only occurs on Windows users with Chrome. It does not happen on Mac/Safari.
I wish I could attach a sample, but the documents are extremely confidential, and I can't make one up with non confidential data as that would then not match what happens in our application.
We would like to generate a PDF without using the existing "PDF" button, but we would like to add our own button that gets a custom template and generates a document filled by the data in the form.
Which Orbeon API we can use for this purpose? This API will get the form id and the PDF template and will generate the document.
The API should give us the possibility to :
Map data to the PDF.
Save the PDF in a given directory.
Sdd some changes to the PDF like adding an image and save the document (this will be our custom code).
Download the PDF after process.
What you're looking for sounds very much like Orbeon Forms' PDF template feature. With Form Runner, you can add your own buttons to the form, and those buttons can have their own label and "logic". The latter is defined in a process, which is a sequence of actions. One of those actions is send(), which as its name implies, "sends" some information related to the form to a service you provide.
You can configure that action to send a PDF generated by "filling" a PDF template with the data entered by users in the form by using send(content = "pdf"). You can find more about this in the documentation for the send() action.
I am having a PDF form that saves the data and validate the data entered by user e.g. a client information PDF document that takes client data and when user click on send button, it must post the data to the web service that further process it or saves to database.
I am using Acrobat Professional for this. Can anyone help in this?
Acrobat and Adobe Reader can submit form data to any URL using a button on the document and the "Submit a Form" action or via Acrobat JavaScript (probably unnecessary). You just need something on the server to interpret the data. If you submit as HTML, the submission will look just like query parameters where the key names are the same as the names of the fields and the values, same as the field values without the formatting. To the server, it looks like it was submitted from a standard HTML form so just about anything you have will be able to work with the submission.
You need to use Acrobat Pro to add this button to the document but then Standard and Reader can use it.
See https://helpx.adobe.com/acrobat/using/setting-action-buttons-pdf-forms.html
You can also submit as FDF or XFDF, an XML(ish) expression of FDF, in which case you'll want to use something like the FDF Toolkit to read it but based on your question, I don't think you need to do that.
3rd party edit
Information from the linked page
FDF
Returns the user input without sending back the underlying PDF file.
You can select options to include Field Data, Comments, and
Incremental Changes To The PDF.
XFDF
Returns the user input as an XML file. You can include Comments with
the field data or just the field data.
I want to know that how to verify the report. Report is in PDF format and has table or images etc. Image is attached here for further information.
Selenium won't give you direct access to the contents of a PDF file.
Have you looked at JPDFUnit (a wrapper around PDFBox)?
I personally would separate the verification of PDF contents from the functional tests based on browser interactions.
I have created a LiveCycle PDF form that includes a Submit button to send it as XDP (including the base64 encoded PDF) to a server that pulls out the XML data and saves that to a database and then pulls out the encoded stream, decodes it and saves that back as a PDF on the server.
The issue that I am having is that once I open the PDFs made from the base64 encoded data, it seems that they are empty. After some testing I found that if I manually save the PDF before Submitting it, the information that was entered up to when it was saved is included in the encoded PDF (whereas the full data is included in the XML portion).
So my question is there a way to either:
Automatically save the PDF or otherwise preserve the data so it is sent in the base64 encoded portion of the XDP? (preferable)
Recognize when a change in the document has changed and request that the user save the PDF before clicking submit?
It seems the issue I described above was actually due to using Foxit reader instead of Adobe reader.
Adobe reader of course requires the Reader Extensions in order to be able to save form data and submit it.
Foxit does not have that restriction but does not embed the updated version of the PDF in the XDP XML data sent to the server. The only way to perform this would be ensure the user saves the PDF first which removes the Reader Extensions as per Adobe's licensing requirements.