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.
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 a DocuSign with multiple signature field (one primary and others secondary), I need to send a form to primary signer where there are few additional email fields which the primary signer will fill and the document needs to go to those email ids (which primary signer has provided in the form). Primary recipient has to sign first signature field and then send the same form to another recipient and he has to sign other signature field keeping the previous recipient signature and so on and I have to set the recipients programmatically in envelop. Is it possible? and how can I implement that?
The answer to this is 'sort of.' We do have a feature that can take care of this for you, or you can programmatically add in additional recipients based on formdata.
The recipient role is an agent managed envelope, specifically Address Recipients. What this role does is allows that person to set the name / email address of any future recipients in the signing order. You would essentially create a placeholder role with the tab information for the additional recipients. Once your Address Recipients role fills in the names / emails, they're automatically processed per your template / envelope.
The other option would be to either update existing envelope roles from dummy information to the intended recipients programmatically. The reference guide for creating a new recipient on an envelope can be found here: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/create/ -- you should be able to add in additional signers as long as the envelope has not reached a 'Completed' status. I would advise adding a sort of placeholder / approver role after the initial signer fills in the email information so the envelope doesn't automatically complete.
The reference page for updating an existing recipient can be found here: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/update/
Regards,
Matt
The way it worked for me is -
Created a template envelop with a recipient role (Update Recipients) and few dummy signers.
In the code just pick the first recipient and send the document to that recipient.
When the recipient with role "Update Recipients" receives the document he can further modify the dummy recipients and the email goes to them for their signature.
When all the recipients signs the document the workflow completes.
But I have one problem: When all the recipients complete their signature and workflow completes, I want to further do some processing in my code so how I can specify a "return url" which will be called when workflow is completed.
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).
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.
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.]