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.
Related
I have a dynamic pdf which I want to use for DocuSign and thus needs to be static. I cannot simply make use of the print as pdf function as I still want to use the interactive fields within the pdf.
I Tried to use Adobe AEM Forms Designer to save the document as static. But solely the first page of the form is saved.
Regarding your concern, I would like to share the following information, you can learn about PDF form field transformation. It enables you to transform PDF form fields automatically into DocuSign tabs, carrying over all of their existing values. The locations of the created tabs will match the locations of the fields from which they were generated.
To transform PDF form fields into DocuSign tabs, you need to set the transformPdfFields property on the documents whose fields you want to transform.
https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/pdf-transform/
https://www.docusign.com/blog/developers/the-trenches-pdf-form-field-transformation
Best Regards,
Eric | DocuSign
It is possible in the moment of upload a content to a document library show the fields defined (of the document library)? At the moment, the only way that the user have to fill the fields is uploading the document first and then click edit to fill the fields.
Unfortunately there is no out-of-the box solution for this scenario. I agree that this would be useful, but currently you have to create a custom solution.
You will have to create a UI that displays the upload control (you can use the built-in Sense/Net plugin) and also the form fields. In the click event of a button, you have to first start and finish the upload, retrieve the new content id and than update the metadata fields - all this in JavaScript. This way users would not see the difference, for them this would be a single operation.
(in mid-term we plan to offer a built-in control that will make this possible, but we do not have a timeline for this feature)
I have a few documents that all look the same initially, but then have different content in the middle of the document.
Is there a way to make a base template pdf, and then tell a pdf to use it as the base and then add additional template data to the result.
i.e. like a modular class system.
I am using pdf, adobe acrobat pro DC, and its Prepare Form component.
and I am usign Itext to read the template and then populate the data into a final pdf.
please remove tag if this is not related to itext, but i wondered if there was an option within itext to pull a template and then add the contents from another template.
the answer seems to be use livecycle designer for dynamic tempaltes.
or wait for itexts new dynamic forms.
We want to do the following:
1) upload 2 to 100 or so PDFs per day
2) have two people digitally sign each individual PDF
2a) The first signature needs to be a "certifying signature" - with certifying rights allowing one additional signature in the pdf
From a simple test of the system, it appears the process is - via the UI:
1) Upload the pdfs via the browser
1a) with the browser UI "place" signatures (Position etc.) in the PDFs (can be 100)
2a) First Person Signs the Batch of PDFs and sends the Batch to a recipient.
2b) The recipient signs and "sends them back"
Manually putting in signature fields in 100 PDF documents per day is quite a Task. Out PDFs can be generated with Signature form fields.
Can the Docusign System find specific form fields and use those for specific users - to fill in a digital signature?
Is this possible/and better done with the API? Is there a example or document that describes this somewhere?
I'm new to this System, so this/these question(s) might be completely naive.
Same underlying document is being sent (eg an order form)
If the pdfs are different versions of the same form or document then you use a template. Eg, if the documents are contracts being sent for approval to different people, then they are all the same underlying "contract document," but with different values for customer, dates, etc.
Easiest is to first "tag" the document using a template via the web interface, then use the same template for the subsequent documents. When you upload a new document, DocuSign will also automatically suggest which of your template matches the new document, saving additional steps.
If you have just a couple of different underlying documents then you'd create a matching set of templates. Since a matching template is suggested when the user uploads a doc, it means that the end users only have to tag ad hoc documents that they are sending or when a document format changes.
Documents that vary
For these cases, using a template with Anchor Text Tabs works well. An Anchor Text Tab tells the tab (eg a "Signature" tab) that, rather than being placed at a specific page and x/y co-ordinates, the tab should instead look for specific text in the document. So you create a template with an Anchor Text Tab that will look for the string "Sign here:" the tab will then place itself nearby (you can give the x and y offsets from the text.)
Anchor Text Tabs can also look for text that is "invisible" on the page (same color as the background). So you can change your docs to include invisible strings which will enable the Anchor Text Tabs to find their correct locations on the pages.
API All of the above can be done via the API. Since templates are often just created when a new document is set up, you may want to create the template using the web UI. Then, using the API, select which specific template should be applied to the doc that you've uploaded with the API.
I've have a editable pdf with button fields in it. I'm processing this editable pdf in my vb.net application using iTextsharp. I want to know, how to programmatically invoke the button field inside the pdf. Though, I'm using iTextSharp dll, I could not find any helpful resource to invoke and handle the button events. Please guide me how to invoke the button events of pdf, programmatically using vb.net.
iText[Sharp] doesn't execute the Javascript within a PDF. It can add/remove/change the scripts present, but won't run them.
For that you need a PDF viewer from Adobe, Appligent, or Foxit (alphabetical order, though Adobe's will be the best at running script, it also puts security restraints on what you can or cannot do).