Flow form
Editing the Router shape properties

Field

Description

Assign a name for this Router task . Choose a name meaningful to application users who see this on the work object history display and the Where-Am-I? diagram. . For example, Route to Closest Adjuster.

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.

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.

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

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 AssignTo parameter is an output, not an input, of an activity of type Router. Don't complete a value for the AssignTo parameter.

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

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.