HomeGuidesRecipesAPI
HomeGuidesAPILog In

(Legacy) DocuSign Connector

Organizations spend billions of dollars on technology solutions to automate their processes, the final step in those processes, the creation of the document and final transaction, is surprisingly still stuck in the past.

When documents need to be signed, inefficient processes like printing, faxing, scanning, overnighting, and data rekeying take over and the inefficiency takes hold.
But this is changing with the integration of SmartIQ forms and DocuSign.

Usage of SmartIQ and DocuSign provides the following benefits:

  • Immediate financial gains – By reducing the transaction time, organizations see needle-moving financial benefits in weeks rather than months or years.
  • Transforms the customer experience – Instead of waiting days, week, or even months for transactions to be completed, progress can be made near instantly. This velocity delights external and internal customers and elevates the organization that provides the superior service.
  • Readily demonstrates compliance – Every document has a readily accessible digital audit trail to making documenting compliance with industry laws and regulations fast and easy.

If you want to learn more about DocuSign, please visit:

Version History

Version 1.0 (released 21 April 2016)

  • Initial release

Version 2.0 (released 22 August 2016)

  • New filter Fields: envelopeId and status available for Get Envelopes Status Method for DocuSign Data Source.
  • Support of following recipient types: Agents, Carbon Copy, Certified Delivery, Editor, In Person Signer, Intermediary and Signer.
  • Brand Id supported.
  • Recipient Recursion supported (allows the same person to sign multiple times in a document).
  • Routing Order Supported (sequential and parallel orders for DocuSign workflow).
  • New Authentication methods supported: SMS, ID, Phone, Access Code, Social (Facebook, Google, LinkedIn and Salesforce).
  • Custom Fonts for Tabs, including Arial, ArialNarrow, Calibri, CourierNew, Garamond, Georgia, Helvetica, LucidaConsole, Tahoma, TimesNewRoman, Trebuchet, Verdana, OcrA, MSGothic and MSMincho.

Version 3.0 (released 31 March 2017)

New Syntax to support additional attributes for Signer TAB’s.
Supplemental Documents

  • Sign On Paper
  • DocuSign Hyperlinks
  • DocuSign Payments

Connector Components

Action

  • Send to DocuSign

Data Source

  • Get envelope status.
  • Envelope documents.
  • Retrieve recipient information.

Custom Question

  • Get Documents from DocuSign

Features

  • Customization of E-mail subject and body to recipients.
  • Embedded signing ceremony.
  • Support of following recipient types: Agents, Carbon Copy, Certified Delivery, Editor, In Person Signer, Intermediary and Signer.
  • Custom Branding.
  • Supplemental Documents.
  • Routing Order Supported (sequential and parallel orders for DocuSign workflow).
  • Draft Mode.
  • New Authentication methods supported: SMS, ID, Phone, Access Code, Social (Facebook, Google, LinkedIn and Salesforce).
  • Sing on paper
  • Recipient recursion (allows the same person to sign multiple times in a document).
  • DocuSign Payments.
  • DocuSign Hyperlinks
  • Tabs
  • Sign Here
  • Initials
  • Date Signed
  • Company
  • Title
  • Decline
  • Approve
  • First Name
  • Last Name
  • Full Name
  • Attachments
  • Note
  • Radio Button
  • Checkbox
  • DropDown List
  • Text
  • Custom Fonts, including Arial, ArialNarrow, Calibri, CourierNew, Garamond, Georgia, Helvetica, LucidaConsole, Tahoma, TimesNewRoman, Trebuchet, Verdana, OcrA, MSGothic and MSMincho.

Creating a DocuSign Sandbox

You’ll require a dev sandbox to perform tests and build solutions using SmartIQ and DocuSign.

  1. Create a new free Dev sandbox account here
  2. You'll receive a confirmation email, click "Verify Account".
  3. Change Password.

At this point, you have successfully created a Sandbox that you can use to develop and test your SmartIQ projects.

