Back Forward Flow form
Editing Assignment Service shape properties

 About Flow rules

Purpose

zzzUse the Assignment Service task in a flow to pass control to an external system using a connector (for example, Connect BPEL rule). Assignment Service tasks support asynchronous coordination with external systems, in contrast to the Integrator tasks, which support synchronous connections.

Both Integrator tasks and Assignment Service tasks reference an activity of type Connect. For an Integrator task, flow execution continues as soon as the activity completes. For an Assignment Service task, flow execution pauses until Process Commander receives a service request of the appropriate type.

Adding an Assignment Service task to a flow

1. Drag the Assignment Service shape (Assignment-Service) onto the flow and drop it.

2. When the Assignment Service Properties panel appears, complete these fields:

Field

Description
Name

Enter a text name for this Assignment Service shape. 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.

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

SmartPromptSelect an activity with an Activity Type of Connect.

Parameters

If the activity accepts input parameters, a list of parameters appears. Enter parameter values. Process Commander validates these parameter values when you exit from Visio editing.

Service Level

SmartPromptOptional. 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.
Audit Note

SmartPromptOptional. 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. 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.)

NoteOptionally, 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 PDNPRKB-25196 How to control history instances written to the audit trail.
Entry Point?

Select to indicate that this Assignment Service 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.

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

3. Click  Apply   when finished.

4. Connect at least one incoming connector and at least one outgoing connector to the shape.

(To edit these shape properties after you save the Flow form, open the Diagram tab, right-click the shape, and select the Edit tab on the pop-up window.)

zzz About Flow rules