Users can send files or forms for signature directly from Asite to DocuSign. They can publish files or create forms, distribute them, have them executed with DocuSign, and then save them back to Asite for safe storage and sharing.
This seamless collaboration works with any file or form on the Asite platform, making it easier and time-efficient for businesses to automate their paper-based processes.
About DocuSign
DocuSign, Inc. is an American company headquartered in San Francisco, California, that allows organisations to manage electronic agreements. As part of the DocuSign Agreement Cloud, DocuSign offers eSignature, an electronic signing solution available on various devices.
Signatures processed by DocuSign comply with the US ESIGN Act and the European Union's eIDAS regulation, including EU Advanced and EU Qualified Signatures.
What are the Features of DocuSign?
Enables users to send any file or form for Signature to DocuSign.
For forms, the signed copy will be returned to Asite, and a PDF record of the DocuSign® Version will be attached to the original form.
For files, the signed copy will be returned to Asite, and a PDF record of the DocuSign® Version will be added as a new revision with an appropriate status.
Automates the status tracking for files or forms.
Offers full audit tracking.
Asite and DocuSign Integration for Files
Prerequisites
An active Asite CDE subscription
Asite CDE Connector for DocuSign® subscription
Privilege to manage integrations on your Asite account ('Enable DocuSign Integration' and 'Can Manage Integration')
Privilege to Send Documents to DocuSign (Can Send to DocuSign) on the relevant project on Asite
An active DocuSign account
Appropriate file statuses should be set up on the project for starting DocuSign on a file, completing the signing process via DocuSign, and for rejection.
How do I Integrate My Asite Account with DocuSign for Files?
Configure DocuSign Integration in Asite
Once logged in, go to More and click Admin.
Select Integrations from available options.
Only users with the Enable DocuSign Integration role privilege can create and configure integrations.
On the Integrations listing page, click Create Integration at the top right corner, and a pop-up will appear.
Fill in the details needed in the pop-up to set up a new integration.
Available options (in the pop-up) when creating an Integration:
Integration: Select DocuSign from the dropdown.
Organisation: Enter the partial or full name of your organisation or select from the dropdown.
Email: Enter or select a user from the same organisation. The chosen user must have the necessary permission on the folder.
DocuSign Credentials - Client ID and Secret: Enter Client ID and Secret Key provided in your DocuSign account.
Click Save to apply the changes. The saved integration will only work for the selected organisation.
Entering the Asite Redirection URI for Authorisation Code in DocuSign
Log in to your developer account at https://developers.docusign.com/.
Go to the screen below for 'Additional Settings'.
Enter the Redirect URI as: https://integration.asite.com/api/authorization-code.
Click Save to apply the changes.
Setting up System Tasks and Triggers
Asite integrates with DocuSign for Files via our robust Visual Workflow tool, along with the above configurations. Below are the steps involved for project administrators to set up system tasks and triggers specific to DocuSign integration for Files.
Create 5 system tasks on files as explained below:
For DocuSign Initiated: Create a File Status Change system task with the required configuration details on the relevant project.
Select the appropriate DocuSign file status, such as 'DocuSign Initiated', in the To field.
For DocuSign Completed: Create another File Status Change system task with the required configuration details on the relevant project.
Select the appropriate DocuSign file status, such as 'DocuSign Completed', in the To field.
For DocuSign Declined: Create a third File Status Change system task with the required configuration details on the relevant project.
Select the appropriate DocuSign file status, such as 'DocuSign Declined', in the To field.
For Revision Unlock: Create an Unlock File Activities system task with the required configuration details on the relevant project.
For Revision Upload: Create a Revision Upload system task with the required configuration details on the relevant project.
Once the system tasks are created, we need to set up triggers on the files for each configured system task. See details below:
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The Revision Upload system task can be triggered:
On the Integration Connector event in Post task mode.
With the DocuSign - Completed Event selected as the task type.
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The Unlock File Activities system task can be triggered:
On the Integration Connector event in Post task mode.
With the DocuSign - Completed Event selected as the task type.
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The File Status Change system task for DocuSign Initiated can be triggered
On the Integration Connector event.
In the Post (Sync) task mode.
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The File Status Change system task for DocuSign Completed can be triggered:
On the Integration Connector event.
In the Post task mode.
With the DocuSign - Completed Event selected as the task type.
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The DocuSign Declined system task can be triggered on the Integration Connector event in Post task mode, with the DocuSign - Completed Event selected as task type.
Create a workflow trigger on the file in the same project. This workflow trigger is meant to be set up so that:
The Unlock File Activities system task can be triggered:
On the Integration Connector event.
In the Post task mode.
With the DocuSign - Declined Event selected as the task type.
Since the system task is configured to trigger the 'Integration Connector' event, the user can send any existing file using the 'Sign with DocuSign' right-click option. The DocuSign sign-in screen will appear in a new browser tab. Based on the integration setup, you can continue preparing to sign the file on the DocuSign website.
Once a file is sent for signature via DocuSign, all its activities will be locked in the relevant project folder on Asite. After the required signatories sign the file, the same activities will be unlocked.
Using the 'View with DocuSign' right-click option, you can view the signature and relevant details on DocuSign.
The signed copy is added as a new revision with an appropriate status on Asite. If the file can't be signed for any reason, the status of the original file will be updated accordingly.
Asite and DocuSign Integration for Forms
Prerequisites
An active Asite CDE subscription + Asite API permission
An active DocuSign account + DocuSign API integration
How Do I Integrate My Asite Account With DocuSign for Forms?
Entering the Asite Redirection URI for Authorisation Code in DocuSign
Log in to your developer account at https://developers.docusign.com/.
Go to the screen below for 'Additional Settings'.
Enter the Redirect URI as: https://integration.asite.com/api/authorization-code.
Click Save to apply the changes.
Setting up System Tasks and Triggers
Asite integrates with DocuSign for Forms via our robust Visual Workflow tool, along with the above configurations. Below are the steps involved for project administrators to set up system tasks and triggers specific to DocuSign integration for Forms.
Create two system tasks on forms - one for Authorisation Integration and another for Attach Document - with required configuration details in the relevant project for the required form type.
When creating a system task for Attach Document, please ensure that 'DocuSign' is selected as 'Document Source' to utilise this integration option.
Once the system tasks are created, we need to add triggers on forms for each configured system task. See details below:
Create a workflow trigger on the forms with the same form type and in the same project. This workflow trigger is meant to be set up so that:
The Authorization Integration system task can be triggered:
On the Create App event.
In the Post (Sync) task mode.
Create a workflow trigger on the forms with the same form type and in the same project. This workflow trigger is meant to be set up so that:
The Attach Document system task can be triggered:
On the Integration Connector event.
In the Post (Sync) task mode and the DocuSign - Completed Event task type.
Create a workflow trigger on the forms with the same type and in the same project. This workflow trigger is meant to be set up so that:
The Attach Document system task can be triggered:
On the Integration Connector event.
In the Post (Sync) task mode and the DocuSign - Declined Event task type.
Since the system task is configured to trigger the 'Create App' event, the user can now create a form. Once the form is created by clicking the 'Send' link, the DocuSign sign-in screen will appear in a new browser tab. Based on the integration setup, you can continue to sign the form on the DocuSign website.
Once the form is signed on the DocuSign website, the signed copy of the form will be added as a PDF attachment to the original form record on your Asite project.