Where do I find my APIToken?

  1. Click on your profile and go to My Admin.
  2. On the navigation pane, click on API and Keys under Integrations.
  3. Click Add Integrator Key
496

Create a new API Integrator Key

🚧

Remember

The API Integrator Key is required to set up the connector variables during installation of the DocuSign Connector

Installation Requirements

Before installing this connector, you must consider the following requirements:

  • You must have administrator/elevated permissions to the SmartIQ web server, including the ability to copy and replace files in the SmartIQ installation folder. This is usually c:\inetpub\wwwroot\<<productname>> however may vary from system to system.
  • You must have an appropriate DocuSign account including the credentials and integration key to use for authentication with DocuSign. For development and testing purposes, go to DocuSign Developer Center.
  • You must have the following installation files:
  • RestShap.dll
  • DocuSign.eSign.dll
  • DocuSIgnConnector.dll

👍

Remember

  • Changes to the configuration may cause interruptions to users in forms.
  • Before installing this Connector in a production SmartIQ environment, ensure the environment is backed up.
  • It is recommended that this installation is tested in a non-production environment first, and installed during scheduled downtime.

Installation and Configuration

Use the instructions below to install the connector. If you are upgrading the extension from a previous version, refer to the section Upgrading the Connector.

Note that [<<productname>> Produce Path] refers to the installation path on the web server running SmartIQ, where the Produce site has been installed. By default this is c:\inetpub\wwwroot\<<productname>>\produce however may vary from environment to environment. Equally, [<<productname>> Manage Path] refers to where the Manage site has been installed, and [<<productname>> Scheduler Path] refers to the where the Scheduler service has been installed.

How to install the DocuSign Connector

  1. Copy the files listed above into the following folder on the SmartIQ web server:
    [<<productname>> Produce Path]
  2. Using a text editor such as Notepad, open the following file:
    [<<productname>> Produce Path]\appsettings.json

📘

Note

Ensure you have elevated privileges when opening the web.config file, otherwise, you may not be able to save in the current folder.

  1. Locate the <Extensions> section and add the following entries:
"Intelledox.Action.LegacyAction`1[[DocuSignConnector.DocuSignAction, DocuSignConnector]], Intelledox.Action",
"Intelledox.CustomQuestion.LegacyCustomQuestion`1[[DocuSignConnector.GetDocumentQuestion, DocuSignConnector]], Intelledox.CustomQuestion",
"Intelledox.Datasource.LegacyDatasource`1[[DocuSignConnector.DocuSignDataSource, DocuSignConnector]], Intelledox.Datasource"
  1. Locate the LegacyActions property or create it if it doesn't exist, and add the following:
"LegacyActions": {
  "DocuSignConnector.DocuSignAction, DocuSignConnector": {
    "Name": "Send to DocuSign"
  }
}
  1. Locate the LegacyDatasources property or create it if it doesn't exist, and add the following:
"LegacyDatasources": {
  "DocuSignConnector.DocuSignDataSource, DocuSignConnector": {
    "Name": "DocuSign"
  }
}
  1. Locate the LegacyCustomQuestions property or create it if it doesn't exist, and add the following:
"LegacyCustomQuestions": {
  "DocuSignConnector.GetDocumentQuestion, DocuSignConnector": {
    "Name": "Get Document"
  }
}

Produce appsettings.json file should look like:

