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.
Related
I am using Remote Signing with the DocuSign api, but I want to know how to determine what action the recipient took (i.e. they signed, declined to sign, viewed, etc). How do I do this?
You want the status of the envelopes you sent?
Best technique is to create a webhook and have DocuSign call your server when the envelope's status changes.
You can create DocuSign notification message subscriptions at either the account level or at the individual envelope level.
See this blog entry for more info. Ask additional questions on StackOverflow if you have any difficulties.
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.
I am using the embedded signing feature of DocuSign and I have integrated my application with DocuSign. I am using the SOBO functionality to create envelopes.
I am able to generate the URL and able to send it also. User also getting the envelope but when I login to my DocuSign account, I don't see the entries in sent items.
Please help me to understand what can be the issue here.If we leverage the SOBO functionality why can't we see the entries in Sent items?
If the signer is receiving the envelope, then you're sending it correctly.
In that case, if you're using SOBO, then the user that you're sending the envelope for should see it in her Sent items list, not in yours.
Eg, "System account 01" is an authorized SOBO user. It sends an envelope on behalf of Susan. Susan should see the envelope in her sent items list. And Susan should receive email notifications when the signer signs the documents, when the envelope is completed, etc.
We have a docusign document that was sent to a customer. Customer couldn't access it, so our customer service sent the document via docusign to him again. So now we have 2 docusign documents for the customer. I wanted to cancel one of them, but I didn't want the customer to be notified because they see the document being voided and they get confused. So I removed the customer from the envelope through REST API and I was going to void the envelope but after I removed the customer from the document, docusign changed envelope's status to complete. I also had Carbon Copy recipients in the envelope.
Any idea how to work around this? Voiding an envelope without sending a notification to the customer? And why is docusign changing the envelope's status to complete?
This sounds like remote signing, and therefore DocuSign will be sending out various emails to recipients depending on the action. IF the customer has a DocuSign account there are options that user can set on which email notifications to receive, but for the most part we can assume they do not. If you void the envelope, they will receive a notification.
When you removed the recipient from the envelope the workflow continued forward (to the CC recipient). As all explicit and required actions by the roles in this transaction are completed, the envelope will transition into a completed state.
I have been creating DocuSign envelopes using SOAP based API call "CreateAndSendEnvelope".
When I create an envelope using captive recipients into my DocuSign demo account..
1) When I include captive recipient's e-mail address in the SOAP request, would a captive recipient get a signed document back? I am not able to get the signed document back. I get an email with the notification that I signed the document.
2) My session never times out. According to DocuSign documentation, the session times out in 5 minutes and it is a configurable setting. Where should I look at that setting and how should I test the session timeout?
3) When I request recipient token once and if I make the request to get the token within a short period of time, I get an error. After I wait for a few minutes, I am able to retrieve the recipient token fine. Is there a time frame that I should consider while making a request to retrieve the recipient token?
1) You can control whether or not to include the completed documents in the email through an account setting. Login to the Console and go to Preferences -> Features, and on that screen you should see an option labeled "Attached Documents to Completed Envelope Email".
2) The default session timeout is actually 20 minutes, not 5. And if you want to change that you need to contact your Account Manager - it's not a setting you have direct access to.
3) Embedded Sending and Signing URL tokens are only valid for 5 minutes, after which they expire. At that point you simply need to generate a new URL token for the given recipient.