My use case only requires Docusign for e-signature of pre-filled PDF forms.
The PDF forms will be generated on our application side where some fields will be automatically filled (using xPressions) and the user will fill in the remaining blank fields.
The use case:
In our web application the user is presented with a task/action.
After invoking the task the user is presented with a PDF form.
The user fills in the blank fields of the PDF form and closes it.
The user is then invited to e-sign the document.
The web applications initiates a session with Docusign and transfers the PDF document to Docusign.
The web application hands control over to Docusign (in an IFrame) where the user can add a signature to the document.
Docusign hands control back to the web application.
The user task is complete.
The web application retrieves the e-signed document.
End
In this use case we don't have a need for Docusign templates or powerforms as the PDF generation solution already exists. This existing PDF generation solution is quite complex and it would not feasible or cost effective re-implement within the Docusign solution.
My question, is the above, e-signature-only, use case feasible within the docusign solution?
You will want to use "embedded signing" to keep the entire flow within your web app. This is accomplished by specifying a "captive recipient" as the signer. In addition to name and email address, you will specify a "clientUserId" for the signer. This should be specific and unique to the actual signer, e.g. a "customer ID", employee ID, etc. In a pinch, you can use the email address.
See (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/).
You can use this API endpoint to create an envelope by passing your pdf.
See guide and section "Attaching documents to an envelope"
Related
We are thinking about using the Docusign API to make signing documents possible in our own app. I am currently unsure if I can implement our ideas using the docusign api.
We have a platform where you can upload and manage documents (PDF). The idea is that a user can click on an uploaded document, sign it and then upload it again. Each document looks different, so we just want to give the user the option to set a signature field and sign it himself.
Here is a short example of our idea:
User selects PDF document (in our app) and clicks on a button called "sign".
A new frame opens (with Docusign UI, if possible?).
The user sets the position of the signature field, signs it himself and presses "save".
The signed document is uploaded to our app as a PDF document.
Can this be done using the Docusign API?
Our App is built with nodejs.
Many thanks in advance :)
Daniel
Not sure if there is a specific part of the scenario you need help with. Yes, the scenario above is possible to implement with our DocuSign APIs.
You'd need to create an envelope with the uploaded PDF documents and send it over to the user. They can then sign/add tabs where they like to sign.
Let us know if you need specific clarification.
I am working with existing Word documents that are currently updated in a mail merge. I would like to be able to (on the high-level) just be able to convert these documents in run-time to a Docusign template with signable fields and automatically send them (without having to upload documents to the Docusign site, etc., etc;). I don't want to change our current workflow, just add a "behind-the-scenes" step that automatically creates and sends the DocuSign envelope(s) to the specified signer. The users won't be signing into Word or DocuSign, they'll be literally clicking a "Generate and Send Document" button. Is the Docusign API object exposed in a way that makes this possible?
Chris Fleetwood
Software Developer
N.C. Partnership for Children, Inc.
cfleetwood#smartstart.org
One way you can do that is using the DocuSign Connector for Flow and PowerApps.
This does require you to have an account with Microsoft and potentially pay them extra (I'm not sure about that part, you would have to check with them) but it seems to have the functionality you need, without having to write any code.
DocuSign also has a Word Add-In that does support templates, but only through the template-match feature. If the document you are authoring looks like a document stored in your DocuSign account inside a template - you can use this template form Word with one-click.
I created a template and to use that I upload a excel with list of user's name and email. Then docusign send the email to recipients and signature is captured.
I want to automate part of it. Have a link in application that should fetch the document to sign [ parameter for templates - logged in user's name and email ] and then display the document for user to sign. How this can be achieved in java web application... we are using Oracle ADF for application.
This Code Example Launcher should help.
If you are looking to have your end-users sign via email, you can
(1) Utilize Bulk Send functionality to send a DocuSign template to a list of different users. See this guide
If, however, you are hoping to embed Docusign in your app, I would suggest you investigate
(2) Building embedded signing with a template. Specifically, Check out example #13.
I'm only mildly technical and not the web lead for my company, but I am the membership lead and I'm hoping to use your API for my workflow. This is what I need:
A web form on our website that asks for Name, e-mail, age, and a drop-down box of predetermined locations.
Using the above, I'd like the age to decide whether the requestor receives the Over 18 or Under 18 version of my form. Then I'd like the name to be auto-filled into the correct form. I'd like the form to be then e-mailed to them for a signature, and I'd like the signed, returned form to not only come to my primary e-mail address, but also to use the location to send a carbon copy to their local representative.
Can it be done? Thank you all for your help!
Yes you can use DocuSign to easily achieve the workflow you've stated. There's probably several ways you can implement this, I'll focus on the first that comes to my mind which is using DocuSign Templates.
Using Templates you can upload documents into your DocuSign account at design time, add workflow, tabs, routing, etc, then at run-time your app can reference these templates and match specific recipients to placeholder roles configured in the template.
For example, your flow would be:
Create 2 templates in your DocuSign account, one for 18+ case and one for Under 18 (note: you have unlimited templates in your account).
Add a Carbon Copy recipient as the second recipient for each template, make sure to give a routing order = 2 by setting the signing order.
Once your web form receives all input data from the user (ie Name, email, age, and location) use the Envelopes: create API to create an envelope with the form data populated in various tabs.
By default, once they are done signing the platform will email them a copy of the signed document (you can control this through account settings).
The Carbon Copy recipient will also receive a copy of the signed document once signing is complete, you can store a static email in the template or provide new recipient information at run-time when making the API request.
For more info see the DocuSign Developer Center. I also recommend you have a look at the Tabs section and Templates section for some highly useful information.
I'm using the Docusign REST API. I've created an envelope with multiple recipients and I've retrieved the sender URL to open up the web consult to place signature/initial tags.
Is there any way with the API to not allow the sender to actually SEND without dragging at least one signature tag per recipient?
Re: Is there any way with the API to not allow the sender to actually SEND without dragging at least one signature tag per recipient?
Not specifically. But here are some ideas to improve the situation:
Include signer tabs for the sender
As part of creating the envelope, include a signer recipient tab for each of the recipients. Then the person editing the document would simply move the tab around on the screen rather than having to drag it over from the tab toolbox on the left side.
Give more responsibility to your integration application
Enable your integration to have more control over the business process and therefore not show the "sending screen" to the sender. This way, your senders spend more time interacting with your app, and your app has more control over the situation.
For example:
If only a couple of document types will be sent, enable the sender to choose the document type and to fill in its parameters via your app. Then you can send the document out for signing and your app can place the various tabs.
Or when the sender uploads a document to your app, you can check the document for anchor text such as "//signer1//" Then, your app adds a signer tab with anchor text //signer1//. See this recipe.
Or enable the senders to upload docs, but use a standard "Signing page" that your app will append to all of the envelopes. When the signer signs, the extra doc (the signing page) looks as a continuation of the prior docs in the envelope. Your app would auto-generate the signing page, including the signature tabs on that page.
If you can, I would recommend that you not enable people to upload docs. (Or maybe just attachments to the main docs). Instead, reach agreement with the business process owner on what are the possible docs that can be sent. Figure out the best format for each, and enable your app to auto-generate the docs based on inputs from the senders and from other business databases/apps.