{
  "Extensions": [
    "Intelledox.Extension.DatasourceBuiltin.OleDbDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.SqlServerDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.CsvDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.OdbcDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.RSSDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.WebserviceDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.XmlDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.InfinitiDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.JsonDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.DatasourceBuiltin.RestDatasource, Intelledox.Extension.DatasourceBuiltin",
    "Intelledox.Extension.ActionBuiltin.FileAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.SQLServerAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.DownloadPageMessageAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.RedirectAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.EmailAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.PrintAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.UserAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.WebhookAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.RESTAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.OracleAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.PushNotificationAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.SQLProjectResultsAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.ActionBuiltin.LogMessageAction, Intelledox.Extension.ActionBuiltin",
    "Intelledox.Extension.EscalationBuiltin.EmailEscalation, Intelledox.Extension.EscalationBuiltin",
    "Intelledox.Extension.EscalationBuiltin.ReassignmentEscalation, Intelledox.Extension.EscalationBuiltin",
    "Intelledox.Extension.EscalationBuiltin.PushNotificationEscalation, Intelledox.Extension.EscalationBuiltin",
    "Intelledox.Action.LegacyAction`1[[DocuSignConnector.DocuSignAction, DocuSignConnector]], Intelledox.Action",
    "Intelledox.CustomQuestion.LegacyCustomQuestion`1[[DocuSignConnector.GetDocumentQuestion, DocuSignConnector]], Intelledox.CustomQuestion",
    "Intelledox.Datasource.LegacyDatasource`1[[DocuSignConnector.DocuSignDataSource, DocuSignConnector]], Intelledox.Datasource"
  ],
  "AppSettings": {},
  "LegacyCustomQuestions": {
    "DocuSignConnector.GetDocumentQuestion, DocuSignConnector": {
      "Name": "Get Document"
    }
  },
  "LegacyDatasources": {
    "DocuSignConnector.DocuSignDataSource, DocuSignConnector": {
      "Name": "DocuSign"
    }
  },
  "LegacyActions": {
    "DocuSignConnector.DocuSignAction, DocuSignConnector": {
      "Name": "Send to DocuSign"
    }
  },
  "Authentication": {
    "Settings": {
      "CookiePrefix": "infiniti",
      "Timeout": "30"
    }
  }
}
  1. Using a text editor such as Notepad, open the following file:
    [<<productname>> Manage Path]\appsettings.json

  2. Locate the <Extensions> section and add the following entry:

"Intelledox.Datasource.LegacyDatasource`1[[DocuSignConnector.DocuSignDataSource, DocuSignConnector]], Intelledox.Datasource"
  1. Locate the LegacyDatasources property or create it if it doesn't exist, and add the following
"LegacyDatasources": {
  "DocuSignConnector.DocuSignDataSource, DocuSignConnector": {
    "Name": "DocuSign"
  }
}

Manage appsettings.json file should look like:

{
    "Extensions": [
      "Intelledox.Extension.DatasourceBuiltin.OleDbDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.SqlServerDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.CsvDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.OdbcDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.RSSDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.WebserviceDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.XmlDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.InfinitiDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.JsonDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Extension.DatasourceBuiltin.RestDatasource, Intelledox.Extension.DatasourceBuiltin",
      "Intelledox.Datasource.LegacyDatasource`1[[DocuSignConnector.DocuSignDataSource, DocuSignConnector]], Intelledox.Datasource"
    ],
    "LegacyDatasources": {
        "DocuSignConnector.DocuSignDataSource, DocuSignConnector": {
          "Name": "DocuSign"
        }
      },
    "AppSettings": {},
    "Authentication": {
      "Settings": {
        "CookiePrefix": "infiniti",
        "Timeout": "30"
      }
    },
    "Styles": {
      "Well": {
        "appliesto": "question,layout",
        "class": "well"
      },
      "Jumbotron": {
        "appliesto": "question,layout",
        "class": "jumbotron"
      },
      "Alert (success)": {
        "appliesto": "question,layout",
        "class": "alert alert-success"
      },
      "Alert (info)": {
        "appliesto": "question,layout",
        "class": "alert alert-info"
      },
      "Alert (warning)": {
        "appliesto": "question,layout",
        "class": "alert alert-warning"
      },
      "Alert (error)": {
        "appliesto": "question,layout",
        "class": "alert alert-danger"
      },
      "Label (default)": {
        "appliesto": "question",
        "class": "labelIx label-default"
      },
      "Label (primary)": {
        "appliesto": "question",
        "class": "labelIx label-primary"
      },
      "Label (success)": {
        "appliesto": "question",
        "class": "labelIx label-success"
      },
      "Label (info)": {
        "appliesto": "question",
        "class": "labelIx label-info"
      },
      "Label (warning)": {
        "appliesto": "question",
        "class": "labelIx label-warning"
      },
      "Label (error)": {
        "appliesto": "question",
        "class": "labelIx label-danger"
      }
    }
  }

