Flow form
Editing Integrator shape properties

Field

Description

Assign a name to the Integrator task. Choose a name meaningful to application users who see this on the work object history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. B-16966.

The task name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Integrator shape on the Diagram tab.

Select an activity with an Activity Type of Connect.

Optional. Select the name of the application that you want to link to the flow shape. The value of this field is referenced with the flow diagram in application documents. 5.4 Proj-831

Optional. Select the name of the work type for the application that you want to link to the flow shape. The value of this field is referenced with the flow diagram in application documents. 5.4 Proj-831

Optional. Select the name of the use case for the application and work type that details the implementation requirements for the flow shape. The value of this field is referenced with the flow diagram in application documents and on the Implementation tab of the corresponding Application Use Case rule. 5.4 Proj-831

If the activity requires parameters, a list of parameters appears. Enter parameter values.

Optional. Select a service level rule to apply to this task. For example, a service level can cause escalation processing when no response is received from the external system after 60 seconds.

This may indicate that the external system is unavailable or that other technical problems are present. See Handling connector exceptions. A GUESS /?? IS THIS FUNCTIONAL?

Optional. Select or enter the name of a Rule-Message rule to control the text of an instances added to the work object history (the "audit trail") when a flow execution completes this shape. B-18887 Process Commander includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work object history displays can be localized. See About the Localization wizard.)

Optionally, to reduce the volume of history detail instances, your application can prevent system-generated messages from being added to work object history. See Controlling the volume of generated work object history instances and the Pega Developer Network article PRKB-25196 How to control history instances written to the audit trail.

Select to indicate that this Integrator task is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Work-.Previous. The default is cleared. 5.2

This checkbox works with Perform harness rules that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the checkbox has no effect.

Because an Integrator task presents no user form, if a user clicks a breadcrumbs control to return to this entry point, flow processing resumes and pauses at the next assignment or other task that requires user input.

This checkbox appears only when you select the Entry Point? checkbox. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it.

For maximum user flexibility, leave this checkbox unselected if your flow accepts inputs in any order. However, this approach is typically not workable for flows that contain fork and decision shapes, or that have intermediate tasks that are not entry points.