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.
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 am using Java SDK, embedded signing. I want to have two or three signers, and with specific order. Also, how to prevent one signer to sign someone else's sign tab?
When you're specifying the recipients of an Envelope that you're creating/sending, set the routingOrder property of each recipient object to an integer to indicate the sequence in which the recipients should sign the Envelope. For example, if an Envelope has 3 recipients and I want them to sign sequentially (one after another), I'd set routingOrder to 1 for the recipient who should sign first, routingOrder to 2 for the recipient who should sign second, and routingOrder to 3 for the recipient who should sign third. Note that if you're using embedded signing, then you won't be able to successfully request the signing URL ("Get Recipient View") for a signer until it's his/her turn in the routing order.
Re how to prevent one signer to sign someone else's sign tab -- when each recipient accesses the Envelope, he/she will only have access to the tabs (including signature tabs and another other input fields) that were assigned to him/her at the time the Envelope was created -- it works this way by default (you don't have to do anything special to get this behavior).
I will add 4 recipients to digitally sign the document. Is there any way where if 3 of 4 recipients sign the document can be considered as complete signing.
You can also have a recipient who is an "Editor" or an "Intermediary" recipient--they would then decide if the additional people need to sign or not.
DocuSign does not have the optional recipients feature.
Your integration should handle the case of conditional recipients and create the envelope with the exact number of recipients.
DocuSign supports other types of recipients. You can consider using them
Carbon Copy
Carbon copy recipients get a copy of the envelope but don't need to sign, initial, date or add information to any of the documents. This type of recipient can be used in any routing order. Carbon copy recipients receive their copy of the envelope when the envelope reaches the recipient's order in the process flow and when the envelope is completed.
Certified Delivery
Certified delivery recipients must receive the completed documents for the envelope to be completed. However, they don't need to sign, initial, date or add information to any of the documents.
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.
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.]