Using a web browser, navigate to the SmartIQ Produce application and SmartIQ Manage to allow the system to register DocuSign Connector. Make sure a DocuSign license key has been applied.

The DocuSign Connector should now be installed, ready for configuration and usage.

📘

Additional Configuration

For integration key, brand id, supplemental documents, on paper signature and other DocuSign configuration, please refer to DocuSign official documentation as this needs to be configured in DocuSign admin portal.

Upgrading the Connector

  1. If a new version of the Connector is available, copy the files included in the Installation Pack into [<<productname>> Produce Path] and [<<productname>> Produce Path]
  2. Using a web browser, navigate to the SmartIQ Produce Application to allow the system to register the upgraded connector.

Installation to Scheduler

If the target environment is using SmartIQ Scheduler, it is best practice to always install connectors and accelerators to this service at the same time as the installation in SmartIQ Produce application. If this is not installed to the Scheduler there may be errors if any projects are executed from the scheduler that refers to this connector.

To install any connector to the Scheduler, follow the instructions in this guide as they apply to SmartIQ Produce, except instead of [<<productname>> Produce Path] use [<<productname>> Scheduler Path], noting that there is no ‘bin’ folder in this path so all files should be copied into the root of this path. For example, consider the path:

c:\inetpub\wwwroot\<<productname>>\produce

To install to the Scheduler, simply use this path:

c:\inetpub\wwwroot\<<productname>>\IntelledoxScheduler

Also, you must apply the same configuration changes as instructed for the Produce appsettings.json file.

Configuring the connector settings

The DocuSign Connector exposes a number of connector settings which provide system-wide values to control behaviour or context.

View/Modify Connector Settings:

  • In a web browser, navigate to the SmartIQ Manage application and log in. E.g. http:\\serverName\Manage
  • Navigate to Settings in the Administration menu group and then click the Connector Settings button at the top of the page.
  • Using the Connector drop-down list, select the ‘DocuSign’ option.
  • Review and update the settings as required each of the required settings are described in the table below.
  • Click the Save button at the top of the page once you have entered your organization's attributes.
SettingDescription
User NameDocuSign account username
PasswordDocuSign account password
Integrator KeyDocuSign API Integrator Key (Unique ID for each DocuSign integration). This key is retrieved from the DocuSign administration portal.
DocuSign Environment URLURL for the DocuSign environment. By default, this is https://demo.docusign.net/ for development. For production integrations, use: https://www.docusign.net/
LoggingTrue | False

This option that allows storing in the SmartIQ DB all generated requests to DocuSign. To enable this capability it is required to run the included SQL Script <DocuSignScript.sql> (see install package) against your active SmartIQ DB.
This option is only recommended for customers that require local audit logs, DocuSign also stores successful requests in its user portal.
1897

Connector Settings in SmartIQ Manage

Set-up DocuSign Datasource and its parameters

To be able to fully utilize all the DocuSign features there are a couple of other configurations that are required to make this all work.

View/Modify Datasource settings in SmartIQ

  • In a web browser, navigate to the SmartIQ Manage application and log in. E.g. http:\\serverName\manage
  • Click on Data Sources label on the left panel
  • Click the New Data Source button (top left)
  • Select the Connection type as DocuSignDataSource and then fill in the following settings panels.
SettingDescription
Data Source NameAny relevant name.
Connection TypeDocuSignDataSource
Connection StringAny relevant name, E.g. DocuSign
CredentialsNo Credential Required
1887

