I am using the embedded sending interface to send DocuSign envelopes.
There might be the case where different senders assess the same envelope through the embedded sending interface. (for example the first user does not send and the second user comes into the application page)
I have tried enabling the Sharing permission but the users are redirected to the Manage Envelopes Inbox page instead of the embedded sending interface.
Any suggestions on how I should go about to do this?
Perhaps the answer is to back up a step:
Your app can show the documents to the user for approval. If he approves, then he sends the envelope. If he thinks someone else should review/send, then he re-assigns the task to his colleague for her to review/send.
The issue is that once a person starts the sending process, it is tricky to undo it.
I suppose the first person could simply not send and then your app could void the envelope and create a new one for the other person to review/send. But I think that would give a poor UI.
Also, are you sure that you need the senders to use the embedded signing view? It is often a much nicer UX (user experience) if your app can entirely send the envelope on behalf of the signers.
Your app has the most "domain knowledge" of what needs to be sent. Any per-envelope changes can be mediated between the senders and your app. Then your app creates the right envelope and documents.
Related
We have ASP.ET MVC Web application. We are using Docusign SDK For C#.
We are planning to go Live with DocuSign Integration and We looked at DocuSign limits (specially 15 minutes get request limit).
We need an advice on how to avoid violation in Envelop Correction scenario. Steps are as given below.
Get status of envelop
Get recipients of envelop and show it user in the GUI
User updates email in the GUI and submits form
On backend we Get recipients again with all tabs and custom fields, Update email address
Call Update recipients method
You see on number 4. It is 15 minutes violation. How to handle this scenario?
We don't want to create Whole mechanism for Saving/Caching DocuSign Recipients data and statuses. As those statuses can change from DocuSign or some of the recipient can decline or void envelop. We want to fetch latest recipient data to update on the time of execution.
I agree with Inbar that you could store the results of the first get_recipients call. You could either store it in the user's session state (server side) or send it all to the browser and then have the browser return it.
I'd go with session state
Saving data in the session state isn't a big deal.
Re:
As those statuses can change from DocuSign or some of the recipient can decline or void envelope.
So you're worried that while the application user is updating an email address, the envelope will be declined by a recipient?
In that case you could lock the envelope while your user is updating it. Or you could not send the envelope until after the user has updated it. Or if you get an error while updating the recipients, that would be the time to do the extra recipients_get.
I want to make an API call to "create" an envelope:
https://developers.docusign.com/esign-rest-api/reference/Envelopes/Envelopes/create/
but where the envelope belongs to a different user than the API caller.
Right now, when a DocuSign envelope is created, they all show up in Manage/Drafts of the API user...but I'd like to control which user they go to, so a user like name#example.com can log into their DocuSign account and have that envelope show up in their drafts. I want to do this programmatically instead of clicking around a UI every time.
We have our DocuSign integration through Intelledox, and in their Infiniti Design, we have different hooks set up (create/post/send email) and their UI dropdowns for Action Input have a lot of different actions one can do....but there's no "Assign Envelope Owner" or anything like that...hence me digging through the API to see what can be done.
I saw a question like this over at DocuSign REST API, easily move envelope from user A to user B? (ie, change the envelope owner) but it was 6 years ago and wasn't sure if this ever got moved to "possible".
If your objective is that you need other users to see the envelope, then you simply share the user's envelopes with other users. That way, one does not have to login with the API user in DS to see the envelopes. If you want the envelope being sent to appear to a different user other than the API user, try using custody transfer feature in DS. however this will be limiting to only one user. Else, I do not thing there is any other way, May be you can check with IX support on that.
createSender creates a URL, which I would like to use to let the sender preview the document before it's send out. Hence the documents are created using templates and and the API.
The link which is created would lead me out of my UI. Does the user need to sign in? Future plan is to have many user's, which have no DocuSign account.
For embedded sending Your app will have to authenticate the user. If you are doing a Service Integration then your Api account will be used as the sender.
Once the sending url is generated using the createSenderView api, there is no authentication required to access the URL.
You also have an option to build a User Application using the docusign Api where your App can support sending from multiple accounts.
The createSenderView requires that the person is a DocuSign user (with their own account and password).
Only DocuSign users can send. We charge for sending, not for signing or receiving.
What exactly do you want to preview? (And why?)
the documents themselves? Use the EnvelopeDocuments resource. You can also preview the thumbnails of the documents.
the documents with the "fields" ("tabs") that indicate where people will sign? I'm not sure that is do-able.
or the recipients and their routing order? Use EnvelopeRecipients: list method.
Added
Another solution is to use a dummy certified delivery "recipient". Add this recipient as the first recipient. This will block the envelope from proceeding on the recipient routing.
Then get the envelope's documents to show as a preview.
Then, if ok, alter the envelope's recipients to remove the certified delivery recipient. The envelope will then continue on with the first "real" recipient.
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.
Is there any way programmatically (using Java) to stop the signer from getting a notification and receiving the completed document?
I see an option in the user profile but I want to set it while sending an envelope.
You could use embedded signing. That way DocuSign would not know the email address of the signer.
You should also check with your legal counsel about your plan. Asking someone to sign a document and then not giving them a copy of it is unusual behavior.