Use the Integrator shape in a process to send or receive data from an external application in a way that continues flow processing as soon as the Connect activity completes. By integrating external applications with your process, you can add more functionality to your application. For example, you can use the Integrator shape to retrieve customer account balances or verify account numbers in an external database.
- Ensure that the process in which you want to use an Integrator shape already exists. For more information, see Creating a top-level case type.
- Build your own Connect rule, and then build a Connect activity that maps the data from the service that you called into your case. For more information, see Connect REST rules and Creating a REST integration by using the Create REST integration wizard.
The Integrator shape identifies an activity that connects your instance of Pega Platform to an external system to send or receive data. The Integrator
shape runs synchronously, meaning that it must receive a response immediately, and then
moves a case to the next step.
- Add the Integrator shape to your process.
- In the navigation pane of Dev Studio, click App.
- On the Classes tab, expand the case type in which you want to add the assignment, and then click .
- In the list of Flow instances, double-click a flow that you want to open.
- On the Flow form, on the Diagram tab, click the Flow shapes icon, and then click .
- Drag the Integrator shape to the flow diagram, and place the shape based on the order of events in the process.
- Connect the Integrator shape by dragging connector end points to connection points on different shapes in the process.
- Modify the Integrator shape to send a request from a process to an external
- Double-click the Integrator shape to open the property pane.
- In the Integrator field, enter a name for the shape.Choose a name that is meaningful to users who see this on the work object history display, in the breadcrumbs control (for entry points), and inside the Integrator shape on the Diagram tab.
The task name does not affect run-time processing of the flow.
- In the Rule field, press the Down arrow key, and then select the name of a connect activity.
- If the connector requires parameters, the system provides a list of response and request data transforms generated by the accelerator. Use the generated request data transform to define the mapping of application (source) properties to connector request (target) properties. Use the generated response data transform to define the mapping of connector response (source) properties to application (target) properties.
- Optional: To control the text of instances added to the work item history when flow processing completes this shape, in the Audit Note field, select or enter the name of a Rule-Message rule.
- Optional: To provide a link to this step from the breadcrumb trail navigation, select the Enable navigation link check box.
- Optional: To update the status of a case on this shape, in the Work
status field, press the Down arrow key, and then select a value that you
want to apply.For more information, see Changing case statuses.
- Optional: To activate a ticket in a flow that detects an exception, error flow or event, in
the Tickets section, in the Ticket name
and the Display name fields, press the Down arrow key, and then
select the values that you want to apply.
For more information, see Responding to business exceptions in a flow. Note: You can use more tickets by adding a row for each ticket. If a shape has more than one ticket associated with it, then processing of that task continues only after all tickets are set.
- Click Submit to close the property pane.
- Click Save.