Use Opero Documents with Opero Signature for Full Automation
This article reviews how to configure the eSignature section of a Document Action, which allows you to use both Opero Documents and Opero Signature for full automation. Prior to this, you will need to complete the steps covered in the Opero 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 send the document for signature. If you configure a document action for automation you must set the signature action to autosend. Preview – Allows you to see the document before you send it. Sign Now – Allows users to generate a document and serve for in-person signing. Note that this feature can only be used with automation. It cannot be used with preview. The following Document Action fields must be populated: Email Template, Email To. Note: Customers upgrading an Opero Signature package version older than 1.91 will need to create a new picklist value “Sign Now” (label) “Sign_Now” (API name). |
| 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. These pre-existing lookup fields are available for the Parent Lookup Field. Format these field as follows: “esign__Account”, “esign__Contact”, and “esign__Opportunity”. Otherwise, you can relate the eSign Doc object to any standard or custom object by creating a lookup field on the eSign Doc object to that object. This will allow you to send documents related to a record on that object. Once created, you will be able to select the lookup field from the dropdown menu. |
| Countersign Method | This is a picklist that shows the countersign method (No Countersign Needed, Countersign Required, Auto Countersign). Set to indicate whether anyone in your company needs to countersign the document after the recipient signs in order for it to be valid. If you would like to merge signatures with automation, select Auto Countersign option and review this 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. The param field should be without the suffix “__c” for custom fields. Note: 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. See this article for more information: Second Signer Feature |
| Signer 2 Email | Second Signer’s email address. See this article for more information: Second Signer Feature |
| 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.