Flow form - Process Modeler - Editing Decision shapes

At runtime, the system evaluates the decision rule based on inputs from the flow and the work item, and chooses one of the outgoing connectors based on the result. No user interaction or input is required.

For example, a decision shape for a credit card processing application may select one of three paths A, B, or C in the flow based on two input values — a card type (Standard, Silver, or Gold) and an amount.

1. Right-click on a blank area of the canvas.

2. Hover over Add on the submenu to display a list of tasks you can add to the flow.

3. Click the name of the shape you want to add to the flow. will the properties panel display by default? Not yet -- too complicated if you add multiple at once, per Joan. You can add multiple shapes without saving the flow.If the properties panel displays by default, it would have to close one before you add a new assignment

4. Right-click the decision shape and select Properties to display the properties panel.

6. When the Decision Properties panel appears, complete complete the Name field.

7. Choose a decision rule Type: Boolean Expression, Decision Table, Decision Tree, Fork, or Map Value.

8. Complete the fields that appear for that type as described in the tables below. (To edit the shape properties after you save the Flow form, open the Diagram tab, right-click the shape, and select Properties.)

7. Click OK when finished.

8. Click and drag the shape as needed to position it in the flow.

8. Connect at least one incoming connector to the decision shape.

9. Connect two or more outgoing connectors from the decision shape.

-Copy/Paste - Ctrl c on Decision, then Ctl V to make a copy (eventually)

Select shape from plus-sign style icon and drop-down menu on toolbar (eventually)

If the decision table or decision tree you reference has no more than five possible results, the outgoing connectors appear automatically when you drop the shape. You can add to, delete, rearrange, and modify such automatic connectors as desired. If the decision rule has more than five possible results, five connectors appear automatically. Make sure each distinct decision outcome has an appropriate connector condition. still true ? What if it's a fork--?

You can add a Decision shape by dragging and dropping a map value, decision tree, or decision table rule instance from the Application Explorer onto the Process Modeler flow diagram. Click the icon to select the rule. See Using the Application Explorer. still true?

Field	Description
Name	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. For example: Customer Limit Check. 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.
Type	`Boolean Expression`
Expression	Enter an expression that returns true or false, for example: .myProperty == "Yellow" See About expressions. REMOVED SECOND VALUE TO COMPARE MARIK 3/9/06`MB-16677 MARIK 1/5/06 ZELEK 1/6/06`
Result in	Optional. Select a target property to contain the result of the expression.
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. 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.
Entry Point	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`
Only going back	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.
Post Action on Click Away	This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

Click Apply .

At runtime, the system evaluates this Boolean expression. In the connectors leading from this decision shape, you can use the result in Status comparisons.

The system evaluates connectors in order of decreasing likelihood. Flow execution continues along the first connector that evaluates to true.

Field	Description
Name	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. For example: Customer Limit Check. 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.
Type	`Decision Table`
Rule	Select a decision table rule, identified by the second key part.
Result in	Optional. Select a target property to contain the result of the chosen rule.
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.) 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.
Entry Point	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.
Only going back	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.
Post Action on Click Away	This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

At runtime, the system evaluates the decision table rule based on the input value you supply and the value of any other properties it references. Two connectors (one for true and one for false) leading from this decision shape can use the result.

The system evaluates connectors in order of decreasing likelihood. Flow execution continues along the first connector that evaluates to true.

Field	Description
Name	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. 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.
Type	`Decision Tree`
Rule	Select a decision tree rule, identified by the second key part.
Input	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.
Result in	Optional. Select a target property to contain the result of the chosen rule.
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.
Entry Point	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`
Only going back	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.
Post Action on Click Away	This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

At runtime, the system evaluates the decision tree rule based on the input value you supply and the value of any other properties it references. Your connectors leading from this decision shape can use the result (the output of the decision tree) in Status comparisons.

The system evaluates connectors in order of decreasing likelihood. Flow execution continues along the first connector that evaluates to true.

Field	Description
Name	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.
Type	`Fork`
Entry Point	Select to indicate that this fork 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` XXXXX Make sure these next 2 paras are still true.This checkbox works with Perform harness rules that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the checkbox has no effect. Because a fork 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.
Only going back	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.
Post Action on Click Away	This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

XXXXX Make sure these next 2 paras are still true. Copied from diagramfork.htm.

Associate a likelihood value between 1 and 99 for each outgoing connector. At runtime, the system evaluates the conditions on connectors in order of decreasing likelihood. Choose distinct likelihood values if you care about the order. (Often, only one of the outgoing connector conditions is true, so the order of evaluation does not matter.)

Set up the tests (When conditions or expressions) on each connector so that at least one of them evaluates to True at runtime. You can set the condition on the least-likely connector to ELSE to make it a none-of-the-above choice.

You can reference a one- or two-dimensional map value rule.

Field	Description
Name	Enter a text name for this shape. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs display (for entry points), and the Where-Am-I? diagram. The task name is descriptive only; it does not affect the runtime execution of the flow. The name appears on the Decision shape on the Diagram tab
Type	`Map Value`
Rule	Select a map value rule, identified by the second key part.
Row Input	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.
Column Input	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.
Result in	Optional. Select a target property to contain the result of the chosen rule.
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.
Entry Point	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.
Only going back	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.
Post Action on Click Away	This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

At runtime, the system evaluates the map value rule using one or two values supplied by this settings dialog box, and compute a result value. The decision result (a text value) is the basis of the decision, using outgoing connectors and the Status comparison.

For example, if the map value returns values "Red", "Green", or "Yellow", the flow can include four connectors flowing from the Decision task shape, all corresponding to Status comparisons. One connector compares the returned value to "Red", one to "Green", one to "Yellow", and a fourth can become the default (Else) connector.

Flow form Process Modeler — Editing Decision shapes

Field

Description

Field

Description

Field

Description

Field

Description

Field

Description

Flow form
Process Modeler — Editing Decision shapes