Add New Data Source in SmartIQ Manage

  1. Click Save to commit the Changes.
  2. Click Test Connection, you should get a message “Connection Successful”. If you have an error, check your credential and integrator key provided in the Connector Settings.
  3. Click on the Data Objects Button (top) and add the following objects
Display NameObject TypeFilter Fields
Get Envelope DocumentsMethodenvelopeId
Get Envelopes StatusMethodenvelopId
fromDate
status
Get Recipient InformationMethodenvelopeId
1887

Data Objects in SmartIQ Manage

🚧

Remember to check the “Required” check box for all the Key Fields. In order to guarantee that SmartIQ will only call DocuSign API if data is provided.

You are now configured and ready to start creating SmartIQ projects that connects to DocuSign for signing.

Using the DocuSign Connector

Action input- Send to DocuSign

480

DocuSign Action in SmartIQ Design

AttributeDescriptionRequired/Optional
Email SubjectEmail subject sent by DocuSign to the recipients.Required
Email BodyEmail body sent by DocuSign to the recipientsRequired
Brand IDAllows to change the branding used by DocuSignOptional
Supplemental DocumentsDefines supplemental documents by name supporting “View” and “View and Accept” modes, using the syntax:
v=filename1,filename2
va=filename3 , filename4
Optional
Embedded Signing Return URLReturn URL after embedded signing ceremony. If key {{envelopeID}} is present in the URL, this will be replaced by the created envelope ID.Required if embedded is specified
Signer (parameter = value)Use this action if your recipient must sign, initial, date or add data to form fields on the documents in the envelope.
Agent (parameter = value)This recipient can add name and email information for recipients that appear after the recipient in routing order. For instance, if you have an Agent recipient in routing order 1, and two recipients in routing order = 2, then the Agent will be able to edit the recipient information of those two subsequent recipients.
Carbon Copy (parameter = value)Use this action if the recipient should get a copy of the envelope, but the recipient does not need to sign, initial, date or add information to any of the documents. This type of recipient can be placed in any order in the recipient list. The recipient receives a copy of the envelope when the envelope reaches the recipient's order in the process flow and when the envelope is completed. CC recipients are special in that they do not take any actions on the envelope but instead just receive a copy of it.
Certified Delivery (parameter = value)Use this action if the recipient must receive the completed documents for the envelope to be completed, but the recipient does not need to sign, initial, date or add information to any of the documents. This is analogous to Certified mail delivery through the U.S. post office and is used to confirm that your recipients have received the envelope.
Editor (parameter = value)This recipient has the same management and access rights for the envelope as the sender and can make changes to the envelope as if they were using the Advanced Correct feature. This recipient can add name and email information, add or change the routing order and set authentication options for the remaining recipients. Additionally, this recipient can edit signature/initial tabs and data fields for the remaining recipients. The recipient must have a DocuSign account to be an editor.
In Person Signer (parameter = value)Use this action if the signer is in the same physical location as a DocuSign user who will act as a Signing Host for the transaction. The recipient added is the Signing Host and new separate Signer Name field appears after Sign in person is selected.
Intermediary (parameter = value)This recipient can, but is not required to, add name and email information for recipients at the same or subsequent level in the routing order (until subsequent Agents, Editors or Intermediaries recipient types are added).

Action Output

Action OutputDescription
Embedded Signer URLURL created by DocuSign for embedded signature. Use this output as a Redirect URL for the Redirect Action.
Envelope IdEnvelope Id created by DocuSign

Signer Parameters Syntax

Required

  • name = (string)
  • email = (string)

Optional

  • allowrecursion = (bool) If true, order is required. If false, no need to include this parameter.
  • order = (int) If routing order required, this parameter is required for all signers
  • embedded = (bool) Embedded is only available for one recipient per envelope. If false, no need to include this parameter.
  • draft = (bool) If true, embedded=true is required. If false, no need to include this parameter.
  • social = Facebook, Google, LinkedIn or Salesforce
  • sms = (string). Country code + Mobile number i.e. +6112345678 for an Australian mobile phone.
  • phone = (text). Country code + Phone number i.e. +6112345678 for an Australian mobile phone.
  • accesscode = (int)
  • id = (bool) Enables ID Authentication.
  • onpaper= (bool) This option has to be enabled in DocuSign Account.
  • location using anchor string: \s#\ or /s#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
