Flow form
|
C-640 Optional. A router activity determines which workbasket, worklist, or agent is to receive an assignment. See Atlas — Standard activities for use in flows (interactive).
Associate a router activity with each assignment, unless the assignment is always to appear on the worklist of the current user (the one who is currently executing the flow rule).
For flows created or edited
with V5.5 or later, the Router shape is optional. If you prefer,
you can record the Router activity directly in the Assignment shape or the Swimlane shape
properties panels. You cannot add a router shape to an assignment shape inside a swimlane. See Flow form
Editing in Visio — Swimlane tasks. GRP-201 5.5 and GRP-198
1. Drag the router shape () onto the flow and drop it.
2. When the Router Properties panel appears, complete these fields:
Field |
Description |
Name |
Assign a name for this Router task of 32 characters or less. Choose a name meaningful to application users who see this on the work object history display and the Where-Am-I? diagram. B-16966. For example, Route to Closest Adjuster. BUG-2983 The task name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Router shape on the Diagram tab. |
Rule |
Select a router activity that determines which workbasket or operator worklist is to receive the assignment. See Atlas — Standard activities for flows to read about a few standard router activities. |
Parameters |
If you choose a router activity that requires parameters, such as the name of an operator, skills required, or the name of a workbasket, complete the parameters. Process Commander validates these parameter values when you exit from Visio editing (unless the flow in is Draft mode). 5.5 GRP-405 You can use the notation param.name in a parameter field to refer to a flow parameter that you want to be the source of an activity parameter value.
The
|
Audit Note |
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. |
Audit Note |
Optional. Text you enter here appears in the history of the work object, recording that this router task was processed. When you plan to localize the application using this rule, so the application can support users in various languages or locales, choose the text carefully and limit text length to 64 characters. A field value rule with this text as the final key part is needed for each locale. When practical, choose a caption already included in a language pack, to simplify later localization. See About the Localization wizard. |
3. Click Apply when finished.
4. Attach the connector of the router symbol to the top center of the assignment shape. Visio changes the connector end to red when the shape is correctly attached.
(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.) GRP-202
You can add a Router shape by dragging an activity rule instance of type Route from the Application Explorer onto the Visio diagram. Click the icon to select the rule. See Using the Application Explorer. V6.1 Proj-179 GRP-2259