Page tree
Skip to end of metadata
Go to start of metadata

DocuSign Tables Overview

DocuSign is an e-signature provider that offers secure electronic signatures for digital documents.   Agiloft's API is compliant with all DocuSign and e-signing requirement standards, provides embedded integration with DocuSign. Before configuring the   Agiloft interface to use DocuSign, you need to set up a DocuSign account. You can connect multiple DocuSign accounts to a single KB. 

To use DocuSign with   Agiloft, you need a Business or Enterprise license for at least one DocuSign user. A DocuSign administrator account is required to complete the initial configuration within  Agiloft. Anyone in   Agiloft who sends a contract document for a signature via DocuSign needs a corresponding DocuSign user account.

Turning on the DocuSign extension creates several tables, fields, and actions in   Agiloft. The Standard System Demo has been preconfigured with DocuSign to the full extent possible without a DocuSign production account, so these tables, fields, and actions already appear by default. 

Visit the DocuSign website to read FAQs and whitepapers, watch How-To videos, and learn more about the e-sign infrastructure. For full details on how to complete the configuration of DocuSign in order to deploy it in   Agiloft, please review the DocuSign Users Manual. The manual gives a full, detailed overview of how to use DocuSign and how it works.

Use Case

The Standard System Demo is currently configured to use DocuSign with Contract records only, but DocuSign integration can be added to any table in Agiloft by a number of ways:

  • Creating a DocuSign action in that table to create an envelope 
  • Adding the DocuSign Envelope related table
  • Adding the DocuSign Recipients related tables to the other table

In Contract records, the DocuSign process begins when a user presses the Create DocuSign Envelope button on the DocuSign tab of a Contract record. This button runs a DocuSign action, and that action can be edited if you have a different preferred configuration of signers. It is currently set to use one internal signer and up to two external party signers. These fields are on the Details tab of the Contract record and need to be filled in during the contract process.

When the button is used to create the envelope, the user can click the Create & Preview button in the Envelope record to go directly to the envelope in DocuSign and preview everything. If the user approves, they can click Send in order to launch the signing process.

Further details of this process are provided in the Contracts Table section, and in the DocuSign Integration topic.

Document Templates

The Standard System Demo contains several sample document templates with DocuSign tags. These are available as a guide for creating your own contract document templates. Most templates are found in the Contracts table, but there is one template found in the Attachments table. This lone template is simply a page with a tagged signature block.

The tagging process is fully discussed in the DocuSign Users Manual, but to view a sample document in the system, go to Document Templates and open the document template with the title "Hosted Service Level Agreement DocuSign Tags." This template has DocuSign tags in the Signature area, and the tags are not visible unless you hover your cursor over the text and apply a different text color. The tags are stored in white font color so they do not appear on the final signed document. If you add more signers or change the basic signing configuration, you need to create your own tagged signature blocks.

  • No labels