IDP Connector in Processes
Last updated
Last updated
IDP connector integrates ProcessMaker IDP into ProcessMaker Platform enabling Process Designers to use IDP in their processes.
Remember before working correctly with IDP Connectors, your administrator must configure .
Add an IDP connector from one of the following locations in Process Modeler:
Object menu: The Object panel is to the left of the Process Modeler canvas. This menu contains Process model objects and 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 Process model objects which are easily accessible to add to the Process model.
The IDP connector has the following panels that contain settings:
Configuration panel
Loop Activity panel
Advanced panel
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 an IDP connector:
Select the IDP connector from the Process model.
During a Request, an IDP connector references a Request variable that stores the documents for processing. This Request variable may be linked to a File Upload control, where the documents were uploaded during a Task.
Follow these steps to enter the name of the Request variable that stores the documents to be processed by this IDP connector:
Select or enter the document type the IDP connector uses to process the documents. This setting does not refer to a file type, such as PDF
or DOCX
. Instead, this setting refers to the DOCUMENT_TYPE
domain in ProcessMaker IDP that has been previously trained to process documents in your Dossier. Note that this setting requires the value inDOCUMENT_TYPE
Domain's Name setting, not its Pretty Name setting value.
Follow these steps to select a document type:
Expand the Configuration panel if it is not presently expanded, and then locate the Select Document Type setting.
Do one of the following:
The Split Document(s) setting allows users to upload a multi-page PDF where each page is an independent document, such as multiple invoices in one PDF. The IDP Connector then splits the PDF into individual documents, creating a new document for every page when uploading to the IDP environment. This helps users manage and track multiple documents simultaneously, making workflows more organized and efficient. This is especially useful for large-scale operations where handling each document individually would be time-consuming.
Follow these steps to split a document:
Select the Split Document(s) option.
Select the folder where ProcessMaker IDP should store the processed documents. Follow these steps to configure a destination folder:
Expand the Configuration panel if it is not presently expanded, and then locate the Select Destination setting.
Do one of the following:
Use the Loop Characteristics panel settings to specify how to perform multiple instances of this connector. The following loop modes are available for this connector:
No Loop Mode: Select the No Loop Mode option to perform this connector's function only once.
Loop: Select the Loop option to sequentially repeat this connector's function multiple times until an exit condition is True
. This is useful when a function 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 connector's function is repeated until the exit condition is True
or the maximum iterations limit is reached.
At any given time, only one instance of the connector 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 function does not complete, workflow pauses.
All active instances are terminated if an interrupting boundary-type event element triggers.
ProcessMaker IDP does not allow multiple documents of the same name in the one folder. Therefore, an IDP connector cannot send more than one copy of a document to a folder while in a loop mode. To address this issue, use a different IDP connector to process the same document to a different ProcessMaker IDP folder.
Multi-instance (Parallel): Select the Multi-instance (Parallel) option to perform this connector'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 connector 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 function that each contains data from its respective array index.
All instances begin simultaneously when this connector triggers; however, they perform their function independently of each other.
The function 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 connector's function multiple times sequentially a fixed number of times or until an exit condition is True
. This is useful when sequentially repeating a function multiple times but with a different set of data each time. This loop mode has the following characteristics:
Instances of the function 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 function that each contains data from its respect array index.
At any given time, only one instance of the function 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 function 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 connector:‌
From the Loop Mode setting, select one of the following options to perform this connector's function 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.
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 an IDP connector:
In the Node Identifier setting, edit the IDP connector's identifier to a unique value from all nodes in the Process model and then press Enter.
.
.
.
.
element
element
element
element
element
Click the Show Configuration button in the upper right of the Process Modeler canvas to view the Configuration panel.
In the Name setting, edit the selected connector's name and then press Enter.
Expand the Configuration panel if it is not presently expanded, and then locate the Variable Name setting.
In the Variable Name setting, enter the Request variable name that stores the documents for processing without using , then press Enter.
Click the initials of your user account in the lower-left in ProcessMaker IDP, and then select the Go to ProcessMaker IDP Admin option.
Click the Domains option from the left navigation pane.
Select the Use Request Variable option, and enter a Request variable that contains a reference to the document type. Reference this Request variable without using .
Ensure that the Use Request Variable setting is not selected, then choose a document type from the drop-down list. The name of the document type must already exist in ProcessMaker IDP. This setting does not create a new file type. For more information, see .
Expand the Configuration panel if it is not presently expanded, and then locate the Split Document(s) setting.
Select the Use Request Variable option, and enter a Request variable that contains a reference to the destination folder in IDP where to upload the file. Otherwise, if the folder does not exist, it creates a new one in the IDP server. Reference this Request variable without using .
Ensure that the Use Request Variable setting is not selected, then choose a destination folder from the drop-down list. These folders already exist in ProcessMaker IDP and are configured in the
An element configured in this mode shows the Loop icon in Process Modeler.
A connector configured in this mode shows the Multi-instance (Parallel) icon in Process Modeler.
A connector configured in this mode shows the Multi-instance (Sequential) icon in Process Modeler.
Expand the Loop Characteristics panel. The Loop Characteristics setting displays. By default, Loop Activity is set to No Loop Mode and the function is performed only once.
Expand the Advanced panel if it is not presently expanded. The Node Identifier setting displays. This is a required setting.