Last updated:
Navigation flows
Navigation flows define how a dashboard’s incoming parameters are populated when it’s opened: either from the main menu or by navigating from another dashboard.
Navigation flows apply only to dashboards. Navigation to forms happens at runtime, but isn’t configurable through this module.
How it works
Section titled “How it works”Opening a dashboard from the main menu
Section titled “Opening a dashboard from the main menu”Each dashboard that can be opened from the main menu can be configured in Navigation flows. Selecting a dashboard shows two sections:
- Parameters: matches the incoming parameters configured on that dashboard (via the dashboard’s Incoming parameters setting).
- Actions: the navigation actions available from that dashboard.
Navigating between dashboards
Section titled “Navigating between dashboards”Navigation between dashboards is configured through Actions. An action can:
- Navigate to another dashboard.
- Navigate to the same dashboard, for example to apply new parameter values.
- Pass parameter values from the source dashboard to the target dashboard.
This covers scenarios such as opening a detail dashboard from a summary view, filtering a dashboard based on a selected record, or refreshing the current dashboard with a more specific context.
Parameters
Section titled “Parameters”For each incoming parameter you configure how its value is determined:
| Setting | Required | Description |
|---|---|---|
| Parameter | Yes | The incoming parameter defined on the target dashboard. |
| Description | No | A label explaining the purpose of the mapping, for the designer’s reference. |
| Value source type | Yes | Defines how the parameter value is determined. |
Value source types
Section titled “Value source types”- Static: a fixed value you enter manually.
- User: the signed-in username (same behavior as the User type in fixed filters).
- UserId: the signed-in user ID (same behavior as the UserId type in fixed filters).
- Variable: a selected application variable (same behavior as the Variable type in fixed filters).
- Control: the current value of a specific control on the source dashboard.
- Drillthrough: the unique row identifier from a grid-like control that triggered the navigation, for drillthrough scenarios where a user selects a row and navigates to a detail dashboard.
- Scanned tag: triggers a scan at runtime and uses the scanned result as the value. If scanning fails or is aborted, the dashboard doesn’t open.
Actions
Section titled “Actions”Actions can be attached to dashboard-level actions or to control-level actions within a dashboard, and define where navigation goes and which parameter values are passed along: using any of the value source types above (static, user context, variables, control values, drillthrough context, or scanned values).
Supported scenarios include dashboard-to-dashboard navigation, a dashboard navigating to itself, multiple dashboards navigating to the same target, and a single dashboard having multiple outgoing navigation actions.
Error handling
Section titled “Error handling”- Required parameter missing: no data is loaded, and the user sees a message that required parameters are missing.
- Undefined or unset values: resolved as an empty value.
- Scanned tag failure: the dashboard doesn’t open if scanning fails or is aborted.
Limitations
Section titled “Limitations”- Only dashboards are supported: navigation flow configuration doesn’t apply to forms.
- No conditional branching logic is supported within parameter assignment.
- No loop detection or recursion handling is enforced.