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.]
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.
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.
using DocuSign API, when a document is send to multiple signers, is there any way to complete the envelope when anyone of the signer signs the document. Eg: Document abc.txt sent to Recipient 1 and Recipient 2. if any one of the Recipient 1 or Recipient 2 signs the document, the envelope status should be set to complete.
Depending on the specifics of your scenario, Signing Groups may enable you to achieve your goal (i.e., send to a group of people, and consider the envelope 'complete' once one of those people completes/submits the Envelope).
There is no optional signer in DocuSign. For the envelope to reach a completed status, all recipients marked as a signer, will have to finish the signing process
DocuSign supports other types of recipients. Read the documentation and see if the other recipient types fit your usecase.
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.
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.