Flow form
|
A flow rule that presents a single user with a sequence of forms to complete is known as a screen flow. This restricted category of flow rules provides an effective way to simplify input processing and present questions or input fields in a series of forms. Users can change an answer to an earlier question by backing up in the flow, and in some situations, can complete steps in any order.
To support this style of interaction, a screen flow rule must meet several restrictions. The flow diagram can contain only these shapes:
Assignment | Fork | ||
Call Subflow | SplitForEach | ||
Connector | Start | ||
Decision | Utility | ||
FlowEnd |
Because many business processes do not meet these restrictions, you can create a subflow for screen flow interactions and call the subflow from an unrestricted starter flow.
Follow these steps to create a screen flow:
ScreenFlowStandard
,
ScreenFlowBPMN
, or
ScreenFlowTabbed
as the
Template value. Click Create
to create the flow rule.Completing the Start shape panel
Complete these fields in the Start Properties panel.
Completing the Assignment shape panel
Each assignment has only one connector flow action. Complete these Assignment Properties panel for each assignment:
Field |
Description |
Name |
Enter the name of the assignment as it appears on the Visio diagram and on the rectangle or tab at runtime. |
Instructions |
Select a field value rule for the worklist display that
describes the task that users perform to complete the
assignment. . Click the pencil icon ( ) to review the field value rule or define a new field value rule. The SmartPrompt lists field value rules with an Applies To key part equal to the work type of the flow rule (or a parent class) and a Field Name key part of 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. See About the Localization wizard. |
Flow Action |
Identify one connector flow action. |
Entry Point |
Select to create an entry point for the assignment and allow user processing at runtime to begin or resume at this point in the flow. When selected, if this screen flow presents steps as tabs, at runtime a tab appears with the Name value as a label. Leave cleared to indicate that users cannot return directly to this assignment; users may be able in some cases to reach it indirectly from an earlier assignment. |
Only going back? |
This check box appears only when you select the Entry Point? check box. Select to restrict users who at runtime are at this entry point to only entry points (on the breadcrumbs or tab display) for earlier steps in the flow. Clear to allow users to select any entry point of the flow from this entry point. Users can click the breadcrumbs control or a tab to visit an earlier or later step. For maximum user flexibility, leave this check box cleared 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? |
Select to cause Process Commander to execute the Validate Rule rule and the After This Action... Run Activity activity (both on the Action tab of the Flow Action form) when a user at runtime clicks a screen flow tab or screen flow tree node to leave this assignment and start (or return to) a different assignment. The post-processing activity can compute additional property values and perform other processing. If the option is not selected, the validate rule does not execute and the post-processing activity does not execute when the user clicks to leave the assignment. As a best practice, check this option if the action has a non-blank Validate Rule or non-blank After This Action... Run Activity activity. |
A screen flow rule can call or branch to another flow rule, but only if the other flow rule is also a screen flow rule and uses the same harness rule.
Decision shapes and fork shapes
Page Group
properties are processed
unordered and all pages are shown.
How to start execution of a screen flow
Call or branch to a screen flow rule from another flow rule that is not a screen flow, using the Call Subflow shape () to start execution.
Buttons for Back, Next, Submit, and Cancel
At runtime, each assignment task in a screen flow rule presents a button labeled Next>> . When users click this button, processing validates user input and advances to the next assignment. (The label on the Next>> button changes automatically to Submit when this assignment is the last one in a flow.)
A <<Back button appears automatically when a user has completed any task that is an entry point.
Optionally, assignments can also include a Cancel button. To include a Cancel button:
bAddCancel
. Select Boolean
as the
Data Type.bAddCancel
parameter check
box to cause a Cancel button to appear.bAddCancel
parameter check
box to remove the Cancel button.Withdraw
at an
appropriate place in the calling flow rule. When a user
clicks the Cancel
button during execution of the screen flow, a ticket named
Withdraw
is activated. Processing typically
continues at that ticket task in the calling flow
execution. The standard flow rule PegaSample-CustomerRequest.CustomerFeedback is a screen flow rule. This subflow is called by the NewWork starter flow when all members of the cover are resolved.
The standard flow rule PegaAccel-Task-Harvest.GatherRuleInfo is a tabbed screen flow rule that supports user cancellation. This subflow is called by the PegaAccel-Task-Harvest.HarvestRule flow rule, which supports the rule harvest facility.
Four standard rules support execution of screen flows:
screen flow, subflow | |
Flow rules —
Editing the Call or Branch to Subflow shape properties
Flow rules — Editing the Decision task shape properties Flow rules — Editing in Visio — Fork tasks Flow rules — Editing the Split-ForEach shape properties |