DocuSign Connector
Customize and send documents for signatures by fully integrating DocuSign’s eSignature functionality into your Processes.
Overview
DocuSign eSignature provides a service to digitally sign legally-binding documents including contracts, account openings, and invoices. You require a DocuSign eSignature account, and its accompanying token, to use the DocuSign connector in your Process models.
See the example how to get a DocuSign eSignature app integration and secret key with which to configure ProcessMaker Platform to use a DocuSign eSignature template, and then configure a DocuSign connector.
Add a DocuSign Connector to the Process Model
Add a DocuSign connector from one of the following locations in Process Modeler:
Object Panel: Located to the left of the Process Modeler canvas, the Object Panel contains various process model objects.
Object Bar: Located at the bottom of the Process Modeler canvas, the Object Bar contains pinned Process model objects for quick access.
Follow these steps to add a DocuSign connector from the Object panel to the Process model:
Click the DocuSign object from one of the following sections:
Pinned Objects: The DocuSign object appears in the Pinned Objects section when it is pinned.
Click the location in the Process model to place this connector. Follow these guidelines when placing this connector:
Optionally place this connector between two existing Process model objects already connected with a Sequence Flow element. See Place an object between two connected objects.
Settings
The DocuSign connector has the following panels that contain settings:
DocuSign Template panel
Document for Signature panel
Response Options panel
Loop Characteristics panel
Documentation panel
Advanced panel
DocuSign Template Panel Settings
Edit the Connector Name
A connector name is a human-readable reference for a Process model control. Process Modeler automatically assigns the name of a Process model connector with its connector type. However, a connector's name can be changed.
Follow these steps to edit the name for a DocuSign connector:
Select the DocuSign connector from the Process model in which to edit its name.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Expand the DocuSign Template panel if it is not presently expanded. The Name setting displays.
In the Name setting, edit the selected connector's name and then press Enter.
Document for Signature Panel Settings
Edit the DocuSign Template ID and User Roles
Select a DocuSign Template ID referencing the document for which an eSignature is required and select recipient roles for users to sign the document. For more information on how to create a DocuSign template and create recipient roles, refer to Working with Templates - DocuSign eSignature User Guide.
Ensure the following before configuring the settings described in this section:
Your organization uses a DocuSign eSignature account.
You created a template for the document in which this DocuSign connector is to solicit signatures. This template must be configured with at least one role.
You created a DocuSign app that uses this DocuSign template.
Your ProcessMaker Platform settings for DocuSign are configured with the DocuSign app integration and secret keys that use this DocuSign template. Your DocuSign settings must also be configured with the DocuSign server and authorized access to that server to authenticate your DocuSign app's integration and secret keys.
Contact your ProcessMaker Administrator for assistance if necessary.
See this example.
Follow these steps to select a Template ID and recipient role(s):
Select the DocuSign connector from the Process model in which to edit its name.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Expand the Document for Signature panel. Settings for this panel display.
From the Template ID setting, select the DocuSign template that references the document to send for eSignature. The template list populates from your DocuSign server specified in the DocuSign settings. If you do not see your templates here, review the DocuSign eSignature templates in your DocuSign account. Note that you may need to ask your Administrator for assistance.
After a DocuSign template is selected, recipient roles populate from DocuSign. For guidance on how to define recipient roles, see Create Templates - DocuSign eSignature User Guide.
Placeholder recipient roles created in DocuSign must be configured in Process Designer.
From the Select a Type drop-down menu for each role, select one of the following options:
User: Select the User option to email the document to a selected user. The Send to User setting displays. From the Send to User setting, select which user serves as that role. The email address associated with this user account is used to send the document for eSignature. This is a required setting when the User option is selected.
Requester: Select Requester to email the document to the Request starter.
User ID: Select User ID to email the document to a user based on a Variable Name value as entered into a Screen during a previous Task in that Request. For example, if a Line Input control in a Screen has the Variable Name setting value of
UserId
that contains a user's ID, then use that value to thereby send the document for eSignature. When this option is selected, the Send to User ID setting displays. The email address associated with this user account is used to send the document for eSignature. This is a required setting when the User ID option is selected.Email Address: Select Email Address to email the document to a non-ProcessMaker Platform user. When this option is selected, Recipient Email and Recipient Name settings display. Enter the email address and name for the intended recipient, respectively. The Recipient Email and Recipient Name settings are required when the Email Address option is selected.
Process Manager: Select Process Manager to email the document to the owner of the Process. The Process Manager understands the Process design and workflow dynamics to troubleshoot Request routing incidents. Ensure that a Process Manager is configured for this Process.
Response Options Panel Settings
Edit Signature and Output Variable Settings
Configure whether to pause a Request while awaiting user signatures and how to save the response from DocuSign.
Follow these steps to configure the response from DocuSign:
Select the DocuSign connector from the Process model in which to edit its response.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Expand the Response Options panel. Settings for this panel display.
From the Wait for Signature setting, select one of these options:
Yes: Select Yes to wait for the user to sign this document. When this option is selected, the Request pauses and does not resume until the document is signed.
No: Select No to continue the Request irrespective of whether the user signs this document. This is the default option.
In the Output Variable setting, enter the Request variable in which to save the response from DocuSign.
Loop Characteristics Panel Settings
Specify Characteristics to Perform Multiple Instances of the Task
Use the Loop Characteristics panel settings to specify how to perform multiple instances of this element. The following loop modes are available for this element:
No Loop Mode: Select the No Loop Mode option to perform this element's Task only once.
Loop: Select the Loop option to sequentially repeat this element's Task multiple times until an exit condition is
True
. This is useful when a Task should be performed multiple times with the same set of data, such as, processing a credit card payment. This loop mode has the following characteristics:The element's Task is repeated until the exit condition is
True
or the maximum iterations limit is reached.At any given time, only one instance of the Task is active. The subsequent instance does not begin until the current instance completes.
The same exit condition evaluates at the end of each instance; however, value(s) of the Request variable(s) used in the exit condition can change during an instance resulting in the exit condition to eventually evaluate as
True
.If any one instance of that Task does not complete, workflow pauses.
All active instances are terminated if an interrupting boundary-type event element triggers.
Multi-instance (Parallel): Select the Multi-instance (Parallel) option to perform this element's Task multiple times in parallel a fixed number of times. This is useful when performing any action in bulk, such as sending an email to several people. This loop mode has the following characteristics:
Instances of the Task are governed by the size of an array-type Request variable where a new instance is created for each item in this variable. For example, an array with 10 items will create 10 parallel instances of this Task that each contains data from its respective array index.
All instances begin simultaneously when this element triggers; however, they perform their Task independently of each other.
The Task as a whole completes when all instances are complete.
The output from each instance can either be saved in the source Request variable or a new array-type Request variable.
All active instances terminate if an interrupting boundary-type event element triggers.
Multi-instance (Sequential): Select the Multi-instance (Sequential) option to perform this element's Task multiple times sequentially a fixed number of times or until an exit condition is
True
. This is useful when sequentially repeating a Task multiple times but with a different set of data each time. This loop mode has the following characteristics:Instances of the Task are governed by the size an array-type Request variable where a new instance is created for each item in this variable. For example, an array with 10 items will create 10 parallel instances of this Task that each contains data from its respect array index.
At any given time, only one instance of the Task is active. The subsequent instance does not begin until the current instance completes.
At the end of each instance an exit condition evaluates and the loop activity halts if the exit condition is
True
.The Task as a whole completes when all instances are complete.
The output from each instance can either be saved in the source Request variable or a new array-type Request variable.
All active instances terminate if an interrupting boundary-type event element triggers.
Follow these steps to specify characteristics to perform multiple instances of the Task:
Select the element from the Process model in which to specify multiple instance characteristics.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Expand the Loop Characteristics panel. The Loop Characteristics setting displays. By default, Loop Activity is set to No Loop Mode and the Task is performed only once.
From the Loop Mode setting, select one of the following options to perform this element's Task more than once.
Loop: Select the Loop option. The settings for this loop mode display:
Follow these steps:
In the Maximum Iterations setting, enter an integer value representing the maximum number of times this Task should be performed.
In the Exit Condition setting, enter a condition in FEEL syntax. When this condition is True the loop activity is halted.
Multi-instance (Parallel): Select the Multi-instance (Parallel) option. The settings for this loop mode display:
Follow these steps:
In the Request Variable Array setting, enter the name of an array-type Request Variable. The size of this array will determine how many times this loop iterates.
In the Output Data Variable setting, enter the name of an array-type Request variable in which to store the results of all instances. Each instance of the loop saves to a separate JSON object within the array of the specified Request variable. If the Output Data Variable setting is not configured, then the output data replaces the source data in the Request Variable Array.
Multi-instance (Sequential): Select the Multi-instance (Sequential) option. The settings for this loop mode display:
Follow these steps:
In the Request Variable Array setting, enter the name of an array-type Request Variable. The size of this array will determine how many times this loop iterates.
In the Exit Condition setting, enter a condition in FEEL syntax. When this condition is True the loop activity is halted.
In the Output Data Variable setting, enter the name of an array-type Request variable in which to store the results of all instances. Each instance of the loop saves to a separate JSON object within the array of the specified Request variable. If the Output Data Variable setting is not configured, then the output data replaces the source data in the Request Variable Array.
Documentation Panel Settings
Edit the Connector's Description Displayed in Process Documentation
Describe the connector's purpose and how it functions in the Process. This description does not affect Requests for the Process, but may be useful for Process model maintenance such as how the connector is configured. Edit information by using the What-You-See-Is-What-You-Get (WYSIWYG) rich text editor.
A Process's entered documentation displays by selecting the View Documentation icon for that Process.
Follow these steps to edit the description for a connector:
Select the connector from the Process model in which to edit its description.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Follow these guidelines to use the WYSIWYG rich text editor to stylize your text:
Select the required text from the Rich Text control.
In the URL setting, enter the destination URL.
In the Text to display setting, edit or enter the text displayed in the Rich Text control.
In the Title setting, enter the text to display when a user hovers over the displayed text.
From Open link in… drop-down menu, select one of these options:
New window: Select this option to open the destination page in a new browser window.
Current window: Select this option to open the destination page in the current browser window.
In the Source setting, enter a URL for the image.
In the Alternative Description setting, enter the text to display if the source URL of the image is not accessible.
In the Width setting, enter the maximum width for the image.
In the Height setting, enter the maximum height for the image.
Click Save.
Format text: Follow these guidelines to format text:
Headings: From the Paragraph/Formats menu, select Headings and then select a heading size.
Bold: Do one of the following:
From the Paragraph/Formats menu, select Inline and then Bold.
Italics: Do one of the following:
From the Paragraph/Formats menu, select Inline and then Italic.
Underline: From the Paragraph/Formats menu, select Inline and then Underline.
Strikethrough: From the Paragraph/Formats menu, select Inline and then Strikethrough.
Superscript: From the Paragraph/ Formats menu, select Inline and then Superscript.
Subscript: From the Paragraph/Formats menu, select Inline and then Subscript.
Code: From the Paragraph/Formats menu, select Inline and then Code.
Paragraph: From the Paragraph/Formats menu, select Blocks and then Paragraph.
Blockquote: From the Paragraph/Formats menu, select Blocks and then Blockquote.
Division: From the Paragraph/Formats menu, select Blocks and then Div.
Preformatted: From the Paragraph/Formats menu, select Blocks and then Pre.
Select one of the color swatches from the color palette. The selected text changes to that color.
Align text: Follow these guidelines to align text:
Left align: Do one of the following:
From the Paragraph/Formats menu, select Align and then Left.
Center align: Do one of the following:
From the Paragraph/Formats menu, select Align and then Center.
Right align: Do one of the following:
From the Paragraph/Formats menu, select Align and then Right.
Justify: Do one of the following:
From the Paragraph/Formats menu, select Align and then Justify.
Advanced Panel Settings
Edit the Node's Identifier Value
A Process node represents a component of a Process model, whether that is a BPMN element or a connector. Process Modeler automatically assigns a unique value to each Process node added to a Process model. A Process node's identifier value can be changed if it is unique to all other nodes in the Process model, including the Process model's identifier value.
All identifier values for all nodes in the Process model must be unique.
Follow these steps to edit the identifier value for a connector:
Select the connector from the Process model in which to edit its identifier value.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
Expand the Advanced panel if it is not presently expanded. The Node Identifier setting displays. This is a required setting.
In the Node Identifier setting, edit the connector's identifier to a unique value from all nodes in the Process model and then press Enter.
Last updated