• Install and configure A5 Documents to generate the Google Docs based on your template.
    • On the Document Action record that you wish to configure to send for signature:
      • Configure fields in sections: Information,  Properties of Merged Document in Google Drive, and Properties of Merged Document as directed in A5 Documents Documentation.
      • In Email section set Email To, Email CC, and Email Template.
          • The Email to field will be a merge field that will link to primary contact or lead ID. You can review more detail in this article for how to configure your email to field.
          • When selecting email template to use in document action, you can use the email template we include with A5 Signature installed package “send for eSignature” or if building your own, remember to include {!esign__Document__c.esign__eSign_Link__c} link in email body to allow recipient to sign a document.

        Example shown below for email section in document action for automation:

          • Send for Signature Action – set to Preview to see the document before you send it or Autosend to automatically send the document for signature.
            1. If you configured an automation method for mass document generation like Process Builder method mentioned above, it is required to use signature action “autosend” and not set to “preview.”
          • Parent Lookup Field Name – this field should be populated with an API name of a lookup field on the eSign Doc object. Parent Lookup Field Name is used to relate the eSign Doc record to an object of your choice and is a required field to populate in document action when setting up automation.
            1. A5 Signature package already comes with lookup fields to Account, Contact and Opportunity, so if you want to relate eSign Doc to one of these objects, you can use those default lookup fields from eSign custom object that you can use for Parent Lookup Field.
            2. If using an object other than Account, Contact and Opportunity (standard or custom), you will need to create a lookup field to that object from the eSign custom object.
            3. From setup menu, go to the eSign custom object and find the lookup field you would like to use or just created.
              1. Find the Field label name of the lookup field you would like to use. For example, if using Opportunity, you will see that the field label name is “Opportunity” and this is what you paste into field on document action.
              2. Important: Target field API name should be left without “__c” suffix, if you’re using a custom field. For example, if you’re using a custom lookup field to Opportunity whose API name is “Signature_Opportunity__c”, you should use the following format: “Signature_Opportunity”.
          • Counter Sign Method – set similar to the logic explained in the previous section.
          • Counter Signed By – set to user ID that will need to countersign the document (for example: a0BE000000h3258), or use a button merge field to merge ID dynamically (for example: {!Opportunity.OwnerId}).In eSignature Section:

        Example shown below for eSignature section in document action for automation:

        • Option to merge signatures into eSign Document with Full Automation – if you would like to merge signatures with automation, select option to “autocountersign” in document action under eSignature section and review this article for setup of merging signatures into your google doc template.
          1. By default, the field “Merge Signature Fields” on eSign doc record is unchecked when new record is created. If you would like to automatically merge signature fields with every new eSign doc record, you can create a workflow to to auto check this field each time new eSign doc record is created.
        • Additional eSignature Field & Additional eSignature Value – these fields are optional. Here you can pass additional lookup field values to eSign object that you created. For example if in addition to your Base/Parent object, you also created another lookup field on eSign object that you wish to pre-populate, you will indicate it in these fields.
          • Additional eSignature Field – write the lookup field label here. For example: if you created a lookup field to Account on eSign object that is called Client, then you will write “Client” in this field  (if your field label consist of 2 words, make sure to include any underscores between words, but leave off the end of label “__c” part). For example if your field label is “Sales_Order__c,” you would use “Sales_Order.”
          • Additional eSignature Value – populate the value you wish to pass into Additional eSignature Field with the button merge code for this field from your Base/Parent object. For example: our Base/Parent object is Opportunity and additional field is Client which is a lookup to Account, then we will set this field to {!Opportunity.AccountId}.
            1. NOTE: If you would like to pass value of picklist field into your custom button code, you would use the eSignparam value (in this example with a two word custom object, it would be “Sales_Order”) and then use the text of a picklist value, removing the quotation marks and DO NOT use underscores between words.
          • 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.
    • Once document action is saved, a button/link formula code will generate at bottom of document action. You can then use the button code provided to add the button/link to your page layout or a formula field so you can click on the record and generate the Google Doc and send for signature using A5 Documents in one click.

Example shown below for Button/Link formula in document action for automation:

  • You can also setup an automation method like Process Builder for mass document generation rather than using custom button and configure the process to trigger related document action you created. 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.