Is there any way programmatically (using Java) to stop the signer from getting a notification and receiving the completed document?
I see an option in the user profile but I want to set it while sending an envelope.
You could use embedded signing. That way DocuSign would not know the email address of the signer.
You should also check with your legal counsel about your plan. Asking someone to sign a document and then not giving them a copy of it is unusual behavior.
Related
I have two problems with Docusign, first, always it sent the envelope with the same account, no matter who is logged always is sending using the same account, i don't know why.
Second, i want to change the subject and message, i am using the example for apex toolkit and i am using the template, but always it show the same subject Documents for your DocuSign signature.
https://www.docusign.com/blog/dsdev-sending-template-apex-toolkit
To change the subject of a message you can use the withEmail method and edit the emailSubject property. See the API reference for more details: https://developers.docusign.com/docs/salesforce/apex-toolkit-reference/envelope.html
Do your salesforce users have the DocuSign Sender permission? I'm thinking that could be the reason that envelopes aren't being sent from their account.
I have researched enough and went through the API and could not find what is the right object to set to not to let users download / print documents once they finish signing. All the documents are submitted using envelopeAPI and controlling all the eventNotifications via api.
Would like to control the following also via API.
Not to send completed email to the recipient.
Once the document is signed, the recipient receives an email as shown below.
What is tried so far -- Tried to change the Email preference for Api user and User and did not see
any difference in notification.
Disable download and print option for the recipient.
when the recipients finish signing they are redirected to a page as shown below.
If possible I would the recipients not be redirected to this. If not at least disable download/print
option.
As a matter of law in most jurisdictions, people who sign using an electronic signature must have the ability to view/download/print the signed document.
That said, you can use an embedded signing ceremony. In that case, you control the emails.
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.
I'm trying to do Embedded Signing and I want to send the email to the Signers myself instead of having DocuSign send it.
I've found this post:
Docusign email notification for embedded signing case
That describes two parameters. I have not been able to find the second one (Use Envelope Complete Email for (non-suppressed) Embedded Signers) in my testing account.
Is this option no longer available? Is there any other way to achieve the same result?
For embedded signers DocuSign will never send an email letting the signer know they have a document awaiting signature. The two emails that are sent can either be Signature Notification and/or Completion email. Signature Notification is sent to the signer immediately after signing, while Completion emails are sent all at once only at the end when the last signer completes the envelope.
The options are both still available in the classic UI under Preferences --> Features.
Update
If you are using the New DocuSign Experience then follow the instructions here
See the Document delivery section.
I am using the DocuSign API in an embedded manner. I create an envelope and add signers, the first signer always being set as embedded. This allows me to retrieve a URL that is then embedded in an iframe.
However, I also wish, to trigger an email (as soon as the envelope has been created, NOT upon completion) that gets sent to the primary recipient/signer as if they were a nonembedded signer.
I tried adding the signer twice, with the same role, to the recipients, but that didn't work. No email was sent.
Is there a way to accomplish this?
I believe there is a setting to enable this but that it needs to be enabled by someone on DocuSign's side, like your account manager. If you do not have an account manager yet please respond to the auto-generated emails that were sent out to you once you created your account, you should have 3 of them.
The account settings available are only for Completion emails. However, the REST API also supports an embeddedRecipientStartURL parameter on the signer object that triggers a normal DocuSign email. The value of this parameter is the URL that should be included in the email. This means you can link back to your own application and request the recipient view as normal.
Check here for more detail: Signer embeddedRecipientStartURL. Note: if you set this to a value of "SIGN_AT_DOCUSIGN" then DocuSign will provide its own URL and take care of signing. The trade-off is that you won't be able to initiate any bespoke authentication you are doing in your own application.