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.
Related
I want to assign a text field(read only) dynamically from code, separate for each recipient in a multi recipient embedded DocuSign using rest api (PHP SDK). How to do that using template role and tabs in php? or
How can I restrict certain fields from being viewed by specific recipients?
So your last question and the "single document" means you cannot use the DocuSign Visibility feature of DocuSign, I assume you know about that.
So, you can have readonly fields and you can have them assign to specific recipients, but other recipients will see them too.
You can also use pre-filled fields that enables to have a field that is not for any recipient and your code can fill it in.
What I recommend is this, since you need a template anyway. Create your template using the web app, make sure it works as you expect by trying it and sending documents to yourself using it.
Once you got it all working as expected in the web app, using the API is not that hard, all you have to do is get API logs of what the web app did using the API and you can do the same.
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"
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 have a web application integrated with DocuSign API, to pass in recipient details to a DocuSign template and initiate signing process. The template has tags for each recipient to enter relevant information and sign.
Once the document is completed/signed by all recipients, the information available in the document needs to be passed on to another web application bound to a DB. What are the options available in DocuSign to trigger document data(e.g. recipient1 signed date) transferred to a DB/other systems on document completion? Any advice on this is appreciated.
You probably need to provide more specific information but generally, you can use DocuSign Connect and configure your API source to integrate the data. After that, you will be able to use webhooks (or Connect) to send tabs data and signing statuses to your 'other systems'.
Once you get your Connect figured out, you can then have GET request using this
{{baseUrl}}/envelopes/{{envelopeId}}/recipients?include_tabs=true
and then have a wrapper class to export desired tabs (ex. Date Signed or other Text Tabs)
OR you can configure a webhook to sync your data between DocuSign and other systems:
Code Example: Using a Webhook to Track Envelope Status
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.