Here is my problem with creating envelope with signers’ order.
If I create the envelope using Docusign console and enabling Set signing order like this:
Then the pdf will be sent to the second signer like this which is OK:
BUT,
If I create the envelope by REST API call like this:
Then the pdf will be sent to the second signer like below and the second signer cannot see his signhere or text tabs:
Would you please advise how to fix this?
Thanks.
I don't see the tabs in your code. But using the API, when you add the tabs, you have to make sure they match the correct recipientID and correct routingOrder.
How did you add the tabs? please provide JSON/code for that, the issue is in there.
Related
I have a PowerForm with a text field that is pre populated via URL. I can see the field’s contents when signing. But when I look at the data received by the webhook, the text field and its value are not sent. I am using webhook.site for testing. Your ideas are welcome!
I’ve tried including the PowerForm in the webhook. Doesn’t make a difference either way. All I really want from the webhook is this one text field. I don’t even need the signer.
To get the value of a tab in a Connect publish, you'll need to go to the Include Data section and enable both Recipients and Tabs.
A little bit of background as to what my goal is and why I need to get the email from the Template (just in case there is a better way):
I added three signers to a docusign template I created, one who is supposed to get the information from my code and two who I have entered their info directly into the email fields. My issue is that when I look at the SDK/API I don't see a way to add the missing email\name and use the default information I added in the Docusign dashboard for the Template.
The solution I came up with was to get a list of the signers from the Template (to add them to the Envelope), but I am not seeing a way to do that in their documentation. Any help provided would be greatly appreciated!
You can get the list of signers from the template using below call
GET /v2/accounts/{accountId}/templates/{templateId}/recipients
Details are available at, TemplateRecipients: list.
Sign at Docusign
As per the above thread, it is possible to retrieve Signing console URL for email recipients too by setting EmbeddedRecipientStartURL property to value "SIGN_AT_DOCUSIGN", As per the documentation(Sign at Docusign), below example has to be framed in order to open Docusign Signing console.
http://senderHost/[[mergeField1]]/beginSigningSession?[[mergeField2]]&[[mergeField3]]
Please explain what is senderHost & what should be filled in the mergeField properties accordingly? Let me know if you need any additional information related to this query.
BVS, I believe that's the opposite. If you provide EmbeddedRecipientStartURL field with SIGN_AT_DOCUSIGN, the signature will happen completely on DocuSign, and you don't have to provide any URL or merge fields.
If the value SIGN_AT_DOCUSIGN is used for this node, the recipient
will be directed to an embedded signing or viewing process directly at
DocuSign.
On the other hand, if you want to route the client through your own application BEFORE he or she goes to DocuSign, you could provide this kind of template URL with merge fields to better handle the request.
Information can be appended to the embeddedRecipientStartURL using
merge fields. The available merge fields items are: envelopeId,
recipientId, recipientName, recipientEmail, and customFields. The
customFields must be part of the recipient or envelope. The merge
fields are enclosed in double brackets.
By example: if you wanted to handle the request before the signer goes to DocuSign, you could send something like https://senderHost?envId=[[envelopeId]]&email=[[recipientEmail]]. Sender host is your host, so it can be anything on the internet (www.yoursite.com, by example).
Hope it helps!
I have been trying merge DocuSign in my application to make the user sign the documents I upload. Currently DocuSign allows us to add the signature tag at a static location, where we can provide the co-ordinates programmatically.
I would like to have a functionality where the signer can move the Signature tag anywhere over the page and insert the signature at the selected location.
Is there any good way to do this using DocuSign API's. Are there any DocuSign API's currently which do this?
Can anyone help me with this?
You want the signer to have the ability to dynamically position where the signature will go? Just send the document with no tabs at all and the signer will be asked to select the type of signing field (signature, initials, date, etc) and then choose its placement.
However, this is typically not a good UI. Instead, it is better for the sender to pick where the signer should sign. This can also be done dynamically using the "Sender View."
Not entirely sure about the part where the signer can move the tabs. But Anchor-Tabs sound like something that might help. I have asked a question on it a few minutes ago with sample code.
DocusignApi - Attachment with SignHere tab on the third page
The following link might also help.
DocusignAPI - Sign here tabs
Looks like we can delete recipient in the REST API but is there a method in the SOAP API that will allow deleting recipients?
Currently we are calling CreateEnvelopeFromTemplatesAndForms() from the SOAP API to create the draft envelope. The template may have multiple recipients and some of them may be optional. Before we can send the envelope by setting ActivateEnvelope to true or calling SendEnvelope(), seems like all the recipients' info (i.e. name, email, etc) must be filled in, otherwise the call will throw an error "...email address is invalid...". So we would like to delete the optional recipients when they are not needed.
Can we somehow define an InlineTemplate for the CreateEnvelopeFromTemplatesAndForms() call to delete recipients?
We also looked at CorrectAndResendEnvelope(), seems like we can edit recipient info but not delete.
Thanks in advance!
No, there is no SOAP equivalent for deleting recipients. This is one of the reasons why DocuSign's REST API is encouraged over the SOAP API, and this feature gap is growing with every monthly release.
Three workarounds I can think of:
Use a recipient type like Editor or Agent to edit the recipient info after envelope has been sent.
Instead of deleting optional recipients, only add them later in the process if needed.
Use REST to delete your optional recipients.
For #1, there are recipient types like Editor, Agent, or Manage Recipients which allow you to edit the recipient info of recipients that are later in the routingOrder.
For #2, instead of adding your recipients at the beginning, only add the required recipients then at a later time if it's decided that optional ones are needed, add them through a Recipient Correction/Addition.
For #3, the nice thing is that you can intermix the APIs, and make some calls in SOAP and others in REST. The only thing you'd have to do is write code to send a REST request and parse the response.