Double-click the Decision shape.
Select an option from the Type list, based on the type of rule that supports the Decision shape.
Options include: Boolean Expression, Decision Table, Decision Tree, Fork, Map Value, Predictive Model, and Scorecard Model.
Complete the fields in the property panel as described in the tables below.
Options for Boolean Expressions:
Field |
Description |
| Expression |
Enter an expression that returns true or false, for example: .myProperty == "Yellow" See About expressions. |
| 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 item history (the "audit trail") when a flow execution completes this shape. The Pega 7 Platform includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item 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 item history. See Controlling the volume of generated work item history instances and the PDN article 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 shape 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. Decision shapes are not typically marked as entry points. |
| Only going back |
This check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
|
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
|
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
At run time, 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.
Options for Decision Tables:
Field |
Description |
| Rule |
Select a decision table, 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 item history (the "audit trail") when a flow execution completes this shape. The Pega 7 Platform includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item 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 item history. See Controlling the volume of generated work item history instances and the PDN article 25196 How to control history instances written to the audit trail. |
| Entry point |
Select to indicate that this decision shape 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. Because a decision shape 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 shape that requires user input. |
| Only going back |
This check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
At run time, the system evaluates the decision table 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.
Options for Decision Trees:
Field |
Description |
| Rule |
Select a decision tree, 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 item history (the "audit trail") when a flow execution completes this shape. The Pega 7 Platform includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item 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 item history. See Controlling the volume of generated work item history instances and the PDN article 25196 How to control history instances written to the audit trail. |
| Entry point |
Select to indicate that this decision shape 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. |
| Only going back |
This check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
At run time, the system evaluates the decision tree 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.
Options for Forks:
Field |
Description |
| Entry point |
Select to indicate that this decision 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. This check box works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the check box has no effect. Because a decision fork 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 check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
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.
On the connector for a fork shape, you can select Condition Type of Percentage. Instead of the Likelihood field on the property panel, a Percentage field appears. Enter a numerical value that corresponds to the approximate percentage of work objects that should take this path. Do not confuse Percentage with Likelihood.
Options for Map Values:
Field |
Description |
| Rule |
Select a map value, 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 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 item history (the "audit trail") when a flow execution completes this shape. The Pega 7 Platform includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item 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 item history. See Controlling the volume of generated work item history instances and the PDN article How to control history instances written to the audit trail. |
| Entry point |
Select to indicate that this decision shape 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. This check box works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the check box has no effect. |
| Only going back |
This check box appears only when you select the Entry Point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only Going Back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry Point check box. Select to run flow action post-processing when you click away from this entry point. |
At run time, the system evaluates the map value 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 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.
Options for Predictive Models:
Predictive model rules are available through the Decision Strategy Manager.
Field |
Description |
| Rule |
Select a predictive model rule. |
| Entry point |
Select to indicate that this decision 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. This check box works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the check box has no effect. |
| Only going back |
This check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
Options for Scorecards:
Scorecard rules are available through the Decision Strategy Manager.
Field |
Description |
| Rule |
Select a scorecard model rule. |
| Entry point |
Select to indicate that this decision 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. This check box works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the check box has no effect. |
| Only going back |
This check box appears only when you select the Entry point check box. 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. Decision shapes are not typically marked as entry points. However, if you do mark this shape as an entry point, as a best practice, also select the Only going back check box to prevent users from jumping ahead to this decision shape before prerequisite steps are executed. |
| Post action on click away |
This check box appears only when you select the Entry point check box. Select to run flow action post-processing when you click away from this entry point. |
Click Submit to close the property panel.
Hover on an existing shape in the flow and drag a connector from it to the Decision shape.
Hover on the Decision shape and drag a connector to an existing shape in the flow.
Repeat step 6 for each value that is returned by the Decision shape.