Flow form
Process Modeler — Editing Decision shapes
Flow form
|
|
Use the Decision shape 
to reference a Boolean expression, decision table, decision tree, fork, map value, predictive model, or scorecard rule that, when evaluated, produces a value that is the basis of branching in the flow.
indicates that one or more tickets are defined on the Decision shape. Assigned ticket names appear beside this icon on the flow.
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.
On the flow Diagram tab or in Process Outline, you can add a shape in one of three ways. Validation of the added shapes occurs when you save the flow.
on the toolbar to display a drop-down shapes menu that will remain open until you close it, facilitating the process of rapidly adding multiple shapes. Click the window title bar and drag the submenu to another area of the screen, as needed.
on the toolbar Flow Shape palette to display a drop-down shapes menu.Double-click the shape.
Right-click the shape and select Properties from the drop-down menu.
Click the shape, then click the View Properties icon 
.
This name also appears inside the Decision shape on the diagram. To change the name after you have exited from the properties panel, click the name, and type over the highlighted text.A decision may be deleted from the process flow. Right-click the decision, and select Delete from the drop-down menu.
You can also select the decision and do one of the following:
icon on the toolbar.When a shape is deleted, the connectors remain on the canvas.
Cut or copy shapes from a flow and paste them within the same flow or in other flows within your user session.
to cut a selected shape(s) and connector(s). Cut differs from Delete in that cut shapes appear faded on the canvas until you paste them elsewhere. You can also cut selected shapes using the right-click canvas menu or the shape drop-down menu.
to place selected shape(s) and connector(s) in the copy buffer. You can also copy selected shapes using the right-click canvas menu or the shape drop-down menu.
to paste selected shape(s) and connector(s) elsewhere in the flow or in other flows within your user session. You can also paste selected shapes using the right-click canvas menu or the shape drop-down menu.Complete this section as follows:
Boolean Expression, Decision Table, Decision Tree, Fork, Map Value, Predictive Model or Scorecard Model.Use the following table to complete the Decision properties panel for Boolean expressions.
Field | Description |
| Type |
|
| 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. PRPC 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.)
|
| 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.
|
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 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.
Use the following table to complete the Decision properties panel for decision tables.
Field | Description |
| Type |
|
| 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. PRPC 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.)
|
| 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.
|
| 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 runtime, 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.
Use the following table to complete the Decision properties panel for decision trees.
Field | Description |
| Type |
|
| 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. PRPC 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.)
|
| 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.
|
| 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 runtime, 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.
Use the following table to complete the Decision properties panel for forks.
Field | Description |
| Type |
|
| 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.
|
| 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.
Use the following table to complete the Decision properties panel for map values. You can reference a one- or two-dimensional map value.
Field | Description |
| Type |
|
| Rule |
|
| Row input |
|
| Column input |
|
| Result in |
|
| Audit note |
|
| 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.
|
| 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 runtime, 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.
Use the following table to complete the Decision properties panel for predictive model rules. Predictive model rules are available through the Decision Strategy Manager .
Field | Description |
| Type |
|
| 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.
|
| 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. |
Use the following table to complete the Decision properties panel for scorecard rules. Scorecard rules are available through the Decision Strategy Manager.
Field | Description |
| Type |
|
| 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.
|
| 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. |
Field | Description |
| Specification | Enter a name to associate a specification with this shape. If you change the default shape name [Decision], the system enters the name in this field. You can either:
Enter a description in the text area beneath the specification name. When you click OK on the Properties dialog, the system creates or updates the specification. See Working with specifications in Process Modeler and Case Designer. |
Complete the Status and Tickets sections as described below.
Field | Description |
| Work status | Enter a work status in this field to set the status for the work item. This allows you to easily change the status at multiple points in the life cycle of a work item without adding a Utility shape to the flow for each status change. Similar to setting work item status using a Utility shape, setting the status invokes the UpdateStatus activity. Any defined tickets dependent on the status are raised, as appropriate. The selected status updates .pyStatusWork when the flow execution reaches this assignment shape. A status indicator appears on connectors to shapes that change a work item status. For example, if the shape status is set to Pending-External, the connector to that shape displays a small red flag. All transitions connecting to the shape will display the status indicator. Following are the status indicators for the four status prefixes.
|
Add a Ticket Name field to indicate the ticket(s) available at runtime. Use the Ticket to mark the starting point for exceptions that may arise at any point in the flow, such as a cancellation. The ticket is a label for a point in a flow, much like a programming "GOTO" destination.
An activity executing anywhere in your entire PRPC application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter. See Ticket help for other ways to raise a ticket.
The scope of a raised ticket includes all flows on the current work item that contain this ticket. If found, processing stops on that flow promptly, and resumes at the ticket point.
The system adds to the decision shape to indicate one or more tickets are associated with this decision. The assigned ticket name appears on the flow.
Field | Description |
| Ticket Name |
ExampleProcessing is connected to a ticket to respond to an exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:
|
| Display Name | The Ticket Name appears by default. Enter a name to display other than the ticket name. |
 | Flows — Concepts and terms Process Modeler basics |
About Flows
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 
Select a map value, identified by the second key part.
New
Open
Pending
Resolved
Select one or more tickets that are to be available at runtime from this decision. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.