|
|
Flow formThe run strategy shape 
uses the configuration in an interaction rule's Run Strategy tab to execute the strategy.
The Run Strategy shape is available only to developers who have access to the Decision Strategy Manager RuleSets Pega-DecisionArchitect and Pega-DecisionEngine RuleSets. For more information about configuring and running strategies, see the PDN article About the Decision Strategy Manager.
Use the canvas context menu:
- Right-click a blank area of the canvas where you would like the End shape to appear.
- Hover over Add on the submenu to display a list of shapes you can add to the flow.
- Click the Run Strategy shape. After the shape has been added to the canvas, click and drag to reposition.
Use the toolbar Flow Shape palette:
- Click the Flow Shape palette
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. - Click and drag the Run Strategy shape to the canvas.
- Close the Flow Shape palette at any time.
Use the toolbar Flow Shape palette down-arrow:
- Click the down arrow
at the right end of the toolbar Flow Shape palette to display a drop-down shapes menu. - Click and drag the Run Strategy shape from the drop-down menu to the desired position on the canvas.
Editing Run Strategy properties
On the flow Diagram tab, open the properties panel using one of the following:
- Double-click the shape.
- Right-click the shape and select Properties from the drop-down menu.
- Click the shape, then click the toolbar View Properties icon
.
2. When the Run Strategy Properties panel appears, enter a text name for this shape. The shape name defaults to Run Strategy. Choose a name meaningful to application users who see this on the work item history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. For example: CustomerOpen-To-Buy.
The shape name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Run Strategy shape on the Diagram tab.
To change the name after you have exited from the properties panel, click the name, and type over the highlighted text.
3. Complete the fields as described in the table below. (To edit the shape properties after you save the Flow form, open the Diagram tab, right-click the shape, and select Properties.)
4. Click OK or click anywhere off the shape to save edits and close the panel.
5. Connect at least one incoming connector to the shape.
6. Connect at least one outgoing connector from the shape to another shape.
Deleting a Run Strategy shape from the flow
A Run Strategy shape may be deleted from the process flow. Right-click the shape, and select Delete from the drop-down menu.
You can also select the End shape and do one of the following:
- Click Delete
on the toolbar. - Press the Delete key on your keyboard.
When a shape is deleted, the connectors to and from the shape are also deleted.
Complete the Utility tab as described in the table below.
Field |
Description |
| Interaction |
|
| Application |
|
| Work Type |
|
| Use Case |
|
| Audit Note |
|
| Entry Point |
Select to indicate that this 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. Because a utility 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 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.
|
| 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. |
Select the Interaction rule containing the run strategy configuration.
For maximum user flexibility, clear this checkbox if your flow accepts inputs in any order.
If the activity uses the TaskStatus-Set method to one of a few possible activity outcomes, the outgoing connectors can depend on this Status value. For example, a utility activity might return the values "HIRE", "REJECT", and "WAIT" through a TaskStatus-Set method. Using three connectors from the utility, one for each status value, simplifies the flow diagram by eliminating a fork or decision shape.
Optional. Add a Ticket Name field under the Tickets tab 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 end shape to indicate one or more tickets are associated with this end shape.
Field |
Description |
| Ticket Name |
|
| Display Name | Optional. The Ticket Name appears by default. Enter a name to display other than the ticket name. |
Optional. Select one or more tickets that are to be available at runtime for this End shape. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.