1. After you related eSign Doc to the object and added the related list to the object page layout, open a record of that object that you want to test it on.  We related eSign Doc object to the Opportunity object to show as example in this documentation.
  2. To send a new document for signature, go to a record you want to send a document for signature for, go to the related list of eSign Doc and click “New” button.  You can also go to the tab “eSign Doc” under more tabs “+” sign on tab bar and then click “New” button.
  3. On the Send Document page you will fill in the following information to send a document for signature.  (Later we will explain how you can pre-populate all these values automatically with a custom button/link).
    1. Google Doc ID – enter the google doc id of the google doc you want to send for signature:
      1. If you are looking at your Google Doc the ID is the text after “https://docs.google.com/document/d/” and before the “/edit”:
    2. Send From – by default the sender of document will be set to “current user” which is typically the eSign doc owner that created the document. You also have the option to change the sender to be from “org wide email address” if you have configured this feature in your Salesforce. That way when the recipient receives the email for with eSign document, the sender address will show the org wide email address/company display name.
    3. Send To – Select to send the document to a contact or to a lead. Defaults to Contact. in your Salesforce via the lookup icon that you want to send the document to, the “Recipient”.
      1. Send To Contact – If you’ve chosen to send the document to Contact in Send To field, this lookup filed will be displayed. Select a Contact in your Salesforce org via the lookup icon that you want to send the document to, the “Recipient”.
      2. Send To Lead – If you’ve chosen to send the document to Lead in Send To field, this lookup filed will be displayed. Select a Lead in your Salesforce org via the lookup icon that you want to send the document to, the “Recipient”.
      3. If you do not select an existing Contact or Lead recipient in the Send To Contact/Lead fields, then you can utilise the following fields in replacement:
        1. Email To Name – If you don’t select a Contact/Lead record in the Send To Contact/Send To Lead, then you can also just type in a name of a person to send the document to.  Type the full name  in this field and then use their email address in the “Email To” field below.
        2. Email To – If you don’t select a Contact/Lead record in the Send To Contact/Send To Lead and typed in name for the “Email To Name”, then you can also just enter an email address of the person to send the document to.
    4. CC – enter any other email addresses separated by a comma (no space in between email addresses) that you wish to CC on this email.
    5. Counter Sign Method:
      1. Defaults to No Counter Sign Needed.
      2. Counter Sign Required – Select if you want this document to be counter signed by someone at the company after it is signed by the recipient.
      3. Auto Counter Sign option allows you to automatically countersign the document after it’s signed by the recipient.
    6. Counter Signed By User – If you select Counter Sign Required or Auto Counter Sign, then here you select the User in Salesforce who needs to counter sign the document.
    7. Email Template – optionally you can select an email template you have previously created to be used to send this document.  Find out how to configure an email template with proper merge fields in Configuring Email Templates section below.
      1. If your template does not have the proper code to include the eSignature link, then this merge code will be automatically added to the email body.
      2. If template is selected then the Subject and Body will be populated.  You can use the button “Email Preview” to preview the email with the fields merged.
    8. Subject – If template was not selected, you can enter an email subject here.
    9. Body – If template was not selected, you can type the email body manually here (as plain text, or paste HTML code).  If you chose to do this, make sure you have the eSignature link {!esign__Document__c.esign__eSign_Link__c} merged somewhere in the email body so the recipient can have the link to click to sign the document.  You can put this link in any way you want with link text like “Sign Here” or with an image button clicking to the link. See Configuring Email Templates section below for examples.
    10. In the Related Records section you can select the record that you want to relate this e-signature to. It will only display the fields for the objects that you previously created lookup fields for (from Step 3 of Configure for Standard or Custom objects).
      1. If you clicked this from a record that eSign Doc is related to, then the record will be pre-populated.
      2. Check the box for Update Related Records if you want to update signature fields on the related record automatically. Please refer to Updating Related Records with Signature Fields section below for instructions on this feature.
  4. Click “Send for Signature” button at the bottom.
  5. Now the email will be sent to the recipient and the eSign Doc record is created with a Signature Status of “Sent”.
  6. If the recipient opens the email, then the “Email Opened” will be updated with that date/time they opened the email and the Signature Status will be changed to “Delivered”.  This gives good visibility and ability to followup if never opened.
  7. The recipient will click the link/button in the email body to sign.
  8. If they click the link and open the document, then the Signature Status automatically changes to “Opened” and the date/time is recorded in “Document Opened”.
  9. When they click the link, they will go to a web page unique to this eSign Doc and display the Google Doc for review.  They have button to download a PDF of the Google Doc or to Comment on the Google Doc.
  10. If ready to sign, they will fill out the fields at the bottom to enter their full name, company, title, and email and then click “Accept and Sign” button once complete. They will receive an error message in red if they do not fill out one of the required fields.
    1. Title And Company Not Required: You have option to remove the required fields “Title & Company” if you do not want recipient to provide this information. You can setup a workflow or process builder to auto check this checkbox field “Title And Company Not Required” each time new eSign doc is created. Or if you wanted to remove these fields for one some eSign doc documents, you would need to check this box after eSign doc is created and before recipients signs eSign document.
  11. Recipients also have option to”Draw Signature” and then draw their signature using mouse or touch pad on tablet. Once you finished drawing your signature, click the “Apply Signature” button and the image of signature will merge into signed eSign document. This is not required by default and signer can just manually type in name to sign document.
    1. Hand Signature Required: You have the option to make a “Hand Signature Required” that is an available checkbox field on eSign Doc record. If you would like to force all signing recipients to draw their signature,  you can setup workflow or process builder to check this value each time new eSign doc is created.
    2. Hide Hand Signature: You can also optionally hide the hand drawn feature by checking box on eSign doc record called “Hide Hand Signature.” If you would like to hide the hand signature option from all signing recipients,  you can setup workflow or process builder to check this “hide hand signature” each time new eSign doc is created.eSign doc settings and draw signatureExample of Drawn Signature:

Draw Signature (2)

Example eSign Doc with French Language:French Translation (2)

  1. Optional Feature: If you want to restrict the recipient from being able to “comment” on the document entirely, you can  create a workflow or Process Builder to auto check box “Disable Comment Button” when a new eSign doc is created.  If you only want to do this manually for some eSign doc records, you would need to check this box after eSign doc is created and before recipient signs the eSign doc document.
    Disable Comment Button
  2. If they click the button to sign, then the Signature Status changes to “Signed” and “Recipient Signed” date/time is populated
  3. Salesforce User who sent document (typically eSign doc owner) will be sent an internal notification when document is signed by recipient with existing email template/workflow that comes with installed package:
    1. “Document Signed by Recipient Notification” Template: You can edit the existing email template “Document Signed by Recipient Notification” that came with installed package or you can create a new email template if you would like, make sure to include the field that will link back to eSign doc record: {!esign__Document__c.Link} somewhere in body of template and refer to  Configuring Email Templates section below for additional instruction on formatting merge fields.
    2. Workflow “Document Signed by Recipient:” You can edit the workflow action “Email to document owner”  to update the email template to a new one of your choice per step above. Or you can also create a new workflow if you do not want to use existing actions in this managed workflow “Document Signed By Recipient” that came with installed package. Make sure to activate any new workflow and deactivate those that are not in use.
  4. If No Counter Sign was needed, then eSign Doc Signature Status will be changed to “Signed”.