There are two ways you can add a signature into the body of signed document:

1) Using merge signature fields or 2) Merging the image of drawn signature into eSign document once signed by recipient.

NOTE: These signature features are only available if you also using our document generation app, A5 Documents app in your Salesforce.

For Merge Signature Fields:

  1. If you would like to merge signature fields onto your eSign document for “signed by” and/or “countersigned by,” you can merge the following fields onto your google doc template:
    a) Signed By: {!esign__Document__c.esign__Signed_By_Name__c}
    b) Countersigned By: {!esign__Document__c.esign__Counter_Signed_By__r.Name}
  2. You can change the font on these fields to look more like a signature font if you would like (or place an underline below these fields to show signature placement).
  3. Apply white color to the above merge fields on google doc template so that text is invisible when sending the document for eSignature (text is white/invisible so the recipient does not see the merge field when first signing document but once the document is signed and PDF is created, the text will change to a color specified in Signature Merge Fields Color field on eSign Doc object—the field supports hexadecimal value for the color, e.g. 000000 for black).
  4. You can add these signature fields to an existing google doc template you use to send documents for signature or add these signature fields as needed when creating a new eSign doc record.
  5. After the eSign doc is sent via email, go to the eSign doc record and check field “Merge Signature Fields” (add this field to eSign doc page layout if not showing).
    1. By default the “Merge Signature” field is unchecked after eSign doc record is created so you need to manually check it after the eSign doc is sent via email and before it is signed OR you can setup a workflow rule to auto check this field when new eSign doc record is created.
  6. Once document is signed, the PDF on eSign doc record should contain names of the people who signed Document where these merge fields were defined (should now show in black font after signed).
  7. Additional eSignature Merge Fields:  Here is a list of other possible eSignature fields you can merge onto your Google Doc template coming from eSign doc object:
    Who you are emailing the eSign document too:
    {!esign__Document__c.esign__Email_To_Name__c}
    {!esign__Document__c.esign__Email_To__c}
    Who signed the eSign document:
    {!esign__Document__c.esign__Signed_By_Name__c}
    {!esign__Document__c.esign__Signed_By_Title__c}
    {!esign__Document__c.esign__Signed_By_Company__c}
    {!esign__Document__c.esign__Signed_By_Email__c}
    Who countersigned the eSign document:
    {!esign__Document__c.esign__Counter_Signed_By__r.Name}
    {!esign__Document__c.esign__Counter_Signed_By__r.Title}
    {!esign__Document__c.esign__Counter_Signed_By__r.CompanyName}
    {!esign__Document__c.esign__Counter_Signed_By__r.Email}
    {!esign__Document__c.esign__Counter_Signed_Date__c}
    Which Salesforce user created the eSign doc:
    {!esign__Document__c.CreatedBy.Name}
    {!esign__Document__c.CreatedBy.Title}
    {!esign__Document__c.CreatedDate}
    Which Salesforce user sent the eSign doc they owned:
    {!esign__Document__c.Owner.Name}
    {!esign__Document__c.Owner.Email}
    Links to Google Doc Link & eSignature Link:
    {!esign__Document__c.esign__Doc_Link__c}
    {!esign__Document__c.esign__eSign_Link__c}

 

For Merging the image of Drawn signature into document:

  1.  This configuration will allow the drawn signature by signing recipient to be added into the body of the signed document using a merge field in your google doc template.
  2. In the google doc template being used with A5 Documents app, you need to copy the merge code for Signature Image URL field from eSign Doc record. The supported format is {!esign__Document__c.esign__Signature_Image_URL__c[IMAGE]}. This is the field where the drawn signature gets saved after the document is signed.
  3. As explained in the section above,  white color should be applied to the merge code in the google doc template so that text is invisible when sending the document for eSignature. Text will be white/invisible so the recipient does not see the merge field when first signing document but once the document is signed and PDF is created, the image will be displayed on the document.

IMPORTANT: As explained in previous section, for this or any other field to be merged after signing, Merge Signature Fields checkbox field on the eSign Doc object must be checked. You can setup a workflow rule to auto check this field when new eSign doc record is created.