This article reviews how to configure the eSignature section of a Document Action, which allows you to use both A5 Documents and A5 Signature for full automation. Prior to this, you will need to complete the steps covered in the A5 Documents Basic Configuration article, up to the eSignature section of step 5, Create Document Action.

Section: eSignature

Field Description
Send for Signature Action Picklist that specifies how to send the document for signature.

  • Autosend – Automatically sends the document for signature. If you’ve configured an automation method for mass document generation, you must set the Signature Action to Autosend.  
  • Preview – Allows you to see the document before you send it.
Parent Lookup Field Name Populate this field with the API name of the lookup field on the eSign Doc object that relates the eSign Doc object to the base object (e.g. where your merge button is located). By default, the eSign Doc object is already related to the Account, Contact, and Opportunity standard objects, so you can use those pre-existing lookup fields for the for Parent Lookup Field. Otherwise, you can relate the eSign Doc object to any standard or custom object in order to send documents related to a record on that object.

Important: If you’re using a custom field, the target field API name should be left without “__c” suffix. For example, if you’re using a custom lookup field from eSign Docs object that looks up to Opportunity whose API name is “Signature_Opportunity__c”, you should use the following format: “Signature_Opportunity”.

Countersign Method Picklist that shows the countersign method. Set to indicate whether anyone in your company needs to countersign the document after the recipient signs in order for it to be valid.

  • No Countersign Needed
  • Countersign Required
  • Auto Countersign

If you would like to merge signatures with automation, select Auto Countersign option and review the Signature Merge section of the following article : About the eSign Doc Object

Countersigned By The user who will need to countersign the document. Can be the hardcoded User Id or button merge field to merge the Id dynamically, e.g. {!Opportunity.OwnerId}.
Additional eSignature Field

&

Additional eSignature Value

Optional. To pass additional lookup field values to the eSign Doc object, write the lookup field label here, e.g. Account. Then, populate Additional eSignature Value with the button merge code, e.g. {!Opportunity.AccountId}.

You can keep passing additional variables like this pair if you have more fields that you wish to pre-populate.  To do that you will need to manually add  parameters to your button code after you create your button. You can keep adding parameters with number like &esignparam3= for the field and &esignparamvalue3= for the value. Start with “3” because 1 and 2 are already used for Parent Lookup field and Additional eSignature fields.

Witness Required Checkbox field to indicate whether a witness is required.

  • See this article for more information: Witness Signer Feature
Signer 2 Name Second Signer’s name.

Signer 2 Email Second Signer’s email address.
Signer 2 Email Template Record Id of the email template used to send eSignature link to Signer 2. Starts with OOX.

Each time you save the Document Action, the app generates custom button/link code in the Button/Link Formula section. You can use this button/link code to create a custom button/link or a formula field on your base object. This allows you to go to a record and click a button/link to generate the  document and send for signature in one click. For more detailed steps, see Create a Custom Button for Document Generation.

Important: After you configured the button or link to generate your documents, remember every time you make changes to Document Action record, you have to copy the new Button/Link Code and update your button or formula, as the changes will not be passed to your button or formula automatically.