Back Forward Navigation rule — Completing the Node Details Action tab

About Navigation rules

On the Action tab, specify the action to be performed when the node is selected at run-time; for example, when a user clicks a menu item. This tab displays when Item, Item List or Selected Item are selected in the Type list on the Node Details dialog.

Click the plus sign to specify an action associated with the node. This opens the Behavior dialog, which contains a column for the Event, Action, and a diamond-shaped condition icon (). Conditions do not apply to actions; they apply to the entire node.

To define the node's behavior, click the add row icon . Your choices populate the grid row. After you have completed the dialog, click OK to apply your edits and close the dialog.

If you define more than one click event for a node, the actions are executed from the top down as displayed in the list; the inherited actions (the ones in the rule) execute first. All processing effects of an action in the list will complete before the next action starts. For example, assume a Display > Set Value action is followed by a Launch > Local Action. When the user clicks the button, the Set Value action also triggers a Post Value action (set in a the Behavior field on a Cell Properties panel) and recalculation of an expression. After all processing is completed, the system starts Local Action.

Action Category Mobile Action Name
Process Work

Show Flow Location

Add New Work (from New or Create harness)
Finish Assignment (from Perform harness)
Cancel
Save

Get Work

Create Work

Open Assignment

Open Work by Handle

Display

Refresh section

Launch

Harness- Target value of Pop-up Window or New Document is supported.

Local Action - Target value of Modal Dialog or Overlay are supported. Using Page is supported.

Advanced

Run Activity

Run Data Transform

Run Script

If the navigation rule is Type Mobile, a subset of the actions is available. Actions that appear for a Mobile application are summarized in this table and indicated in the sections below.

Mobile applications support one action per node. Only the first action is executed. Any additional defined actions are ignored.

Certain actions (such as Create Work, Open Assignment, Launch Harness, and Run Script) that display user interface features do not run on a phone device when specified on a node with children. These actions require that the main navigation and content panels appear simultaneously which is not possible on a phone. Therefore, as a best practice, implement these actions on child nodes. If placed on a parent node, they should be optional actions, not critical to work item processing.

Run Activity and Run Data Transform can be run on a node that has children.

Process Work

Get Work

Handle List Items

Use these actions only when acting upon repeating layouts.

Display

Launch

Advanced

Up About Navigation rules