Skip to main content

​
Overview

Saved views are managed in the RISKSHEET configuration and define which columns are visible when a view is selected. Unlike the ‘Select Visible Columns’ feature (which allows individual users to control visibility in real-time), saved views are predefined by administrators and provide preset configurations for common tasks.
Saved Views (admin-configured, reusable presets) differ from Column Visibility Preferences (user-controlled, per-session toggles). Use saved views for standardized team workflows; use column visibility for temporary personal adjustments.

​
Configuration Structure

​
Views Property

PropertyTypeRequiredDescription
namestringYesDisplay name shown in the saved views selector dropdown
columnIdsarrayYesArray of column IDs that should be visible in this view
defaultViewbooleanNoIf true, this view loads automatically when opening the Risksheet (default: false)

​
Column ID Syntax

The columnIds array supports two syntaxes: Inclusive: List specific column IDs to show 
"columnIds": ["item", "failureMode", "severity", "occurrence"]
Exclusive: Use @all to show all columns, then prefix column IDs with - to hide them 
"columnIds": ["@all", "-task", "-taskTitle", "-taskStatus"]

​
Configuration Example

{
  "views": [
    {
      "name": "Potential Failures",
      "columnIds": ["item", "failureMode", "effect", "severity"]
    },
    {
      "name": "Mitigation Tasks",
      "columnIds": ["item", "task", "taskTitle", "taskStatus", "taskAssignee"]
    },
    {
      "name": "Risk Assessment",
      "columnIds": ["item", "failureMode", "severity", "occurrence", "detection", "rpn"],
      "defaultView": true
    },
    {
      "name": "All Data (Except Drafts)",
      "columnIds": ["@all", "-draftFlag", "-draftNotes"]
    }
  ]
}

​
Saved Views Selection Diagram

​
Use Cases

​
Use Case 1: Failure Mode View

For FMEA analysis teams reviewing potential failures: 
{
  "name": "Potential Failures",
  "columnIds": ["item", "failureMode", "effect", "impact"]
}
Users see only the columns needed to understand what can fail and the consequences.

​
Use Case 2: Mitigation Planning

For teams assigning and tracking mitigation tasks: 
{
  "name": "Mitigation Planning",
  "columnIds": [
    "item",
    "failureMode",
    "task",
    "taskTitle",
    "taskAssignee",
    "taskDueDate",
    "taskStatus"
  ]
}

​
Use Case 3: Risk Review

For stakeholder review with executive summary metrics: 
{
  "name": "Risk Review Summary",
  "columnIds": [
    "item",
    "failureMode",
    "severity",
    "occurrence",
    "detection",
    "rpn",
    "reviewStatus"
  ],
  "defaultView": true
}

​
Setting Default View

​
Configuration Method

Add "defaultView": true to the view definition in the configuration: 
{
  "name": "Risk Assessment",
  "columnIds": ["item", "severity", "rpn"],
  "defaultView": true
}

​
Script Method

Set the default view dynamically in risksheetTopPanel.vm using Velocity Template Language: 
<script>
risksheet.appConfig.views[0].defaultView = true;
</script>

​
Conditional Default View

Use Polarion APIs to set default views based on user role: 
<script>
#foreach($r in $securityService.getRolesForUser($securityService.getCurrentUser()))
  #if($r.equals("admin"))
    risksheet.appConfig.views[1].defaultView = true;
  #elseif($r.equals("reviewer"))
    risksheet.appConfig.views[2].defaultView = true;
  #end
#end
</script>

​
User Interaction

​
Selecting a Saved View

  1. Click the View Selector dropdown in the RISKSHEET toolbar (appears by default when views are configured)
  2. Select a view name from the list
  3. The RISKSHEET immediately displays only the columns specified for that view
  4. Selected view choice persists during the current session

​
Switching Between Views

Users can switch between views multiple times without saving:
  • Click the view selector dropdown
  • Choose a different view
  • Current row selection and scroll position may reset depending on column changes

​
Column Visibility vs. Saved Views

FeatureSaved ViewsSelect Visible Columns
Defined byAdministratorIndividual user
PersistenceReusable across sessionsPer-session only
Preset configsYes (multiple predefined)No (manual each time)
Edit capabilityRequires config editYes, real-time toggle
Use forStandard workflowsTemporary adjustments

​
Version Support

FeatureIntroducedNotes
Saved views (basic)23.0name and columnIds properties
Default view24.1.0defaultView property and script methods
Exclusive syntax (@all, -columnId)23.0Supported from initial release
Dynamic view selection (scripts)24.1.0Set default views based on user context

​
Configuration Best Practices

Use descriptive, task-oriented names like “Failure Analysis”, “Risk Assessment”, “Mitigation Tasks” rather than generic names like “View 1” or “View 2”.
Column IDs in saved views must exactly match configured column IDs. Misspelled IDs are silently ignored and the column will not appear in the view.
When switching views, the RISKSHEET may trigger a refresh depending on the refreshOnSave configuration property. Unsaved changes may be lost if the refresh occurs before saving.

​
Limitations

  • Personal views not supported: Each user cannot create their own saved views. Only administrators can define saved views in the configuration.
  • No sorting/filtering persistence: Saved views control column visibility only; they do not save sort order, filters, or row selections.
  • One default view: Only one view can be marked as the default view; if multiple views have defaultView: true, the first one wins.
  • Column-level only: Saved views cannot hide individual data types or rows; they control which columns are visible in all rows.
KB ArticlesSupport TicketsSource Code
  • CommandFactory.ts
  • AppConfig.ts