High-Level Specification

Functional Overview

This document details the DocuSign integration requirement between Syensqo DocuSign and Icertis Contract Intelligence (ICI). This document provides all necessary information to enable and guide the configurator to effectively integrate ICI with DocuSign.

Scope and Objectives

Scope Includes:

1. Integration of DocuSign with Icertis for Agreement Signatures by Internal & External signatories (Contract Execution)

Process Flow Diagram

Assumptions

NA

Dependencies

1. Signature workflow rules must be configured in Icertis for Electronic Signature else DocuSign integration will not work.
2. While configuring the integration at DocuSign end, the user must be an Account Administrator. 
3. While configurating the integration at Icertis end, the user must be assigned ESign Admin role

Security, Integrity and Controls

As this is a standard integration through an adaptor, all security requirements are followed as per standard.

Configuration Requirements

Following configuration needs to be completed in both Icertis and DocuSign platform:

1. DocuSign: In DocuSign, the configuration is a two step process.

   1. Configure Account 
      1. Log in to the DocuSign account as an Account Administrator.
      2. Go to the Setting tab.
      3. In the left navigation panel, click INTEGRATIONS > Connect.
      4. Click Add Configuration and select Custom from the dropdown list.
      5. In the Add Custom Configuration section, update the following sections:
         • Go to the Listener Settings section.
         • Select Active Connection in the Status dropdown.
         • Add a Name for the connect.
         • Add a URL to Publish as https://syensqo-dev/ESignCallBack/Initiate. (For UAT it will be https://syensqo-uat/ESignCallBack/Initiate, for Prod it will be https://syensqo/ESignCallBack/Initiate)
         • Go to the Event Settings section.
         • Select REST v2.1 in the Date Format dropdown.
         • Select Send Individual Messages (SIM) in the Event Message Delivery Mode dropdown.
         • Go to the Trigger Events section.
         • From the Envelope Events list, select Envelope Sent, Envelope Declined, and Envelope Voided.
         • From the Recipient Events list, select Recipient Signed/Completed, Recipient Declined, Recipient, and Reassign.
         • Go to the Include Data section.
         • Select Custom Fields, Extensions, Recipients, and Tabs from the list.
      6. Go to the Integration and Security Settings section. Select Enable Manual TLS.
      7. Click Save Configuration. You can see the configuration you created.
   2. Add App in Account created above
      1. Log in to DocuSign account as an Account Administrator.
      2. Go to Setting > Connect.
      3. Select the configuration which was created as above
      4. Go to Setting > Apps and Key
      5. Capture the following information.
         • The User ID.
         • The API Account ID.
         • The Account Base URI.
      6. Click Add App and Integration key.
      7. Add a Name for the app and click Add.
      8. The app is automatically assigned an integration key (GUID) value that cannot be changed. Note the Integration key value.
      9. Click Generate RSA to create a new, automatically generated GUID value that represents the ID for the private and public key pair.
      10. Note down the Private key. Click Close.
      11. Click Save

2. Icertis Side Configuration - Post configuring the above steps, the following configuration needs to be performed in Icertis

   1. In Icertis, navigate to Configurations > System Configurations > ESign Configurations

   2. Click Create>DocuSign Account
   3. Configure the following fields

Add the Redirect URI in DocuSign

1. Log in to the DocuSign account as an Account Administrator.
2. Go to Setting > Apps and Keys.
3. Find the integration key you previously added and click ACTIONS > Edit.
4. Go to Additional settings and click Add URI.
5. Add the Redirect URI that you decoded.
6. Click Save.

Special Requirements

Design Rationale

Data Structure

Source Structure

The following fields will be used to provide the required information for this interface:

Target Structure

The following fields will be used to provide the required information for this interface:

Mapping and Calculation

Processing Logic

Processing within Source

Processing within Middleware

Processing within Target

Interface Dependency

Interface Constraints

Delivery Requirements

Delta or Full Load Requirements

Interface Alert & Monitoring

Interface Reporting

Language Requirements

User Interface Requirements

Volumetrics

Performance Consideration

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log