Not received email that was typed in textbox "Email Address" using dialog "Save your Copy" in "In Person" signing.
While signing the envelope in In-Person mode there is an window (popup) to send a copy of the document in an email. We have entered the email (many times and different email services) but no email received. Checked settings in the DocuSign portal account but not able to find any setting for this. Please let us know how to enable the save a copy email in DocuSign.
We using DocuSign SOAP API under C#.
For InPererson Recipient we add :
new Recipient
{
Email = "email of host recipient",
UserName = "name of host recipient",
SignerName = "name of current recipient",
ID = "id current recipient",
Type = RecipientTypeCode.InPersonSigner,
RoutingOrder = 2,
RequireIDLookup = false,
CaptiveInfo =
new RecipientCaptiveInfo {ClientUserId = "special id of current recipient"}
};
And we open docusign token url (RequestRecipientToken method) in new browser window without iframe we open it in IE 8-11 and Google Chrome
What we have to specify in addition to this , when creating and sending envelope or in account preferences of main account in docusign.com?
First, keep in mind that the email you're describing will only be sent upon Completion of the Envelope -- so if there are other recipients after the In-Person signer in the routing order for the Envelope, the In-Person signer wouldn't receive the email until all recipients have completed their required actions and the Envelope is complete.
Second, you might want to verify (in Preferences >> Features within the DocuSign web console) that these two settings are set as shown here:
These settings control whether or not emails are sent to "embedded/captive" recipients. Even though you're using "In-Person" signing -- it sounds like you're launching the host's signing session using "Embedded Signing" (i.e., RequestRecipientToken), so these settings might be affecting whether or not the email actually gets sent to the signer.
Related
I have combed through the DocuSign documentation but am unable to find a real world example.
I am looking for sample code that shows the InPerson signing flow via the docusign node client.
I am able to successfully create a new Signer and it works. I am unsure how to set that signer to InPerson.
let inPersonSigner1 = docusign.InPersonSigner.constructFromObject({
email: "enduseremail#domain.com",
name: "end user name",
hostEmail: "hostemail#doamain.com",
hostName: "host name",
recipientId: '1',
routingOrder: '1'});
// Add the recipients to the envelope object
let recipients = docusign.Recipients.constructFromObject({
inPersonSigners: [inPersonSigner1]});
env.recipients = recipients;
The rest is the same as any other envelope, you can find the remote signing example here.
Note that the host must have a DocuSign account and they need to log-in to host the signer.
My company is trying to avoid having many Docusign logins for the group (group X) using Docusign. We were wondering about using one login to do the create, but override the email settings to have it go to members of group X without them having to have Docusign credentials. I was wondering if that would be possible with the replyEmailAddressOverride.
You can do so by using the "Send On Behalf Of" feature where you specify an email address in the authentication header in order to "assign" each transaction to a specific person with the same and unique credentials.
{
"Username": "",//Email of Group X credentials
"Password": "", // Password of Group X credentials
"IntegratorKey": "",// Integrator Key of Group X credentials
"SendOnBehalfOf": "" // Email of the specific person to be assigned the DocuSign transaction
}
If I understand your question correctly, I am not sure that using the replyEmailAddressOverride feature will accommodate what you need.
From the official documentation, this email will be used when the user decided to "reply" to the email sent from DocuSign.
Example in C# below :
EmailSettings settings = new EmailSettings
{
ReplyEmailAddressOverride = "otherUserThanTheSende#fakeemail.com",
ReplyEmailNameOverride = "Other User"
};
envelope.EmailSettings = settings;
If you configure the above email settings, when the signer receives the DocuSign email inviting him to initiate the signing ceremony, if he/she decides to reply to this email, the original DocuSign sender email will not be used but instead the email you have configured will be used.
Example, my "Frederic "account was used to create a transaction so the sender appears as "Frederic" in the DocuSign email. However, when I decide to reply, it doesn't go back to "Frederic" but instead to the user I have configured in the envelope :
But if I understand correctly, you want to send a transaction from a specific sender and this email override setting doesn't affect the transaction sender but the transaction reply.
If you want to use replyEmailAddressOverride and replyEmailNameOverride as present in DS Docs then when an email goes to the signer from DocuSign and if they want to revert to that email then it will go the email which is mentioned in replyEmailAddressOverride property
Although the ‘Assign to Someone Else' action should send a notification to the Sender when the Recipient has used this option, we need a way to prevent recipients from using this action in the first place. Is there an option we can set when we create the envelope? Using REST.
Set the allowReassign Envelope property to false in the Create Envelope request to prevent recipients from being able to Assign to someone else. It's a top-level property of the Envelope object, a peer of emailSubject, etc.
POST https://ENVIRONMENT/restapi/v2/accounts/ACCOUNT_NUMBER/envelopes
{
"emailSubject": "Please Sign",
"emailBlurb": "Please sign this contract. Thank you!",
"allowReassign": "false",
...
"status": "sent"
}
You can disable the Reassigning Signing Responsibility at an account level by going to Admin -> Signing Settings and unchecking below options
Allow recipients to change signing responsibility
Allow senders to override change signing responsibility
If you uncheck both the settings then none of sender can set this setting neither from WEBApp nor from API. But you uncheck first setting and don't uncheck second then Sender can override the account level settings. So, if you want to disable this "Assign To Someone Else" feature then uncheck both checkboxes.
I am creating an envelope via the Docusign Rest API. this envelope has 2 inline templates each have their own roles and do not share any tabs. I have a custom workflow that requires the user to fill in each document separately so i use the (/views/reciepients) endpoint to get a signing url.
The first signer sees the first (and only the first) document correctly, it is filled in and completed. Then i want to show the second document from the envelope in an iframe to a user. When i get the signing URL for the second recipient (signer) it also includes the first document all filled out.
I have document visibility set up on the account.
I have read the documentation a few times and there is one confusing, under "Post Recipient View" there is a field "userName" which is not mentioned when creating the recipient or in the response from the recipient end point. I assume this is the "name" field.
to make it a bit easier to read i have put all the API requests into paste bin.
Generate Envelope with 2 templates and 2 signers.
Request = http://pastebin.com/e98Dwaj8
Get First signing URL using /envelope/xxxx/views/recipient
Request =
{
"returnUrl": "http:\/\/local.example.com\/return.html",
"authenticationMethod": "none",
"email": "role1#example.com",
"userName": "TestFirstName TestSurname",
"clientUserId": "1"
}
Get recipients for envelope after first signer has completed
Response = http://pastebin.com/9VmGsE3p
Get second signing url (this shows both documents when visited)
Request =
{
"returnUrl": "http:\/\/local.example.com\/return.html",
"authenticationMethod": "none",
"email": "test#example.com",
"userName": "TestFirstName TestSurname1",
"clientUserId": "2"
}
Is there a way i can show the second signer only the second document?
Is it possible or will the completed document always show? does the /views/recipient url only hide documents in "draft" or "sent" and always shows "completed"?
note: this is a follow up to Docusign signing url - Showing document 1 of a composite template but that question was answered and solved the original issue so i thought it best to open a new more specific question.
In order for certain signers to only see certain documents, you will want to investigate the Document Visibility feature and settings. There is some starting documentation available at: https://support.docusign.com/guides/cdse-user-guide-advanced-sending-using-document-visibility-in-a-template
In short, signers can only see documents in an envelope for which they have at least 1 tab assigned. This is honored during the signing ceremony as well as any view of the completed document.
Regarding your last question, you should only be able to start a POST /recipient/view (signing ceremony) for an envelope which has been SENT. If you perform this action against an envelope which is completed it will start the signing session in a read only viewing mode (since the transaction is complete).
Is the 2nd signer a member on the sending account? If so, they would be able to see all documents in the envelope based on "Must sign to view unless Sender Account". This setting essentially means internal signers that have memberships on the same account as the Sender can see everything.
I would like to preserve the Email Subject & email Message that are defined on the Docusign Template and send those vs sending generic email subject & message when sending a document via Custom Button in Salesforce? Below is my button code
{!REQUIRESCRIPT("/apex/dsfs__DocuSign_JavaScript")}
var DST='<Docusign Template Id>';
var LA='0';
var OSO = 'Send';
var CRL = 'Email~{!Fulfillment__c.Primary_Contact_Email__c};Role~Client;FirstName~ {!Fulfillment__c.Primary_Contact_First_Name__c};LastName~{!Fulfillment__c.Primary_Contact_Last_Name__c}';
var CCRM='Client~Client';
window.location.href = '/apex/dsfs__DocuSign_CreateEnvelope?DSEID=0&SourceID='+eSignatureNotSent.Id+'&DST='+DST+'&LA='+LA+'&CRL='+CRL+'&OCO='+OCO+'&CCRM='+CCRM;
I think Docusign is using Default Email Subject and Default Email Message defined in the Admin settings in Salesforce. I do not want to send it as all the work is done when building templates in Docusign.
If you leave the Default Email Message blank in the Admin settings, it will grab the contents of the Template Email Message.
The API has a hard requirement to define an email subject through the request. Currently because Salesforce uses the API, it has to follow this guideline.
My best advice is making a custom button that defines the Email subject that you'd like for each workflow that you may have.