signature=\s1\:: CEO :: tablabel=ceo

name= John Doe
[email protected]
signature=1,50,50 ; 2, 50,80 :: CEO :: tablabel=ceo
  • location using anchor string: \i#\ or /i#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string), optional(bool)```
    
name= John Doe
[email protected]
initial=\i1\:: CEO :: tablabel=ceo, optional=true

name= John Doe
[email protected]
initial=1,50,50
  • location using anchor string: \ds#\ or /ds#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
datesigned=\ds1\:: contract :: tablabel=ceo

name= John Doe
[email protected]
datesigned=1,50,50 ; 2, 50,80 :: contract
  • location using anchor string: \co#\ or /co#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
company=\co1\:: Company :: tablabel=ceo

name= John Doe
[email protected]
company=1,50,50 ; 2, 50,80 :: CEO :: tablabel=ceo
  • location using anchor string: \t#\ or /t#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
title=\t1\:: title :: tablabel=title

name= John Doe
[email protected]
title=1,50,50
  • location using anchor string: \d#\ or /d#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
decline=\d1\

name= John Doe
[email protected]
decline=1,50,50 :: approval :: tablabel=decline
  • location using anchor string: \a#\ or /a#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
approve=\a1\:: approval :: tablabel=check

name= John Doe
[email protected]
approve=1,50,50
  • location using anchor string: \fn#\ or /fn#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
firstname=\fn1\:: FirstName :: tablabel=fn

name= John Doe
[email protected]
firstname=1,50,50
  • location using anchor string: \ln#\ or /ln#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
lastname=\ln1\:: lastname :: tablabel=lastname

name= John Doe
[email protected]
lastname=1,50,50 ; 2, 50,80 :: lastname :: tablabel=ceo
  • location using anchor string: \fullname#\ or /fullname#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
fullname=\fullname1\:: FullName :: tablabel=fullname

name= John Doe
[email protected]
fullname=1,50,50 ; 2, 50,80 :: FullName :: tablabel=fullname
  • location using anchor string: \a#\ or /a#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: tablabel(string)```
    
name= John Doe
[email protected]
attachment=\a1\

name= John Doe
[email protected]
attachment=1,50,50 ; 2, 50,80 :: CEO :: tablabel=ceo
  • ```font = Arial, ArialNarrow, Calibri, CourierNew, Garamond, Georgia, Helvetica, LucidaConsole, Tahoma, TimesNewRoman, Trebuchet, Verdana, OcrA, MSGothic or MSMincho````. If not specified default font is Calibri.

  • location using anchor string: \no#\ or /no#/, where # defines the signer id.
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: conditionalparentlabel (string), conditionalparentvalue(string), tabLabel(string)```
    
name= John Doe
[email protected]
note1=\no1\:: This is an example of a note in DocuSign :: Note1 :: tablabel=test

name= John Doe
[email protected]
note2=1,50,50 :: This is a second note using coordinates :: Note2 :: tablabel=test2
  • location using anchor string: \rb#\ or /rb#/, where # defines the signer id.```
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Radio Optional Parameters: selected(bool), required(bool), value(bool), locked(bool). Use ‘+’ as separator character.
    Radio Group Optional Parameters: conditionalparentlabel (string), conditionalparentvalue(string), requireall(bool), shared(bool), requireinitialonsharedchange(bool) and required(bool), locked(bool).
    
name= John Doe
[email protected]
radiobutton1 = \rb1\ , \rb2\ , \rb3\ , \rb4\ , \rb5\ :: Fav Colour :: requireAll=true

