Flow form
Editing Decision shape properties

Field

Description

Enter a text name for this 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. BUG-2983Removed Enter a name that is no more than 32 characters long. B-16966

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

Map Value

Select a map value rule, identified by the second key part.

Optional. Enter a literal text value or a property reference that becomes the input value for the row of the map value at runtime. When you leave this blank, the row property identified on the Inputs tab is used as the source of the value.

Optional. If the map value rule selected has two dimensions, enter a literal value or a property reference that becomes the input value for the column of the map value at runtime. When you leave this blank, the column property identified on the Inputs tab is used as the source of the value.

Optional. Select a target property to contain the result of the chosen rule.

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.

Select to indicate that this decision 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. 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 tasks that are not entry points.

Field

Description

Enter a text name for this 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. Enter a name that is no more than 32 characters long.B-16966. For example: CustomerLimitCheck.

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

Decision Tree

Select a decision tree rule, identified by the second key part.

Optional. Enter a literal text value or a property reference that becomes the input value for the decision tree at runtime. If you leave this blank, the system uses the value of the property identified on the Input tab.

Optional. Select a target property to contain the result of the chosen rule.

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.

Select to indicate that this decision 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. 5.2

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 allows inputs to arrive in any order. However, this approach is typically not workable for flows that contain fork and decision shapes, or that have intermediate tasks that are not entry points.

Field

Description

Enter a text name for this 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. Enter a name that is no more than 32 characters long. For example: Customer Limit Check.BUG-2983

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

Decision Table

Select a decision table rule, identified by the second key part.

Optional. Select a target property to contain the result of the chosen rule.

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

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.

Select to indicate that this decision 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. 5.2

Because a decision task presents no user form, if a user clicks a breadcrumbs control to return to this entry point, flow processing resumes and pauses at the next assignment or other task that requires user input.

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 allows inputs to arrive in any order. However, this approach is typically not workable for flows that contain fork and decision shapes, or that have intermediate tasks that are not entry points.

Field

Description B-16677 BUG-516

Enter a text name for this shape of 32 characters or less. 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. For example: Customer Limit Check.BUG-2983

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

Boolean Expression

Enter an expression that returns true or false, for example:

.myProperty == "Yellow"

See About expressions. REMOVED SECOND VALUE TO COMPARE MARIK 3/9/06MB-16677 MARIK 1/5/06 ZELEK 1/6/06

Optional. Select a target property to contain the result of the expression.

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.

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.

Select to indicate that this decision 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. 5.2

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 allows inputs to arrive in any order. However, this approach is typically not workable for flows that contain fork and decision shapes, or that have intermediate tasks that are not entry points.