We would like to archieve documents which don't have to be signed on docusign, is there a possibility to create an enveloppe as complete (skipping the signing part) in order to be able to directly create working view links ?
Thanks !
You cannot send and complete an envelope w/o recipients. A CarbonCopy will create and send and complete the envelope, but what do you mean by create working view links?
If you are referring to using the API to pull the completed documents then yes this is possible.
You could send an envelope with just one cc recipient. That cc recipient could be a blackhole email address on your system.
Related
It is possible to send document attachments by email, when send a document to sign? I need to attach additional documents that do not required a signature.
Thanks,
EV
You can use the SDK/API to add documents to an envelope, even if they do not require signature. You can even add attachment tabs via the API so that signers can add their own attachments. You cannot, as far as I know, add attachments to email messages generated by the DocuSign system.
Inbar is correct. In addition, you could send your own emails to signers (in any format you like), and include a link to the signing ceremony via your app.
See this article for more.
I am trying to implement embedded signing in our application. I followed the steps as mentioned in the guide - https://developers.docusign.com/esign-rest-api/guides/concepts/embedding
I am able to create the envelope, generate the recipient signing URL, use that URL to sign and complete the document. But I haven't received the completed signed document to the email that I mentioned as the Signer.
Is there any additional properties that I need to specify to receive the document signed via the recipient signing URL?
What is the other way to receive the signed document in this case, Can I use webhook to receive the completed document?
Yes, webhook is the better approach for this.
in Embedded signing there are no emails going to the signer. That's the purpose. Embedding it in your app unlike remote signing where emails are sent.
Your app can receive a webhook notification from connect and retrieve the complete document.
https://developers.docusign.com/esign-rest-api/code-examples/webhook-status provide some examples. There are other resources about how to use DocuSign Connect webhook.
There's an option for this in the esignature admin tool., Send completion emails to embedded signers
That setting is account-wide. So if your application is used by people in multiple accounts, you'll need to set it for each account.
We have bulk send feature on Docusign by which we can send the document to mulitple envelopes which would be signed by many from the list. So each of them would be getting their own copy of the document to sign. So, is it possible to download the document as the receipent(s) signed it. We can download the document with mulitple users and single sign document once it is completed by registering the webhook. Is it possible to get this in same way for bulk send also? Can we get the document one by one as the receipents from the list signs that ?
Thanks in advance!
Bulk Send generates multiple envelopes, each envelope for a CSV row, so DocuSign Connect will help you getting notified for each envelope.
Using DocuSign Connect, you can subscribe to Recipient Level Trigger events - For instace Recipient Signed/Completed, once any recipient signs the envelope then you will receive the notification from the DocuSign, on receiving the notification you can call DS API to download the document or you can include documents in the DocuSign Connect message itself if the document is not very big.
I am playing with a sanbox account for docusign. I have created a template in the sandbox website, and am using the API to generate envelopes using that template.
If I edit the document or template at the website after the email has been sent and viewed by signer 1 (but not yet signed), will it invalidate the envelope?
No, it will not invalidate the envelope. Once an envelope is sent it has all the information it needs to process towards completion, even if you modify or delete the template it was created from. The template is simply used to help streamline the sending process and once the envelope is sent there is no attachment to it or anything like that.
I'm trying to dynamically populate a non-signer CC role upon creating an envelope from a template using the REST API. Is this possible? Currently, when I add the "receive a copy" recipient role to a template and then set the email for that roleName in the code and send the document off for signing, it automatically "completes" the document which seems like a bug or it may be that I'm doing something that isn't supported? Can anyone help?
Thanks,
Janea
Ergin was correct. Using the API call to add the CC role as the envelope is created from the template works as expected. It did not seem to work initially but, not sure why.
Carbon copy recipients are unique in that that is the only recipient type that does not take any actions on the envelope. They simply receive a copy of the envelope when it's their turn in the routing order, they never see the "tagging" workflow (unless they are added as another signing recipient on the envelope at the same or a different routing order).
When you have a CC recipient and it is their turn in the routing order, nothing happens except that they receive the notification email. If they have the highest routing order out of all recipients (i.e. if they are the last recipient) then the envelope status will already be completed by the time it reaches them and it won't change status and will remain as complete.
Are there other recipients? If there's only a single recipient and they are marked as "receive a copy" or "CarbonCopy", and not marked as a "Signer" type, it will probably see the envelope as complete.