name= John Doe
[email protected]
radiobutton2 = \rb6\ (selected=true+locked=true) , \rb7\:: Policy
  • location using anchor string: \cb#\ or /cb#/, where # defines the signer id.```
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: conditionalparentlabel(string), conditionalparentvalue(string) , locked (bool), selected(bool), required(bool), tabLabel(string), shared(bool) and requireinitialonsharedchange(bool)
    
name= John Doe
[email protected]
checkbox1 = \cb1\ :: Tooltip name :: required=true, tablabel=Checkbox

name= John Doe
[email protected]
checkbox2= 1,50,50:: Approve
  • dropdownlist{number} = location:: values (item optional parameters) :: name :: optional parameters
    location using anchor string: \ddl#\ or /ddl#/, where # defines the signer id.
    Location via coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Item Optional Parameters: name(string), selected(bool), value(string). Use ‘+’ as separator character.
    List Optional Parameters: conditionalparentlabel (string), conditionalparentvalue(string), requireall(bool), locked (bool), defaultValue(string), required(bool), tabLabel(string), shared(bool) and requireinitialonsharedchange(bool)
name= John Doe
[email protected]
dropdownlist1 = \ddl1\ :: apple (value=red) , lemon (value=yellow) , pumpkin(value=orange) :: FruitDropdown :: shared=true , requireinitialonsharedchange = true

name= John Doe
[email protected]
dropdownlist2 = \ddl2\ :: Deep Learning(name=noSQL+selected=true) , SQL Server ,MongoDB(name=Open Source + value=mongo), DocumentDB :: DBs
  • location using anchor string: \txt#\ or /txt#/, where # defines the signer id.```
    Location using coordinates: page,x,y (if more than one location, use ‘;’ separator char.
    Optional Parameters: conditionalparentlabel (string), conditionalparentvalue(string), requireall(bool), locked (bool), required(bool), maxlength(int), validationpattern(string), tabLabel(string), shared(bool), requireinitialonsharedchange(bool) and hyperlink(bool).
    Hyperlink: name= URL and value = Text to be displayed.
    
name= John Doe
[email protected]
text1=\txt1\:: This is an example of a text :: Free Text1 :: tablabel=text1

name= John Doe
[email protected]
text2= \hyp1\ :: Click Here :: www.intelledox.com

name= John Doe
[email protected]
text3=1,50,50 ; 2, 50,80 :: Please Sign this document :: Reminder
  • location using anchor string: \txt#\ or /txt#/, where # defines the signer id.```
    Location using coordinates: page,x,y.
    Optional Parameters: currency (Currency Code), total (number), decimalplaces (number), tablabel (string).
    
name= John Doe
[email protected]
payment = \p1\:: Payment :: currency=USD, total=100, decimalplaces=2

📘

Note

Note: ValidationPattern optional parameter requires a escape character ‘!’ when a ‘,’ is used. For example, “1!,2!,3” would match “1,2,3”.

Simple Example of use of all tabs:

name= John Doe
[email protected]
note1=\no1\::This is a note 1::FYI
radiobutton1 = \rb1\ , \rb2\ , \rb3\ , \rb4\ , \rb5\ :: Fav Colour :: requireAll=true
radiobutton2 = \rb6\ (selected=true) , \rb7\:: Policy
checkbox1 = \cb1\ :: One :: required=true
checkbox2 = \cb2\ :: Two
checkbox3 = \cb3\ :: Three :: locked=true,selected=true
text1 = \txt1\ :: This is free text in Docusign :: Free Text
text2= \hyp1\ :: Click Here :: www.intelledox.com
dropdownlist1 = \ddl1\ :: Australia , New Zealand :: country :: requireAll=true, defaultValue=Australia
dropdownlist2 = \ddl2\ :: Deep Learning(name=noSQL,selected=true) , SQL Server ,MongoDB, DocumentDB :: DBs
embedded = true
initial = \i1\
datesigned = \ds1\
company = \co1\
title = \t1\
decline = \de1\
approve = \ap1\
firstname = \fn1\
lastname = \ln1\
fullname = \fulln1\
attachment = \at1\