Flow form
Editing the Split/Join shape properties
 

Field

Description

Enter a text name for this Split/Join 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 shape name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Split/Join shape on the Diagram tab.

Choose Any or All. Choose:

• All if the current flow is to resume only when all the split subflows return.
• Any, if processing in the current flow is to resume after any one of the split subflows completes. At that time, processing of the other split subflows that have not completed is stopped. Open assignments for these subflows are cancelled. MARIK 1/12/05B-18901

Optional. You can associate a cost value (in any units) with this branch. For each work object, the system computes the sum of these cost values for the specific path it takes through the flow rule. MARIK 1/15/04REMOVED?

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, you can localize the corresponding text on work object history displays. 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. Click the plus sign to access a text box. Text entered here appears as a history instance for the work object recording that this Split/Join shape was started.

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.

Select to indicate that this Split-Join shape is an entry point, which a user can return to using the breadcrumbs control or the standard flow action 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.

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 shapes that are not entry points.