I have looked at several PDF uploaded on docusign website but didn't get success at all. My problem is I want to create a generic email template in my docusign account but want to update its uncommon(client specific) content dynamically using the Docusign Web-service API.
For example: Client Name, Client Address, Phone Number, Mobile number, Payment Amount, and Payment Last date are some fields whose values varies based on client whereas other content of the email is common for all, Hence I want to understand that is there any way so that I can set the values for this fields in WS call and docusign will use that common email template and replace the customized fields on the fly for every client.
We Will make one WS call for one client at a time. Please help it is quite crucial for us.
Currently we are creating email content to our side and set into the EmailBlur but want to do it more customized so in future we can make changes easily.
Quick response is highly appreciate!
Thanks in Advance !!
It's not possible to create/maintain an "email template" in DocuSign that contains placeholder variables for you to dynamically inject client-specific values into the email for each Envelope as part of the Create Envelope request.
To acheive your scenario, you'll need to create/maintain the email template contents within your application, and have your application dynamically generate the email contents for each Envelope. Then you can simply set the Envelope's emailBlurb property (in the Create Envelope request) to the contents (i.e., full email body) that your application generated.
It is Account related setting which needs to be enable by docusign, In my case I have contacted them and they made some changes after which the emailblurb method start supporting HTML.
Related
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 am using the DocuSign REST Api and noticed that the lifetime of a URL obtained using the EnvelopeViews API (https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeViews/createRecipient) is only a few minutes. However, I have gotten emails in the past with DocuSign links. How are these links able to be added to an email (and therefore have a longer lifetime)?
Is there a separate API that can be used to get a longer-life link like the one in the email?
For example, here is an email that has a Review Document DocuSign link:
Good question. Here's what you can do.
Your application wants to let Larry sign a document using the
EnvelopeViews::createRecipient API call.
Your application should store the details needed for the API call in your app's database. Something like: envelopeId, signerEmail, clientUserId.
Create a guid for the database record and add it to the database record.
Now you can look up the database record via either the row's key or
via the guid. Ensure that the guid database column is indexed.
Now create a signing url that you will send to Larry. Something like:
https://myapplication.example.com/docusign-ceremony/[guid]
Send the url to Larry
When Larry clicks on the URL:
Your app is invoked
Look up the guid in the url in your database. You should find the
record that you stored there.
Retrieve all of the record's info: envelopeId, signerEmail,
clientUserId.
Call the EnvelopeViews::createRecipient API call with the data
and get back the signing ceremony url (that must be used within
5 minutes)
Redirect the user's browser to the url.
They'll sign the document(s) and then be re-directed back to your
application.
Done.
And guess what? This is pretty much what DocuSign does itself.
The response from Larry K above is correct, you would need to handle this on your side.
These are all the parameters that you can send as part of the request body for the POST {vx}/accounts/{accountid}/envelopes/{envelopeid}/views/recipient API endpoint and there are no options to set the expiration time for the recipient view that you create.
You could look into using PowerForms to see if they fit your needs. With PowerForms you can create a URL that users can click and it will allow them to fill out a specific DocuSign envelope. This might not fit your needs if you need to pre-fill some of the fields with information related to the specific recipient but it might be worth looking at.
PowerForms Documentation:
https://www.docusign.com/features-and-benefits/features/powerforms
Please correct me if I'm wrong but I think that your goal is creating the recipient view URL, creating an email formatted in a specific way and sending that email to the recipients.
If you use the branding feature you could specify the format for your email (if you want to use a specific message) and just send the envelope to your recipients. Once the recipients receive the email they'll see the message in the format that you specified and the link for accessing the envelope would be a regular DocuSign link that doesn't expire.
The link below shows how to create Brands in your account. Specifically signing brands would allow you to set the email content.
If you have multiple email formats you could create multiple brands and just specify the brandId when creating the envelope.
I hope this helps.
Branding:
https://support.docusign.com/guides/ndse-admin-guide-configure-branding
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.
I imagine this is something simple and I'm just not looking in the right spot for it.
Is there a way to write a custom email blurb for the completed signing email notification the same way you can generate one for the request for signature notification within the embedded signing API code?
Currently my integration has the first signer embedded, then is emailed to two further recipients. All the requests for signatures have the custom HTML I've created in our application as the "emailBlurb" in the XML request body but I don't see any options to set the message for the completed signing one as well.
Sorry if this is something easy in a FAQ or guide somewhere and I just missed it.
Thanks.
A majority of the Email notifications that DocuSign sends can be customized via modification of the "Email Resource File" (an XML file that contains text strings used in the emails that DocuSign sends). You can access Resource Files via the DocuSign web console (when logged in as an Administrator) by going to Preferences >> Branding >> [Edit Brand] (link) >> Resources (tab).
This guide provides all the information you should need to customize the Resource File:
Note that an Email Resource file applies to a specific "Brand" -- i.e.,all envelopes that use a specific Brand will derive their content from the Email Resource file that's associated with that Brand. It's not currently possible to specify email contents (other than the EmailBlurb in the signing invitation email) via the API. But, depending on the nature of your email customization requirements, you could always create multiple Brands via the DocuSign web console, customize the Email Resource file differently for each Brand, and then set BrandId in each "Create Envelope" API call to affiliate the correct Brand (and therefore email contents) with each envelope.