CDATA External Integration
Configure a CDATA External Integration.
Overview
CDATA External Integrations integrates with a large library of third-party applications and services. CDATA External Integrations are easy to configure after the driver is authenticated with the third-party service in Settings.
A CDATA External Integration that ProcessMaker Platform supports is not available from Process Modeler until the Administrator does the following in this order:
From Settings, add the CDATA driver for one of the following third-party applications and services:
DocuSign
GitHub
Microsoft Excel
Slack
Configure that CDATA driver to authenticate with the external integration.
Permissions Required
Your user account or group membership must have the following permissions to configure a CDATA connector unless your user account has the Make this user a Super Admin setting selected:
Processes: Edit Processes
Processes: View Processes
See the Process permissions or ask your Administrator for assistance.
Add a CDATA External Integration to the Process Model
Add a CDATA External Integration from one of the following locations in Process Modeler:
Explorer panel: The Explorer panel is to the left of the Process Modeler canvas. The Explorer panel contains Process model objects and PM Blocks which may be added to the Process model.
Objects bar: The Objects bar is at the bottom of the Process Modeler canvas. This bar contains pinned Process model objects which are easily accessible to add to the Process model.
Follow these steps to add a CDATA External Integration from the Explorer panel to the Process model:
Locate the CDATA object category from one of the following locations in the Explorer panel:
Pinned Objects: The CDATA object category displays from the Pinned Objects section when it is pinned. This element type is not pinned by default.
Object Category: The CDATA object category displays at the end of the Object Category section when it is not pinned.
Click the CDATA object category as follows:
Its icon displays adjacent to the mouse icon to indicate this connector type may be placed into the Process model.
Click the location in the Process model to place this connector. If a Pool element is in your Process model, the CDATA External Integration cannot be placed outside of the Pool element.
After adding the CDATA External Integration, consider adding the following Boundary-type Process model elements to design business solutions when your best-case scenarios don't happen:
Boundary Timer Event element (Don't know what that is?)
Boundary Error Event element (Don't know what that is?)
After the CDATA External Integration is placed into the Process model, you may adjust its location in the following ways:
Move the CDATA External Integration by dragging it to a new location.
Select the CDATA External Integration with other objects and/or PM Blocks, and then move them collectively by dragging them to new locations in relation to one another.
Align and/or distribute the CDATA External Integration in relation to other selected elements and/or connectors.
Moving a CDATA External Integration has the following limitations in regards to the following Process model elements:
Pool element: If the CDATA External Integration is inside of a Pool element, it cannot be moved outside of the Pool element. If you attempt to do so, Process Modeler places the CDATA External Integration inside the Pool element closest to where you attempt to move it.
Lane element: If the CDATA External Integration is inside of a Lane element, it can be moved to another Lane element in the same Pool element. However, the CDATA External Integration cannot be moved outside of the Pool element.
Change a CDATA External Integration's Appearance
See Customize the Appearance of a Process Model Object.
Copy a CDATA External Integration
See Copy Process Model Objects into the Clipboard.
Clone a CDATA External Integration
See Clone Process Model Objects Without the Clipboard.
Delete a CDATA External Integration
See Delete Process Model Objects.
Settings
The CDATA connector has the following panels that contain settings:
Properties panel
Loop Activity panel
Query panel
Response Mapping panel
Error Handling panel
Documentation panel (available when the Documentation package is installed)
Advanced panel
Configuration Panel Settings
Edit the CDATA External Integration Name
A CDATA External Integration name is a human-readable reference for a Process model control. Process Modeler automatically assigns the name of a Process model connector with its type. However, a connector's name can be changed.
Follow these steps to edit the name of a CDATA External Integration:
Select the CDATA External Integration 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 Properties panel if it is not presently expanded. The Name setting displays.
In the Name setting, edit the selected External Integration's name and then press Enter.
Loop Activity Panel Settings
Specify Characteristics to Perform Multiple Instances of the CDATA External Integration
Use the Loop Activity panel settings to specify how to perform multiple instances of this CDATA External Integration. The following loop modes are available for this External Integration:
No Loop Mode: Select the No Loop Mode option to perform this element's External Integration only once.
Loop: Select the Loop option to sequentially repeat this element's External Integration multiple times until an exit condition is
True
. This is useful when a External Integration 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 External Integration is repeated until the exit condition is
True
or the maximum iterations limit is reached.At any given time, only one instance of the External Integration 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 External Integration 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 External Integration 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 External Integration 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 External Integration that each contains data from its respective array index.
All instances begin simultaneously when this element triggers; however, they perform their External Integration independently of each other.
The External Integration 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 External Integration multiple times sequentially a fixed number of times or until an exit condition is
True
. This is useful when sequentially repeating a External Integration multiple times but with a different set of data each time. This loop mode has the following characteristics:Instances of the External Integration 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 External Integration that each contains data from its respect array index.
At any given time, only one instance of the External Integration 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 External Integration 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 CDATA External Integration:
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 External Integration display.
Expand the Loop Characteristics panel. The Loop Characteristics setting displays. By default, Loop Activity is set to No Loop Mode and the External Integration is performed only once.
From the Loop Mode setting, select one of the following options to perform this External Integration 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 External Integration 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.
Query Panel Settings
Enter SQL Queries
Enter SQL queries to interact data with the CDATA External Integration such as storing, manipulating and retrieving data.
Follow these steps to enter SQL queries:
Select the connector from the Process model.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
In the SQL setting, enter queries to interact with the CDATA External Integration.
Press enter to save queries.
Response Mapping Panel Settings
Map Data from the Data Source to the Request's JSON Data Model
Configure how data from the CDATA External Integration source integrates with Request data.
The procedure to integrate the data source's data to the Request JSON data model is called response mapping: specifying into which Request variable to store the data source's data. The External Integration may be configured with response mapping, whereby a specified source name in the body or header of the data source response's is mapped to store that value in a specified Request variable. By relying on the CDATA External Integration's response mapping, the Process Designer only needs to select the Request variable name as mapped in the CDATA External Integration's response without knowing technical details for this mapping.
Each JSON object contains a key name that references the JSON object, and the value for that key. If the JSON object already exists in a Request's JSON data model, then the CDATA External Integration overwrites the existing JSON object value with that from the data source. If the JSON object(s) to map the data source data does not exist, then the CDATA External Integration adds the JSON data object(s) to that Request's JSON data model.
Follow these steps to specify the Request JSON data object(s) to which to map the data source's data:
Select the External Integration from the Process model to map the data source's data to the Request JSON object(s).
Ensure that the Configuration panel displays. If not, show it. Panels to configure this element display.
In the Source setting, enter the name of the source from which to store the response. If the source is from Request data, such as from a Collection, the source name is
data
.data
is the name of the JSON object that stores all data for each Request. However, the Source setting corresponds with how the CDATA External Integration maps the data response: by selecting a mapped Request variable from the Set to Request Variable setting below, its corresponding source name displays in the Source setting. Optionally, specify the source name as a Request variable using mustache syntax.In the Set to Request Variable setting, enter the Request variable as configured in the CDATA External Integration's response mapping in which to store the data source's response. Optionally, specify the source name as a Request variable using mustache syntax. After doing so, the Source setting displays the source's name configured for that response mapping.
Click Save.
Repeat Steps 4 through 6 for each Request variable to store the data source's response.
Error Handling Panel Settings
Edit Timeout and Retry Settings When Errors Occur
Follow these guidelines to set how to handle CDATA External Integration runtime errors:
Set how many seconds to wait when an unexpected error occurs during runtime before displaying the error in that connector, thereby causing that Request to be in Error status.
Set how many consecutive attempts to run the connector before displaying a runtime error.
Requests are going to wait the configured number of seconds and consecutive runtime attempts for an unresponsive connector before displaying the error.
Optionally, notify the Process Manager of the External Integration runtime error via an in-platform or email notification.
Follow these steps to edit the Error Handling settings for a CDATA External Integration:
Select the CDATA External Integration from the Process model in which to edit the Error Handling.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this External Integration display.
In the Timeout setting, configure how many seconds to wait for an unresponsive External Integration before declaring a time-out as follows:
Enter the number of seconds. Use the up and down arrows to increase or decrease seconds.
Set
0
for no timeout.Leave empty to use the External Integration default setting.
In the Retry Attempts setting, configure how many times to re-execute the External Integration if the connector returns a runtime error as follows:
Enter a number. Use the up and down arrows to increase or decrease the number.
Set
0
for no retry attempts.Leave empty to use the External Integration default setting.
In the Retry Wait Time setting, configure how many seconds to wait before attempting a retry as follows:
Enter the number of seconds. Use the up and down arrows to increase or decrease seconds.
Set
0
for no timeout.Leave empty to use the External Integration default setting.
Enable the In-app Notification toggle to notify through the user interface to the Process Manager that there is a External Integration runtime error.
Enable the Email Notification toggle to notify through an email to the Process Manager that there is a External Integration execution error.
Documentation Panel Settings
Edit the CDATA External Integration's Description Displayed in Process Documentation
If the Documentation package is installed, describe the CDATA External Integration'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.
Package Required
The Documentation package must be installed to view or edit the documentation for a Process element or connector. Use the Documentation package to view documentation for Processes that includes an image of the Process map and entered description of its elements and connectors.
Follow these steps to edit the description for a CDATA External Integration:
Select the CDATA External Integration from the Process model in which to edit its description.
Ensure that the Configuration panel displays. If not, show it. Panels to configure this External Integration 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, including any of its objects. 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 CDATA External Integration:
Select the CDATA External Integration 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 External Integration 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 External Integrations's identifier to a unique value from all nodes in the Process model and then press Enter.
Related Topics
Documentation PackageLast updated