1. AODocs Knowledge Base
  2. AODocs connectors and add-ons
  3. AODocs–DocuSign integration

Configure a library with the AODocs eSign Connector

Follow
Avatar
AODocs

The AODocs eSign Connector offers an electronic signature system for digital files. It lets you integrate DocuSign or Adobe Acrobat Sign into AODocs.

The AODocs eSign Connector is used to sign attachment(s) of an AODocs document in a Document Management library.

 

  • Important: The AODocs eSign Connector can be configured only in Document Management libraries. When the file is signed, the way it is reattached to the document depends of the connector configuration.
    • For DocuSign only :
      • Archive : A zip containing the signed pdf, and the certificate of signature is attached to the document
    • For both :
      • Certificate : Only the signature certificate is re attach to the document
      • Combined : The signed pdf as "name.signed.pdf"
      • CombinedAndCertificate : Both of the above

As a library administrator, to enable the electronic signature on your library, you need to configure several features. This article provides an example of a simple use case.

Automatically generated table of contents

Scope of this article

This article provides an example of the simple use case for the AODocs eSign Connector, with two or more signers determined by property values in the document class.

The following advanced features of the AODocs eSign Connector are not described in this article:

  • define a signing order (parallel or sequential validation) when using more than one signer – learn more from the DocuSign documentation or from the Adobe Acrobat Sign documentation
  • Carbon Copy (available in DocuSign and Adobe Acrobat Sign) or Blind Carbon Copy (available only in DocuSign) in the email sent to the signer – learn more:
  • choice of attachments:
    • all attachments concatenated into one PDF
    • only send a specific file format – consult the list of supported files for DocuSign and Adobe Acrobat Sign
    • give the Google Drive attachment IDs that you want signed – only in libraries using Google Drive storage, not Google Cloud Storage (GCS)
  • recover the certificate produced by Docusign or Adobe Acrobat Sign showing a summary of the process
  • optional DocuSign properties:
    • Sign status: feedback for the end user about the signature request (envelope) status in the signing process
    • Status reason: description of the reason the document is in its current status
    • Link to DocuSign envelope: URL on the DocuSign platform of the document to be signed
    • Envelope ID: DocuSign ID of the signature request (envelope)

To find out about advanced features and how to customize this simple use case to meet your specific business requirements, contact your AODocs sales representative or send an email to sales@aodocs.com.

Configure your document class 

1. Access the library administration and select Document classes.

2. Select (or create) the document class for which you want to enable eSignature.

Tip: We recommend creating a separate document class for each signature process you want to implement.

3. In the Properties tab, create the property or properties for the signers. There are different instructions for DocuSign and Adobe Acrobat Sign. 

Note: There can be any number of signers.

Learn more: Create and configure custom properties.

 

#DocuSign #Adobe Acrobat Sign

For DocuSign, as a minimum, you must add:

  • one Person property for the signer of your document, by default Signer emails
  • one String property for the name of the signer, by default Signer names

Tip: We recommend using a calculated property to synchronise easily Signer mails and names

For Adobe Acrobat Sign, as a minimum, you must add one Person property for the signer of your document, by default Signers.

If you intend to use the tag to extract the full name of the signer when you prepare your document for signature, you must also add a String property for the name of the signer. 

Note: There's no default value for the property containing the signer names. 

If there's more than one signer, make the properties multi-value.

Note: You can customize the property names according to your business case. If you don't use the default values, you must map the properties to parameters in the custom script. In our example, we use customized values.

Tip: You can use conditional logic in the property for the signer names. Use a formula that extracts the display names from the emails, for example: propertyMultiPerson`Signer email addresses`.map(p => p.displayName). Learn more: Configure conditional logic to calculate property values.

image01.png

Create and configure a custom script

The AODocs eSign Connector relies on custom scripts. You can use the sample custom scripts provided to configure eSignature in your library. There are different custom scripts for DocuSign and Adobe Acrobat Sign. You will probably need to adapt the custom scripts to match your own use case. If you need assistance, contact your AODocs sales representative or send an email to sales@aodocs.com.

Learn more: Custom scripts.

You can use the sample custom scripts provided to configure eSignature in your library. There are different instructions and custom scripts for DocuSign and Adobe Acrobat Sign.

1. Create a new custom script. Define it as type Viewer Action or Workflow Transition Action, depending on which custom script you want to use.

Note: If you choose to trigger your eSignature through a Workflow Transition Action custom script, you must also configure a workflow for eSignature.

2. Copy the code from the sample custom script into your custom script.

#DocuSign #Adobe Acrobat Sign

3. If required, edit your custom script. 

  • Google Cloud Storage (GCS)
    If you're in a library using GCS, edit the following line:
    //.setAttachmentStorageType(ESignConnectorRequest.StorageType.DRIVE) // 
    Remove the two forward slashes (//) at the beginning of the line and change DRIVE to OSS.
  • Microsoft users
    If you're a Microsoft user, edit the following line:
    // .setDocumentUpdateType(ESignConnectorRequest.UpdateType.asCurrentUser) //
    Remove the two forward slashes (//) at the beginning of the line.

4. Create parameters for your custom script. 

#DocuSign #Adobe Acrobat Sign

Mandatory parameter

In the custom script editor, create a parameter called accountId with the API Account ID as the default value.

Notes:
– The parameter name is case sensitive.
– Don't select the Mandatory checkbox.

To find your API Account ID:

Optional parameters

If you didn't use the default values for your eSign properties, you must map your cusomized properties to parameters in the custom script. Create these parameters: 

  • signersEmailFieldName – the default value must be the exact name of the property containing the signer emails
  • signersNameFieldName – the default value must be the exact name of the property containing the signer names

image02DocuSign.png

If you didn't use the default value for the property containing the signer emails, you must map your cusomized properties to parameters in the custom script.

Create a parameter called signersFieldName. The default value must be the exact name of the property you defined for the signers.

Notes:
– The parameter name is case sensitive.
– You don't need to map the parameter containing the signer names.
– Don't select the Mandatory checkbox.

image02Adobe.png

5. Click Save.

If you created a Viewer Action custom script, the configuration is now complete. You can create a document for signature. Learn more: AODocs eSign Connector User Guide.

If you created a Workflow Action custom script, you must create and configure a workflow for eSignature. 

Create and configure a workflow for eSignature

Create a workflow according to your business case

If you’ve never configured workflow transitions (or if you need to refresh your memory) refer to Create and configure workflows.

Below is a simple example of a workflow used for eSignature.

Note: This example corresponds to the most simple use case. For a more advanced configuration specific to your business, contact your AODocs sales representative or send an email to sales@aodocs.com.

image03.png

Configure a custom action in your workflow

Custom actions define how custom scrips are triggered. In our example, the custom script is triggered via a workflow.

If you’ve never configured custom actions in workflow states (or if you need to refresh your memory) read the article Trigger custom scripts on workflow states. 

1. Click the Customize button on the workflow state from which eSignature will be triggered. In our example, this is in the Initial state.

2. In the dialog, select Add new action.

3. Enter a name for the action.

Note: The action name appears in the custom script logs when the custom script runs.

4. Select Run when document leaves state before outbound transition is completed.

5. In the Script name drop-down menu, select the custom script you configured.

6. Click Save.

7. Save the changes to your workflow.

#DocuSign #Adobe Acrobat Sign
image04DocuSign.png image04Adobe.png

The configuration is now complete. You can create a document for signature. Learn more: DocuSign Connector User Guide.

Was this article helpful? 8 out of 8 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

Related articles