Skip to main content

Button Component

The Button component adds a clickable action to a report page. Buttons support navigation between pages, drill-through to detail views, external URL links, bookmark navigation, back navigation, and filter actions. They are primarily used in interactive web outputs; in PDF export, buttons render as styled visual elements but the action is not active.

Action types

Action typeDescription
Navigate pageJumps to another page in the same output when clicked.
Navigate bookmarkJumps to a named bookmark anchor on the same page or another page.
Navigate URLOpens an external URL in a new browser tab. Use for linking to source systems, documentation, or external dashboards.
Drill throughOpens a detail page filtered to the context of the current selection (e.g., clicking a discipline name on a summary page opens the discipline detail page filtered to that discipline).
BackReturns to the previously viewed page (browser-style back navigation).
FilterApplies or clears a filter on the current page when clicked (toggleable).

  1. Set Action type to Navigate page.
  2. Select the Target page from the dropdown of pages in the current output.
  3. Optionally pass parameter values to the target page: In Properties → Parameters, map the current page context to parameters the target page consumes.

Drill-through setup

Drill-through is the most powerful button action. It allows a summary page to act as a navigation hub into detail pages:

  1. Set Action type to Drill through.
  2. Select the Detail page (the destination page configured as a drill-through target).
  3. In Properties → Drill-through mapping, map each filter field: the field value from the current page (e.g., the selected discipline) maps to a parameter or filter on the detail page.
  4. On the detail page, ensure the target parameters or filters reference the passed values.

  1. Set Action type to Navigate URL.
  2. Enter the URL (must begin with https://).
  3. Enable or disable Open in new tab (default: enabled).

Dynamic URL segments can include field values: use {[FieldName]} syntax. For example: https://app.example.com/activities/{[ActivityID]}.


Filter action setup

PropertyDescription
Filter fieldThe field to filter when the button is clicked.
Filter valueThe value to apply. Can be a static value or bound to a field.
Toggle behaviorClick once to apply the filter; click again to clear it.
ScopePage (affects only the current page) or Report (affects all pages sharing the field).

Button style options

OptionDescription
Label textThe text shown on the button.
IconOptional icon from the icon library, shown before or after the label.
Button styleFilled, outlined, ghost (text only), or icon only.
Fill colorBackground color for filled style.
Border colorBorder color for outlined style.
Text colorLabel text color.
Font size and weightTypography of the label.
Corner radiusRounded corners (0 = sharp, 50% = pill shape).
PaddingInner spacing around the label.
SizeSmall, medium, large, or custom width/height.
Disabled stateStyle when the button is non-interactive (greyed out).
Hover stateColor change on hover (interactive mode only).

Icon support

Buttons can display an icon from the built-in icon library (1000+ icons from Material Design and project-specific sets):

  1. In Properties → Icon, click the icon picker.
  2. Search by name or browse by category.
  3. Set icon position: Left of label or Right of label or Icon only (no label).
  4. Set icon size independently of the label font size.

PDF export behavior

In PDF export, buttons render as styled visual elements (label and icon visible) with the appearance configured, but are not clickable. If a button's purpose is navigation, consider adding a tooltip or footnote explaining what the button links to in the interactive version.


Good practice

  • Use Back buttons on drill-through detail pages so users can return to the summary page without using the browser's back function.
  • Use Navigate URL buttons sparingly — external links should be stable and should not require authentication.
  • For filter toggle buttons, use a visual indicator (e.g., border change or fill toggle) so users know when the filter is active.
  • Group navigation buttons in a consistent location on each page (e.g., top-right or bottom-center).