Live Data Views - Nextedy Documentation

A view in Risksheet is a saved column visibility preset. It does not store its own copy of data and it does not change the underlying work items. All rows in the grid remain bound to the same Polarion work items at all times — the view only changes which columns are visible. Switching from one view to another is therefore a zero-cost UI operation that filters the grid down to the columns a given role needs to see during a given stage of the analysis. This page explains how the five typical stages of a risk assessment map onto views, how views are declared in the sheet configuration, and which configuration properties drive the behavior.

Stages of a Staged Risk Assessment

A typical FMEA, HARA, or TARA proceeds through five stages. Each stage has a distinct intent and a distinct set of columns. The diagram below shows the progression.

Stage 1 — Context and Risk Identification

The analyst captures the system context and lists the failure modes, hazards, or threats. Visible columns are the upstream context (function, item, system reference) and the initial description fields (failure mode, hazard, threat scenario). Classification and mitigation columns are hidden so the analyst is not tempted to fill them in before the identification work is complete.

Stage 2 — Risk Classification

The risk team rates each identified risk. Visible columns are the classification parameters such as severity, occurrence, detection, ASIL, or CVSS metric vectors. Mitigation and residual columns remain hidden. This view is typically used in a workshop where multiple stakeholders agree on the initial ratings.

Stage 3 — Mitigation Planning

Mitigation owners propose actions. The view exposes the task (downstream) columns — the linked mitigation item, owner, target date, and status — alongside the classification result so the planner can prioritize. Residual-risk fields are still hidden.

Stage 4 — Residual Risk Assessment

After mitigations are agreed, analysts rate the residual risk. The view shows the residual severity, residual occurrence, residual detection, and the calculated residual RPN or risk index. The initial classification columns may also be visible side-by-side so the change is visible at a glance.

Stage 5 — Final Review

The reviewer needs the complete picture. This view exposes every column, typically using the @all shorthand, so nothing is hidden during sign-off.

How Views Are Configured

Views are declared in the views section of the sheet configuration. Each entry has a name and a list of columnIds to include. One view can be marked as the default with defaultView: true so it loads automatically when the sheet opens.

views:
  - name: 1. Context & Risk Identification
    columnIds:
      - function
      - item
      - failureMode
      - hazard
  - name: 2. Risk Classification
    columnIds:
      - failureMode
      - severity
      - occurrence
      - detection
      - initialRpn
  - name: 3. Mitigation Planning
    columnIds:
      - failureMode
      - initialRpn
      - task
      - owner
      - dueDate
      - status
  - name: 4. Residual Risk Assessment
    columnIds:
      - failureMode
      - initialRpn
      - resSeverity
      - resOccurrence
      - resDetection
      - residualRpn
  - name: 5. Final Review
    defaultView: true
    columnIds:
      - "@all"

Two special tokens are available inside columnIds:

Token	Effect
`"@all"`	Includes every column defined in the configuration.
`"-columnId"`	Excludes a single column from the set (typically combined with `@all`).

A “show everything except the downstream task block” view can therefore be expressed concisely:

- name: Risks Only
  columnIds:
    - "@all"
    - "-task"
    - "-owner"
    - "-dueDate"
    - "-status"

Naming views with a leading number (“1. Context…”, “2. Classification…”) makes the intended order visible in the view switcher and turns the dropdown itself into a lightweight workflow guide.

The views[].columnIds array names the columns to show. Earlier drafts of community documentation used columns, but the engine only honors columnIds. Using the wrong name produces an empty view (no columns rendered).

Views Versus Filters

Views are about which columns are visible. They do not filter rows. Row-level scoping is handled by other mechanisms:

Mechanism	Scope	Configured in
`views`	Hides/shows columns	Sheet configuration
`queryFactories`	Filters autocomplete options inside link columns	Sheet configuration
`dataTypes.task.document`	Restricts downstream tasks to a specific document	Sheet configuration
URL parameters (`sort`, `filter`, `collapsed`)	Per-session row filtering and sorting	URL query string

The same sheet can therefore be opened multiple times with the same view but different URL filters — for example, one tab showing only the highest-severity rows for a triage meeting, another tab showing all rows for a complete review.

The exact column IDs to put inside each columnIds list depend on your specific sheet configuration. Open the configuration editor and copy the id value of each column you want to expose; the IDs are case-sensitive.

What Users See

When views are configured, the grid toolbar shows a view switcher. Selecting a view immediately re-renders the grid with the new column set — no work items are reloaded, no data is lost, and any unsaved edits remain in place. Switching back exposes the previously hidden columns again. You should now see five entries in the view switcher of the configured sheet, the “5. Final Review” view selected by default, and only the columns appropriate to the current stage visible after picking any other entry.

​Stages of a Staged Risk Assessment

​Stage 1 — Context and Risk Identification

​Stage 2 — Risk Classification

​Stage 3 — Mitigation Planning

​Stage 4 — Residual Risk Assessment

​Stage 5 — Final Review

​How Views Are Configured

​Views Versus Filters

​What Users See

​See also

Stages of a Staged Risk Assessment

Stage 1 — Context and Risk Identification

Stage 2 — Risk Classification

Stage 3 — Mitigation Planning

Stage 4 — Residual Risk Assessment

Stage 5 — Final Review

How Views Are Configured

Views Versus Filters

What Users See

See also