After you add an Assignment Service shape to a flow, you can configure it to call an activity. By using Assignment Service shapes, you can integrate external applications with your process.
Double-click the Assignment Service shape.
Complete the fields in the property panel as described in the following table.
Field |
Description |
Type |
Select an activity with an Activity Type of Three standard activities, stubBPELinvoke, stubBPELreceive, stubBPELreply, defined with Work- as the Applies To class are always choices in this field. |
Parameters |
The activity you select may accept input parameters that will appear in the box below. Supply a value for each parameter. Parameter values are validated when you save the flow unless the flow is in draft mode. |
Audit Note |
Select or enter the name of a Rule-Message rule to control the text that is added to the work item history (the "audit trail") when a flow execution completes this shape. The Pega 7 Platform includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item history displays can be localized.) Optionally, to reduce the volume of history detail instances, your application can prevent system-generated messages from being added to work item history. See the PDN article How to control history instances written to the audit trail. |
Click Submit to close the property panel.
Hover over an existing shape in the flow and drag a connector from it to the Assignment Service shape.
Hover over the Assignment Service shape and drag a connector to an existing shape in the flow.
At run time, flow processing is paused when the Assignment Service shape is reached. The flow resumes when an incoming service request of the appropriate type is received.
Tip: Right-click an Assignment Service shape to view more configuration options.