I've been working with a docusign integration into our own application for a while, and recently I've started encountering a new error that I've never experienced before. I create a docusign envelope using Docusign's own interface, add my recipients, set up the signing fields, and then click send.
An email goes out to the users with a link for them to sign the document, as expected. But simultaneously, there is another email that says the following:
[My User] has corrected [My Document].
As a result, you no longer have access.
I click on the link for signing the document, and it results in the following:
In theory, this makes sense. If an envelope is edited or corrected, then the previous links are no longer valid. However, the envelope is never being corrected. It is created and sent in a single action. There isn't even time for a correction to be made. I'm the only person with access to the account, so no one else can be making corrections to the envelope. Additionally, this only seems to occur for certain recipients. Some recipients are fine, and this correction thing doesn't occur. For others, it happens and breaks the entire chain.
What could be causing Docusign to do this? I'm working with a developer account if that makes any difference. The only recent change that was made to my configuration is the addition of Connect with HMAC signatures to verify the validity of docusign responses back to my application. Even so, most of the time things seem to work exactly as intended and expected.
Related
I've been working on an integration that sends an envelope to 2 signers. I am trying to test and program for the case of 1 of the signers having a bad email address. I would need to:
Be notified of this (webhook?)
Update the email address for the signer
Update the email address in the custom fields as that's printed on the agreement
Resend the envelope
When I enable the delivery failure notification in Connect (this is set up at the account level, for now), I don't see where the failure is noted in the webhook response or for which signer the error is happening.
I've found multiple links via Google talking about "correct and resend" but I haven't been able to get anything definitive in terms of what steps need to be taken or a (PHP) code example. I've also found "resend" in the API reference but still no code examples.
I also haven't seen any code examples (PHP) of how I would update a signer's email address and how that would work via the API.
It'd also be good to know how to update custom field data for both signers so the email address in the contract is updated (it's listed separately as part of the custom form data).
And finally, how would I resend the envelope?
Thank you for your thoughts.
Per DocuSign support (customersupport#docusign.com):
Be notified of this (webhook?)
I have updated your account settings and now you should be able to see AutoResponded in your webhook messages when email invalid or unreachable.
(my comments: so it sounds like you have to ask to be able to see this stuff, it's not part of their standard webhook responses)
Update the email address for the signer
I also haven't seen any code examples of how I would update a signer and how that would work.
Unfortunately we don't have an example for recipient update but the logic is to get list of all recipients, pick the one need to be updated, and update.
You can use below to retrieve all recipients per envelope
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/list/
GET /restapi/v2.1/accounts/accountId/envelopes/envelopeId/recipients
Extract the one you need to update edit email and update using the below
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/update/
PUT /restapi/v2.1/accounts/accountId/envelopes/envelopeId/recipients
You can also see example code in C# how to do this in this thread https://github.com/docusign/docusign-csharp-client/issues/307
Update the email address in the custom fields as that's printed on the agreement
There is bug case created ( above link ) regarding this. At the moment you can not update signer custom fields case EC-2944.
Resend the envelope
You can resend the envelope during recipient update
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/update/
PUT /restapi/v2.1/accounts/accountId/envelopes/envelopeId/recipients
My commentary:
Since custom fields can't be updated, this whole use-case goes out the window. We can't have contracts with incorrect data on it, so my client will have to do these corrections by hand. Kind of a bummer.
I'm a BA trying to understand DocuSign's eSignature feature (specifically, requesting a signature via email aka remote signing) as my company are soon to integrate. I'm really struggling to understand the end to end workflow. Is anybody able to A) shed light on this in layman's terms and/or B) point me toward documentation that better explains this than this documentation does? A step by step breakdown with no assumptions would be so helpful.
I'm particularly cloudy on how the "signing link" works; when/how it is generated and shared with the recipient and how they interact with it.
Thanks.
I suggest you look at these two:
If you are looking for non-developer document - https://www.docusign.com/products/electronic-signature/how-docusign-works
If you are looking to write code - https://developers.docusign.com/esign-rest-api/code-examples/code-example-request-a-signature-via-email
The idea is this: the signing is contained in something we call an envelope. An envelope represents a transaction. In that transaction you have people (recipients) and documents. You also need to specify how the recipients act on the documents with tabs (signing elements).
After you define all of this (which require you to specify among other things - email address(es) of the signers) you change the status to "sent" to actually send the envelope which means emails will be sent to remote signers.
At that point the DocuSign system automatically generates an email to any recipient that needs to sign that is in the first routing order (lowest number).
These emails will include a link.
That links does indeed expire eventually, but only to be replaced with a new link sent to the same email.
Clicking the link will launch the signing UI where the signer can complete the signing.
when all recipients completed acting on the envelope - the envelope is complete and a final signed/complete PDF is produced.
We've been developing a web application which uses DocuSign's API for around a year now and it was just updated to version 2.1, which seems to have caused an issue with our application. One use case for our application, which is now unable to work, is as follows:
A document has errors and needs to be sent back to our representatives and clients while maintaining information that was already filled in to be re-signed, but the simple cloning of an envelope removes all information filled in.
In order to circumvent this problem and get our application functioning as intended, we do the following:
Get a list of all of the tabs on the envelope
Clone the envelope as a draft (status: 'created')
Delete all of the tabs off of the newly cloned envelope
Making modifications such as removing any signatures from signature boxes
Add all of the tabs to the cloned envelope
Send the envelope
This all worked until around the end of last week (v2.1 of the API releasing on 08/02) when we realized that tabs were starting to be duplicated. After some investigation, we noticed that the tabs being duplicated were set to be "Restrict Changes" and were not being deleted by our API calls which used to override that sender permission. Since then, we've tried simply updating the cloned tabs with a PUT request after adding a value to certain tabs, which also gives us an INVALID_TAB_OPERATION error. While we haven't seen any documentation in the v2.1 update to suggest that change, we believe it has happened, whether it be a feature or a bug.
So the question is: was this change intended and can it be circumvented somehow to get our application functioning? If it was an intended change, can admins have an option to allow API calls to override these types of lock outs?
Yes, this was an intended change to the API as deleting and modifying restricted tabs in the v2 API was seen as a bug.
I'm performing a DocuSign integration with a FileMaker solution to send signature requests via email, and receive a copy of the signed document once completed. I'm using the Java SDK to email signature request, as well as a Javalin app process to listen for the completed signature event, as well as more Java to pull the document back into FileMaker.
When the completed document is sent to my listener and pulled in, the document lacks a signature and tab field. It essentially looks just like the pdf document before being sent.
I have a feeling there's a variable I can tweak in some object to allow the signature to appear after being signed. I've played with all the usual suspects (e.g., eventNotification.setIncludeDocumentFields("true")), but nothing seems to do the trick. Any hints?
Aside from looking through the code for every object I'm instantiating and trying different variations, it's hard to pinpoint the exact source of failure in this. Thanks for any leads!
Sounds like you're receiving notifications by either including the eventNotification object in your Envelopes::create call or are using Connect at the account level. Either way, that's great, that's exactly right.
You can request notifications at many different points along the processing route of the envelope. To receive signed documents, you'll want the notification when the envelope is completed. At that point all signer recipients have signed.
To receive the notification when the envelope is complete, either adjust your Envelope Send parameters (the eventNotification value) or the settings for Connect (via the Admin tool), whichever one you're using.
I'm trying to create the following workflow for one signer in DocuSign :
- The signer access to an embeddded view of DocuSign. In this view, he can see the documents, refuse to sign or ask for more information but he can't sign anything or complete any field.
- He then clicks on "Finish", is redirected to my application.
- In my application, he has several steps to pass into (like giving bank information).
- Then, he can finally access to another emebdded view of DocuSign where he can sign, refuse to sign or ask for more information.
Today, I do not know how to make step 1 (visualisation without signing). Do you have any idea or solution to achieve this step ?
I'm aware of the "Certified copy" role but it's not what I want : a certified cannot refused to sign or ask for more information.
I've tried to simply define no tabs for this signer (both signer.setTabs(null) and signer.setTabs(new Tabs())). But DocuSign gives the possibility to the signer to add every field he wants, where he wants. Of course, it isn't the behaviour I'm looking for.
I'm using the REST Api in Java.
Even though a recipient may be defined as a "Signer" role, that does not necessarily mean there needs to be a signature/initials tab on the document. I'd recommend adding the desired optional/required fields, and do not specify any signature tabs. Once all required fields have been met on the document the signer/recipient will be able to hit Finish.