I am making a node application with handlebars.
The website contains normal signup and login functionality. After that, User has to fill a Form which contains his/her basic information. There he/she has to do a digital signature on it.
I want to do this by DocuSign.
I want that each time any new user signup, then he/she can do sign on the form.
I see the DocuSign docs but I am not clear about how to do dynamically with different users. I am able to do the sign manually by creating an account on DocuSign website. Then write the integration key on code and creating a template of form.
But I am unable to do all these by the code in nodejs.
If I understand correctly, you want:
Someone visits your web app
They use forms to add data to your web app
Your web app will create a document based on the data entered.
The visitor will then sign the document using DocuSign.
Very do-able:
Your web app can create the document to be signed in multiple ways. Your app can create a PDF, or many other document types. I suggest that you start with an HTML document. Note that an HTML doc can't include external content such as links to a css file or graphics. See example 2 of eg-03-node-auth-code grant for an example of this technique.
An alternative is to use a PDF of a form as a DocuSign template. Then your envelope will fill in values for the template. See example 16 of eg-03-node-auth-code grant
Next, your web app needs to create an envelope in DocuSign and present it for embedded signing to the web app visitor. First, get a DocuSign access token by using the JWT Grant flow. Use this flow since the signer doesn't have their own account on DocuSign. If the envelopes are "from" the HR department then use a generic HR department user id. Example of using JWT Grant in Node.JS: eg-01-node-jwt
Use the access token to create the envelope and then open an embedded signing ceremony for your web app visitor. See example 1 of eg-03-node-auth-code grant for this part.
Related
Is there any way to display all the documents/envelopes which are needed to be signed by the user in our app? or list all the links of these envelopes in our app so that when the user clicks it will take to Docusign UI same as how it works with email
enter image description here
Yes, you can, but there are some things to consider.
First, you will need to make API calls to find all the envelopes that needed to be signed by the user.
From the Java SDK use the ListStatusChanges method to do that.
Then, for each envelope you found in the right status, you will want to generate a URL using the embedded signing feature.
However, don't do that when the page loads! These URLs expire after 2 min and so what you want is to generate them when the user clicks and redirect to the generated URL dynamically, or you'll have issues with the app.
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 am trying to integrate Docusign API into my web application. I tried using Envelope Views where I am redirected to either login page or the signing page. But I would like to redirect to Add Recipients page from within my web application where the user can add the recipients, prepare the document and send it to the signer. Is there any method as such exposed from Docusign API?
Re: But I would like to redirect to Add Recipients page from within my web application where the user can add the recipients, prepare the document and send it to the signer.
Is there any method as such exposed from DocuSign API?
Yes, the EnvelopeViews::createSender view enables your application to open the Sender's view of the envelope on the DocuSign web site. The user can then add recipients, tabs, etc.
Here is a code example that shows you how this works. You can download and run the code example in many languages.
Information Security Notice
This method, EnvelopeViews::createSender, provides full access to the sender's user account. When you use this view, the sender has full access to the user account. If the sender user account has administrative privileges, then this method also provides administrator access.
If your use case needs to enable a sender to update a draft envelope before it is sent, then either:
Configure each sender to have their own individual user account to use this API method.
Enhance your API integration so that this method is not needed. Your integration can create the tabs, recipients and other envelope settings as needed.
I am new to Docusign and we have a requirement to integrate Docusign in our web app. I have gone through all the links for integrating docusign into a web app using REST Api calls. After thorough read and watching youtube videos, I came to know that we can integrate docusign in our web app through REST API calls but for the same additionally we need to develop our own UI to upload documents and send it to the recipient. But basically we are looking something where we can be reidrected to docusign from our webapp to perform all the operations of sending document for signing and once document is sent then I will be redirected back to our web app.
Kindly help with the above query and let me know if my understanding is correct for integration of docusign and for the same developing our own UI in our web app. Also please let me know if there is any alternative to fullfill the requirement of directly accessing docusign from our web app and performing all required operations of sending a document to recipient.
Thanks in advance!
So you want a button on your web app that says "Sign with DocuSign" and then what?
Most customers who want to send from their web app already have the documents controlled by their web app.
They:
authenticate the user with DocuSign (OAuth Authorization Code Grant)
Upload the document to DocuSign from their app.
Add tabs (signing fields) to the documents programmatically. (This is not hard and it saves the sender a lot of work.)
Upload the recipients (signers, copy-only recipients, etc)
And then tell DocuSign to send the envelope (the transaction).
Applications can also monitor the progress of the envelope through the signing process and programatically act on the signed documents.
The above is not hard to do and provides a good user experience.
You can also redirect the user of your application to DocuSign to accomplish any/all of the above manually. But the more the user does manually, the less convenient the integration will be for them.
If you want the manual experience, check out the EnvelopeViews::createSender method.
When using the Docusign API (in my case, via the Sandbox/demo env), in the signing view at the top of the screen it displays the name & company of the user account that was used to authenticate with the API.
However, because this is embedded signing from my app, I would have thought we'd only have one user account - for the app. So I want to change what appears at the top there - the information on the sender of the envelope. Either to be the user account that exists in my app that created the envelope, or just to state what company sent the document.
Are there options on the API to do this? I can't see any reference to anything like this in the envelopeDefinition JSON structure in the REST API docs.
You can use the DocuSign SOBO - Send On Behalf Of Functionality
The Send On Behalf Of feature permits automated sending through the API by one account user on behalf of another account user.
More information here