Presenting flow actions — Comparing three approaches

Often, one connector flow action is more likely to be chosen than others. This is reflected in the relative likelihood values recorded on the flow diagram. You can present this most-likely flow action as the default while still allowing a user to select another. The user interaction sequence is:

1. The work object form appears (in Perform mode) with the connector flow action with the highest likelihood visible, including any associated input fields.
2. If the user's choice matches the default, the user enters data into the form (if any) and clicks  Submit   to complete the assignment.
3. If the user's choice is for a connector flow action other than the default, the user clicks a link with the appropriate label. The form changes to reflect the requirements of the selected flow action. The previous choice remains available as a link.

To implement this approach:

1. Create a Perform harness using the SmartFrames layout and JSP tags..
2. Include the standard section rule named Work-.Action_Step in the Perform harness rule.

As an example, the standard harness rule Work-.Perform_Step includes the Work-.Action_Step flow action. See also Pega Developer Network article PRKB-25450 How to present the default and alternate flow actions distinctly.

Available flow actions, filtered by user privileges, appear in a drop-down list. Connector flow actions appear at the top of the list in the selection box. Local flow actions appear at the bottom of the list.

The user interaction sequence is:

1. The user selects an action from the drop-down list.
2. The Take Action area of the form changes to reflect the inputs if any needed by the selected action.
3. The user enters data into the form.
4. The user clicks  Submit   (or another control) that submits the form.

To implement this approach, include the standard section rule Work-.Action in the harness rule named Perform in your application. The standard harness rule Work-.Perform may suit your requirements, or you can override it as needed. Your harness and section rules may use either SmartFrames layout with JSP tags or the legacy layout with either JSP tags or directives. SmartFrames with JSP tags is preferred for new development.

The connector flow actions available to a user can be presented as an array of labeled buttons, eliminating the drop-down list. A single editable text area, applying to all connector actions, appears above the buttons.

When this approach is implemented, the interaction sequence is:

1. The user completes a form by entering fields (if any) that apply to all connector flow actions.
2. The user records a choice of connector by clicking a button.
3. The Take Action area changes to present the input fields (if any) needed by the selected action. Users can click a link to return to this form.
4. The user enters data into the updated form.
5. The user clicks  Submit   (or a similar control) to submit the form.

When this approach is used, local actions listed on the assignment shape in the flow rule are not available. If a few local actions are needed, they can be defined as buttons or icons on the work object form. If many local actions are needed, this approach is less suitable.

To implement this approach:

1. Create a Perform harness using the SmartFrames layout and JSP tags. The standard harness rule Work-.Perform_Buttons may suit your requirements, or you can override it as needed.
2. For each connector flow action that requires no input fields, set the HTML Generation value (on the HTML tab) to No HTML.
3. Include the standard section rule named Work-.Action_Buttons in the Perform harness rule.
4. If desired, override the standard action section Work-.ActionContent if desired to collect input fields needed by all connector flow actions.
5. If local actions are needed, define each local action as an icon or button on the Harness rule form. By default, the button section includes a local action area that contains the Work-.Transfer local flow action. You can override the local action section.