This article will show you how to merge signatures into the body of a signed document, either by using merge signature fields or merging the image of a drawn signature. Please note that this feature is only available if using Opero Documents with Opero Signature for full automation.

Prior to setting up this feature, you should already be generally familiar with the fields on the eSign Doc object, especially the Merge Signature fields and how to use them. If not, check out our About the eSign Doc Object article.

Article Contents:

• How to Merge Signature Fields
• How to Merge the Image of a Drawn Signature
• Table of Merge Fields

How to Merge Signature Fields

This configuration adds signer information into the body of the signed document.

• Copy and paste the desired merge fields into the Google Doc template.
• Adjust the font settings as desired, e.g. to make it appear more like handwriting or underline to show signature placement.
• Change the font color of the merge fields to white so that the merge fields will be invisible to the recipient.
• After the document is signed and the PDF is created, the text color will change to the color specified in the Signature Merge Field Color field of the eSign Doc record.
• Once signed, the PDF on the eSign record shows the names of the people who signed the document where these merge fields were defined.

How to Merge the Image of a Drawn Signature

This configuration adds an image of the Signer and Countersigner drawn signature into the body of the signed document.

• Copy/paste into the Google Doc template the merge fields for Signature Image and/or Countersigner Image fields.
• As explained with merging signature fields,  the font color of all merge code in the Google Doc template should be set to white. This ensures that the merge code is invisible when sending the document for eSignature. Once the document is signed and PDF is created, the image will be displayed on the document.
• Important Note: To control the size of the drawn signature image when it is merged, place the merge field inside an inner table and set the column width to a value such that the inner table appears small enough to fit within the outer table (see example below). By defining the column width, the merged image will be resized to fit within that column width. To do this, go to Format>Table>Table properties. Select “Column width” checkbox and set value (e.g. “3” or “3.25”). Make the table border color white so that the borders are not visible within the template and to the signer.
• If choosing to merge the Countersigner Image, you will additionally need to configure the following:
  • There is a URL field on the User object called Hand Signature Image URL. Add this field to  the page layout of the User object.
  • The Salesforce user who is the countersigner will paste the URL to their drawn signature image into this field on their user profile.
  • The image file must be a publicly available URL to the direct image. At this time, the field only supports merging a publicly available URL from a Salesforce Documents file (Classic only). For details, see Opero Documents Template Configuration article. Under the “Merge Images”, section see “Documents (Classic Only)”.

Example nested tables to control the size of merge images

Table is shown with black borders so that you can see the configuration. Normally the borders of the nested table and the merge fields would be set to white. 

Example of drawn signature images merged into a signed PDF document

Table of Merge Fields

Listed below are merge fields that you can add to your Google Doc template to show signature information. All information about each field and its features is reviewed in About the eSign Doc Object.

Field	Description
Signed By	{!esign__Document__c.esign__Signed_By_Name__c}
Signed By Name	{!esign__Document__c.esign__Signed_By_Name__c}
Signed By Title	{!esign__Document__c.esign__Signed_By_Title__c}
Signed By Company	{!esign__Document__c.esign__Signed_By_Company__c}
Signed By Email	{!esign__Document__c.esign__Signed_By_Email__c}
Countersigned By	{!esign__Document__c.esign__Counter_Signed_By__r.Name}
Countersigned By Name	{!esign__Document__c.esign__Counter_Signed_By__r.Name}
Countersigned By Title	{!esign__Document__c.esign__Counter_Signed_By__r.Title}
Countersigned By Company	{!esign__Document__c.esign__Counter_Signed_By__r.CompanyName}
Countersigned By Email	{!esign__Document__c.esign__Counter_Signed_By__r.Email}
Countersigned Date	{!esign__Document__c.esign__Counter_Signed_Date__c}
Email To Name	{!esign__Document__c.esign__Email_To_Name__c}
Email To	{!esign__Document__c.esign__Email_To__c}
Created By Date	{!esign__Document__c.CreatedBy.Name}
Created By Title	{!esign__Document__c.CreatedBy.Title}
Created Date	{!esign__Document__c.CreatedDate}
Owner Name	{!esign__Document__c.Owner.Name}
Owner Email	{!esign__Document__c.Owner.Email}
Doc Link	{!esign__Document__c.esign__Doc_Link__c}
eSign Link	{!esign__Document__c.esign__eSign_Link__c}
Signature Image	{!esign__Document__c.esign__Signature_Image_URL__c[IMAGE]}
Countersigner Image	{!esign__Document__c.esign__Hand_Signature_Image_URL__c[IMAGE]}