Skip to Content
This documentation is provided with the HEAT environment and is relevant for this HEAT instance only.
RunnersDashboard UtilsDashboard Tools Runner

Dashboard Tools Runner

The Dashboard Tools Runner provides reusable node templates for filtering JSON and publishing dashboard dimensions. These nodes are broadly used across projects anywhere a parent node produces JSON that should become a dashboard dimension.

1. json-filter (Transform Node)

This node uses a JMESPath  expression to extract a specific subset of JSON from its input. Typical usage: isolate data related to the current session, user, or any scoped variable before passing it to downstream nodes. Full node documentation: json-filter node page.

2. dashboard (Aggregation Node) - Legacy V1

This node consumes JSON and publishes a legacy dashboard dimension (DashboardVersion="Legacy"). Full node documentation: dashboard node page.

3. dashboard-v2 (Aggregation Node) - Next V2

This node consumes JSON and publishes a Next dashboard dimension (DashboardVersion="Next"), with $heat-dataservice input validation. Full node documentation: dashboard-v2 node page.

4. lattice-processor (Processing Node)

This node inspects mixed upstream payloads and emits a single JSON summary of detected formats, metadata, and per-node/per-item analysis. Full node documentation: lattice-processor node page.

5. opendis-parser (Transform Node)

This node parses OpenDIS byte streams into structured JSON PDU objects for downstream processing. Full node documentation: opendis-parser node page.

6. filter-payload (Processing Node)

This node gates upstream binary payloads by allowed detected file types and forwards only matching payloads. Full node documentation: filter-payload node page.

7. session-trigger (Processing Node)

This node finds a related session and reprocesses a configured node to propagate updates across sessions. Full node documentation: session-trigger node page.

Integration in a Session Template

  1. Insert a json-filter node after ingestion or transformation.
  2. Set expression with session-scoped values (for example records[?userId=='$SESSION.userId']).
  3. Connect a dashboard or dashboard-v2 node to consume the filtered output.
  4. Provide dataSourceName, layoutConfiguration, and dashboardName.

This pipeline ensures the published dashboard dimension reflects only the relevant session data.

json-filter usage

For complete configuration, runtime behavior, failure modes, and examples, see the dedicated json-filter node page.

Tabular Remap NodeDashboard Node (Legacy V1)