Is it possible to send an Envelope to someone, have them fill it out and sign, do external validation, and then send the envelope to the next signer? Currently using the API, if I specify only one recipient, the Envelope is marked completed, and if I specify multiple recipients, the next signer is immediately notified after the previous person signs.
You could add a special recipient that is your "validator."
That recipient can be your system and using DocuSign Connect webhook, your system would be notified when it's your turn, between the first and third recipients. You can do the validation and decide how to proceed. You can do things like void the envelope or correct it. If you need the envelope to be routed differently - you can do that too.
The second recipient is just a mock one to stop the envelope from going to the next recipient upon signing of the first one.
Related
We have a business case where we have a document that is auto-tagged (text-pattern matching) for two signers. We send the envelope to three recipients. The two auto tagged signers are able to login and sign the envelope, however the envelope does not send back the envelope complete notification in DocuSign Connect.
Is there an account setting so that only the signers that actually have to sign can send the complete notification. We have a few envelopes in this limbo state of not being complete.
We are using the C#SDK/RestAPI to create our envelopes.
Thank you
We have tried submitting an envelope with three signers, and the document only contains auto-tags for two of them. The third signer can access, but has no signing capabilities (as intended). The envelope doesn't fire the completed notification because of this.
Every signer must "act" on an envelope in order for it to be complete.
In your situation. the 3rd signer was intended to only view the envelope then it should not be a signer.
There are other types of recipients based on your requirements.
Two options:
CC - this means they'll get a copy, but they don't have to view/open it.
MustView - this is a type of recipient HAS to open the envelope for it to be complete, but does not have to sign it.
If you change your 3rd recipient to either one of these (and in case #2 that recipient actually opens the envelope) it will be completee and you'll get the complete notifications.
I have successfully created a system to use a document template to create a new envelope.
The system has a tabbed UI and iframe that fetches new URLs from the Docusign API every time a tab is changed, and when a URL expires.
My problem is that now, some clients will either be sign in-person or sign via email. After reading the docs, I don't see a way to change from an in-person to an email signer after the envelope has been created. Is that correct?
Is it possible to set whether a role will be in-person or email sign at the time of envelope creation, without affecting the original template?
If that is not possible, Is my best option to create a template with duplicate fields for both in-person and email signing, and only use the appropriate ones based on my case?
If you need to change an in-person signer to a remote signer, or vice-versa, or any other recipient type into another recipient type you have two options:
Perform an Envelope Correction
Remove then Add the Recipient back to the in-process envelope as a different type.
For option #1, using an envelope correction you can edit things like recipients, tabs, and even documents if they have not been signed yet. Make the following API call to request the correction URL of an envelope:
POST /v2/accounts/{accountId}/envelopes/{envelopeId}/views/correct
API Docs: https://docs.docusign.com/esign/restapi/Envelopes/EnvelopeViews/createCorrect/
For option #2, the system does not let you convert a recipient into another recipient type - HOWEVER - you can delete a recipient from an envelope then add them back in as a different type. For instance, delete an in-person signer and then add them back in as a signer.
You can see the needed calls through the EnvelopeRecipients Resource.
According to DocuSign documentation, we have to use "Modify or Correct and Resend Recipient Information" method in order to resend an envelope. However, this method is also expecting a collection of recipients.
Is there a way to simply resend the envelope to the current recipients?
I had originally thought about something like this:
string requestUrl = string.Format("https://{0}/restapi/v2/accounts/{1}/envelopes/{2}?resend_envelope=true", Properties.Settings.Default.Domain, Properties.Settings.Default.AccountNumber, envelopeId);
HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(requestUrl);
request.Method = "PUT";
request.Headers["Authorization"] = string.Format("bearer {0}", Properties.Settings.Default.AccessToken);
Related question: Resend DocuSign Emails
I don't believe it's currently possible to resend an Envelope to all recipients, without using the "Modify or Correct and Resend Recipient Information request (which requires that you supply the recipient information for each recipient you wish to resend the envelope to). As you noted in your question, this procedure is described in this related question.
Seems like the main use cases for 're-sending' an Envelope involve scenarios that would most commonly affect only a single/specific recipient within an Envelope. For example:
A recipient has misplaced or deleted their original "invitation to sign" email.
A recipient's email address was specified incorrectly the first time around, so you need to re-send the "invitation to sign" email to the new address.
Etc.
In scenarios like these, it makes sense for the 're-send Envelope' API call to require that you specifically identify the recipient(s) who should receive the email notification again -- because you only want to re-send to the specific recipient(s) who had trouble with the notification the first time around.
using the DocuSign API is it possible to build a workflow where we send one document to two (or more) signers in such a way that the document envelope gets marked as "complete" as soon as one of the signers signs...e.g., we send a document to persons A and B, as soon as person A signs then DocuSign marks the envelope as complete and B no longer has to sign.
Cheers !
DocuSign behavior is such that each and every existing "signer" for an Envelope must access the Envelope and "confirm signing" before the Envelope can move to a status of "Completed". However, it IS possible to implement the workflow you describe -- with some coding on your part.
For this example, let's assume you create an Envelope with 3 recipients, each of type signer. As soon as any one of the 3 recipients completes/submits the Envelope, you want the Envelope to be considered Complete. You could achieve this by doing the following:
Implement DocuSign Connect either at the account level OR at the Envelope level (by setting eventNotification properties in the API request that creates/sends the Envelope) -- such that DocuSign Connect will send the "listener" endpoint you specify an HTTP POST message (in XML format) whenever a "Recipient Signed/Completed" event occurs for an Envelope.
Build/code your "listener" application to parse the XML messages it receives from DocuSign Connect, and if/when a message indicates that a recipient signed an Envelope, code your "listener" application such that it makes an API call to DocuSign to Delete each remaining signer recipient for the specified Envelope. In the example of an Envelope that contains 3 signers -- signer A, B, and C -- this would mean deleting signers A and C if the Envelope's been signed by signer B.
As soon as an Envelope no longer contains any recipients that must receive/acknowledge/complete the Envelope, the Envelope's status will automatically advance to "Completed". By implementing the procedure I've outlined above, you're essentially forcing an Envelope to complete by removing/deleting all incomplete recipients by using the API, as soon as DocuSign Connect notifies you that a recipient has signed. [Do note, however, that when you remove/delete a recipient from an Envelope, that recipient loses the ability to access the Envelope from that point forward.]
I'm trying to dynamically populate a non-signer CC role upon creating an envelope from a template using the REST API. Is this possible? Currently, when I add the "receive a copy" recipient role to a template and then set the email for that roleName in the code and send the document off for signing, it automatically "completes" the document which seems like a bug or it may be that I'm doing something that isn't supported? Can anyone help?
Thanks,
Janea
Ergin was correct. Using the API call to add the CC role as the envelope is created from the template works as expected. It did not seem to work initially but, not sure why.
Carbon copy recipients are unique in that that is the only recipient type that does not take any actions on the envelope. They simply receive a copy of the envelope when it's their turn in the routing order, they never see the "tagging" workflow (unless they are added as another signing recipient on the envelope at the same or a different routing order).
When you have a CC recipient and it is their turn in the routing order, nothing happens except that they receive the notification email. If they have the highest routing order out of all recipients (i.e. if they are the last recipient) then the envelope status will already be completed by the time it reaches them and it won't change status and will remain as complete.
Are there other recipients? If there's only a single recipient and they are marked as "receive a copy" or "CarbonCopy", and not marked as a "Signer" type, it will probably see the envelope as complete.