Docusign Connector Configuration

Sales Engineering Quick Guide on how to configure the Docusign connectors for e-signature POCs.

Valid for PM Connectors as available on Enterprise editions 3.1.x through 3.3.x

Instructions

On Docusign

URL.- https://appdemo.docusign.com/home

Admin Configuration

A. Create and configure an OAth application from inside DocuSign developers console.

Login to your Docusign developer account. (https://account-d.docusign.com/)
On the top menu go to Settings, then in the sub menu go to Integration → API and Keys.
Click on Add APP / Integrator Key. (Note: If a key already exists, you may be able to use it). Name it ProcessMaker.
Copy the Integration Key for later
Choose Authorization Code Grant
Add a Secret Key, copy the Secret Key for later
Add a redirect URI like: https://your.processmaker.server/docusign/authorization
Save the application

B. Configure DocuSign in ProcessMaker

Go to Admin menu
Click on DocuSign Configuration sub menu
Paste the previously copied Integration Key
Paste the previously copied Secret Key
Save the configuration

C. Grant Access Code from Admin menu (Optional)

From DocuSign Configuration click on GRAN DOCUSIGN ACCESS
Click on Authorize access
Login with you docusign accound (the owner of your docusign documents and templates)
Done

Template Configuration

You could use any template you have in DocuSign or create a new one. To create a new template follow the following steps:

From your DocuSign account go to Templates.
Create a New Template
Set the name an a brief description
Upload a document to be signed
Setup the recipients
Save and exit

Connector Use

Design a Process with a form task that captures necessary Recipient information (name, email).

The request will be expecting a Body with the following JSON structure:

{

"status" :"sent",

"emailSubject" :@@Subject,

"templateId" :@@Template,

"templateRoles":@=SignersList

}

You'll need thus to create these variables prior to calling the connector.

emailSubject can be either hard-coded or read from a variable. It is a plain text field.
templateId is the ID for the template you will request signing. It can be hard-coded or read from a variable.

templateRoles is a JSON array with details for each Recipient. Each element in the array will follow this structure:

"roleName"=> "rolename",
"name"=> "name"
"email"=> "email",
"recipientId"=> "id",
"tabs"=> { {"textTabs" => $textTabs }
Here you will replace these values with form data. See the following sample script that builds this payload:

DS Script

$tempArray=array();
$textTabs=array();

array_push($textTabs,
           array(
           "tabLabel"=>"txtCompany",
			"value"=> @@companySignature
           ));


array_push($tempArray, 
	  array(
      "roleName"=> "Disclosing",
      "name"=> @@signeeSelect_label,
      "email"=> @@txtCioEmail,
      "recipientId"=> strval("2")
	  ),		   

	  array(
      "roleName"=> "Receiving",
      "name"=> @@employeeFirstName,
      "email"=> @@employeeEmail,
      "recipientId"=> strval("1"),
	  "tabs"=> array ("textTabs" => $textTabs)
	  )
);

$json=json_encode($tempArray);

#Payload:
@@SignersList=$json;
@@Template = "94e26f82-42cf-4689-8b49-85495e3fe773"; // id for the PM NDA 
@@MessageEmail = "Please sign the NDA";
@@Subject = "DocuSign: NDA available for signature";

#Get User Email
$userInfo =userInfo(@@USER_LOGGED);
//@@txtAdvisorName = $userInfo['firstname'] . " " . $userInfo['lastname'];
@@txtUserEmail = $userInfo['mail'];

Once you have these variables set, you can use the Service Task with the createSendEnvelope connector:

Configure Body type as JSON
Add the JSON object in the body, as follows:

{

"status" :"sent",

"emailSubject" :@@Subject,

"templateId" :@@Template,

"templateRoles":@=SignersList

}

Profit!