Back Forward Flow form
Editing in Process Modeler — Integrator shape

About Flows
  1. About 
  2. New 
  3. Diagram 
  4. Parameters 
  5. Pages & Classes 
  6. Design 
  1. Process 
  2. Specifications 
  3. Requirements 
  4. Test Cases 
  5. History 
  6. More... 

An Integrator shape identifies an activity that connects your PRPC system to an external system to send or receive data.

The indicates that one or more tickets are defined on the integrator. Assigned ticket names appear beside this icon on the flow.

Purpose

An integrator shape can connect to a customer master database to retrieve account balances or verify account numbers and status. Integrator shapes use activities (with Connect as the Activity Type) that call connector rules (Rule-Connect- rule types).

Configuration

Advanced

Complete the Status and Tickets sections as described below.

Status

Field

Description

Work status

Enter a work status in this field to set the status for the work item. This allows you to easily change the status at multiple points in the life cycle of a work item without adding a Utility shape to the flow for each status change. Similar to setting work item status using a Utility shape, setting the status invokes the UpdateStatus activity. Any defined tickets dependent on the status are raised, as appropriate. The selected status updates .pyStatusWork when the flow execution reaches this assignment shape.

A status indicator appears on connectors to shapes that change a work item status. For example, if the shape status is set to Pending-External, the connector to that shape displays a small red flag. All transitions connecting to the shape will display the status indicator. Following are the status indicators for the four status prefixes.

New

Open

Pending

Resolved

Tickets

Add a Ticket Name field to indicate the ticket(s) available at runtime. Use the Ticket to mark the starting point for exceptions that may arise at any point in the flow, such as a cancellation. The ticket is a label for a point in a flow, much like a programming "GOTO" destination.

An activity executing anywhere in your entire PRPC application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter. See Ticket help for other ways to raise a ticket.

The scope of a raised ticket includes all flows on the current work item that contain this ticket. If found, processing stops on that flow promptly, and resumes at the ticket point.

The system adds to the decision shape to indicate one or more tickets are associated with this decision. The assigned ticket name appears on the flow.

Field

Description

Ticket Name

add row Select one or more tickets that are to be available at runtime from this decision. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.

TipCreating ticket rules is recommended but not required. You can enter here a name that does not correspond to a ticket rule .

NoteIf a shape has more than one ticket associated with it, then processing continues with that task only after all tickets are set.

Example

Processing is connected to a ticket to respond to an exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:

  • Include a ticket named Withdrawn on a utility shape that computes the fees due for work done so far, and any refund amount
  • Follow the utility shape with another that produces correspondence, to alert all parties working on the mortgage that it was withdrawn
  • Connect to external systems to back out (rollback) changes or void accounting entries as appropriate
Display Name The Ticket Name appears by default. Enter a name to display other than the ticket name.
Definitions activity type, breadcrumbs control, connector, entry point
Related topics How to create activities for use in flows
TaskStatus-Set method
Standard rules Standard activities for flows

Up About Flows