I'm using the Docusign API and programmatically create the envelope and add recipients. The sender is then redirected to the sender view URL, adds initial and signature tags and then sends the envelope. Works great.
The problem is sometimes that once the envelope is SENT, the senders then realize they forget to add these tags for multiple recipient. I can always generate another sender view URL with no problem and redirect the sender. The problem is that it takes them to a sort of "read only" view of the document and they have to click on "OTHER ACTIONS" and then "Correct". From there they can modify the envelope somewhat and the recipients and then click a button that reads "Edit Documents and tags" to get back to the original sender view where you place the signature tags.
Once an envelope is sent, is there any way to correct it like this but SKIPPING this "correction page" and going straight back into the view where you're actually placing the tags? Our web application does all the recipient adding and envelope creation. We don't want our users to be able to have any advanced options and possibly mess up the envelope.
Yes, you can use createCorrect API call for the sent envelope, API call is
POST /v2/accounts/{accountId}/envelopes/{envelopeId}/views/correct
More details are available at https://docs.docusign.com/esign/restapi/Envelopes/EnvelopeViews/createCorrect/
This call will directly open the envelope for editing.
Related
I've successfully created DocuSign envelopes with a single button click from Salesforce through REST API by auto-populating documents, recipients and Document Visibility settings through this API call.
In order to achieve this, Document Visibility settings has been set to "Must sign to view unless Sender". Hence this section can be edited by any sender. The Document Visibility section in the Draft envelope should be locked/hidden for specific senders.
Is there any feature available to achieve this in New DocuSign Experience? Can this done through Apex REST API?
Any suggestions please?
No you cannot disable Document Visibility for the sender of an envelope. Since you are using API integration, you can send an envelope using API credentials and add the requestor of an envelope (logically a sender) as first recipient in the routing order as CC recipient. This way requestor can monitor the envelope but will not do any activity on an envelope including Document Visibility.
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.
I'm using the Docusign REST API. I've created an envelope with multiple recipients and I've retrieved the sender URL to open up the web consult to place signature/initial tags.
Is there any way with the API to not allow the sender to actually SEND without dragging at least one signature tag per recipient?
Re: Is there any way with the API to not allow the sender to actually SEND without dragging at least one signature tag per recipient?
Not specifically. But here are some ideas to improve the situation:
Include signer tabs for the sender
As part of creating the envelope, include a signer recipient tab for each of the recipients. Then the person editing the document would simply move the tab around on the screen rather than having to drag it over from the tab toolbox on the left side.
Give more responsibility to your integration application
Enable your integration to have more control over the business process and therefore not show the "sending screen" to the sender. This way, your senders spend more time interacting with your app, and your app has more control over the situation.
For example:
If only a couple of document types will be sent, enable the sender to choose the document type and to fill in its parameters via your app. Then you can send the document out for signing and your app can place the various tabs.
Or when the sender uploads a document to your app, you can check the document for anchor text such as "//signer1//" Then, your app adds a signer tab with anchor text //signer1//. See this recipe.
Or enable the senders to upload docs, but use a standard "Signing page" that your app will append to all of the envelopes. When the signer signs, the extra doc (the signing page) looks as a continuation of the prior docs in the envelope. Your app would auto-generate the signing page, including the signature tabs on that page.
If you can, I would recommend that you not enable people to upload docs. (Or maybe just attachments to the main docs). Instead, reach agreement with the business process owner on what are the possible docs that can be sent. Figure out the best format for each, and enable your app to auto-generate the docs based on inputs from the senders and from other business databases/apps.
I am using DocusignAPI, I do want to view the envelope like recipient view. I searched for the "Post Recipient View", this can be done only for the sent envelope. In the "Post Envelope correction" I am able to see the tags and also able to delete/reupload the documents. I would like to view only the documents with their prefilled tag values. Is there any option to do this?
You can try the various DocuSign recipient types. For instance, there is the carbonCopy recipient who doesn't take any action on the envelope but just gets a copy and they can be inserted at any routing order in the envelope.
There's also some of the other recipient types with various permissions that can change recipient info for people who are later in the routing order, such as the agent and intermediary recipient types.
See this page from the REST API Docs
We need to be able to handle a scenario where the document PDF needs to be updated and resent, after the envelope is In Process. Do we always need to create a new envelope or can we reuse the current envelope ID?
Our process goes roughly like this:
A PDF document is generated (not using a DocuSign template).
We create an envelope for the document PDF.
The first signer (our employee) signs the document (using an embedded signing page).
The other signers sign the document (also using an embedded signing page).
Firstly, we want to know if we're forced to incur another "sent" envelope (i.e. we're billed) every time we want to update a document PDF. Secondly, we're looking for a clean way to implement updates, without the need to manage multiple envelopes.
Yes you will unfortunately have to make a new envelope if you want to make changes to the underlying document(s) of the envelope after it has been sent. This is actually a fundamental part of the service and the reason is not to make you incur a new envelope - instead it's actually a security / legal requirement.
Imagine that we are in the old world and I need two people to sign a document on paper. I have the first person sign, then before the second person signs I make a change to the document that says the first person owes me $1,000,000. Then the second person signs, the document completes, and now you have a signature from both people but it contains content that the first person did not actually agree to (and they apparently owe you $1,000,000 now!). That's the main reason why you can't change the underlying document once it's been sent.
Two possible workarounds I can think of:
1. Add data fields or other Stick-eTabs to the envelope for the parts of the document that might change.
2. Use the signer attachments tab to add additional documents.
For #1, let's say you send out a sales contract for $100,000, but after it's been sent a new price is determined. If the $100,000 is in the document content itself then you can not edit it and you'd have to create a new envelope with the new document; however if it's through a Data Field then your recipients can simply edit the value as the document works towards completion.
For #2, there are special Stick-eTabs you can add called Signer Attachment Tabs which allow recipients to attach whole documents and other files to the envelope. You could utilize this to add your changes to the envelope.
Is there a human involved in updating/replacing the document, or are you looking to fully automate the process with the API? As Ergin stated, it's not possible to add/remove documents using the API once an Envelope has been Sent. However, it IS possible for the Sender of the envelope to "Correct" (and re-send) the Envelope using the DocuSign web console -- including adding or removing documents for an Envelope that's already been Sent, but documents can be ONLY be removed/replaced IF none of the recipients have yet acted on the Envelope. i.e., once at least one recipient has acted on the Envelope, it won't be possible for the Sender to remove/replace documents in the Envelope (although they can Add new documents, as long as the Envelope is still in-process).
You can use the API to launch the "Correct Envelope" view as follows:
POST https://demo.docusign.net/restapi/v2/accounts/{acctId}/envelopes/{envelopeId}/views/correct
The response to this operation will return a URL that you can use to launch the "Correct Envelope" view.
Finally, one important caveat about using the "Correct Envelope" feature to enable the Sender to modify documents in an envelope: once the person is logged into the DocuSign web console where they'll correct the envelope, they'll have full access to that user account in the DocuSign web console -- i.e, they'll be able to access all Envelopes in that user account (Sent Items, Inbox, Deleted Items, etc.), send new Envelopes, access user settings via "Preferences", etc. So, be careful using the Correct view if you're concerned at all with providing the person with full access to that user account within the DocuSign web console.
Note: In order for the Sender to be able to add/remove Documents in the "Correct Envelope" view, the "Advanced Correct" feature must be enabled for the DocuSign account (in Preferences >> Features).