Skip to main content

​
Prerequisites

  • Two or more Risksheet documents configured in your Polarion project
  • Upstream or downstream columns linking work items between the documents
  • The target document must have a valid risksheet.json configuration attached

​
How Nested Navigation Works

When your Risksheet contains columns that reference work items stored in a different Risksheet document, you can open that target document directly from the grid. This is particularly useful for multi-level risk analysis structures such as:
  • A system-level HARA linking down to component-level FMEAs
  • A top-level risk register linking to detailed failure mode analyses
  • A cybersecurity TARA linking to STRIDE threat sheets per component
diagram

​
Step 1: Configure the Upstream or Downstream Column

Ensure the column that links to items in another document is properly configured. The linked items must reside in a document that has its own Risksheet configuration. For an upstream column linking to items in another document, your risksheet.json should include a column definition with isItemLink or a multiItemLink type: 
{
  "columns": [
    {
      "binding": "systemRequirement",
      "header": "System Requirement",
      "type": "itemLink",
      "isItemLink": true,
      "level": 1
    }
  ]
}
For downstream task columns that reference items in a separate document: 
{
  "dataTypes": {
    "task": {
      "type": "MitigationAction",
      "role": "mitigates"
    }
  }
}

​
Step 2: Open a Linked Item via Context Menu

  1. Right-click on a cell that contains a linked work item reference
  2. From the context menu, select Open Linked Item (for upstream items) or the task type name (for downstream items)
  3. The linked work item opens in the Polarion item editor
The context menu label for linked items is derived from the level definition or the column header. For task items, the menu label uses the name configured in dataTypes.task.name if set, otherwise it defaults to “Task”.
When the linked work item resides in a document that has a Risksheet configuration, you can navigate from the Polarion item editor to that document’s Risksheet view. Open the work item, then use the document navigation to open the containing LiveDoc in Risksheet mode.

​
Step 3: Configure the createInCurrentDocument Parameter

When users create new upstream items directly from the Risksheet grid, the createInCurrentDocument parameter controls whether new items are stored in the current document or created externally. To store new items in the current Risksheet document: 
{
  "dataTypes": {
    "risk": {
      "type": "RiskRecord",
      "createInCurrentDocument": true
    }
  }
}
If createInCurrentDocument is not configured, new upstream items may be created outside the current document. This means navigating to them will not open a nested Risksheet view but instead the standard Polarion work item editor. Plan your document structure carefully to ensure linked items land in the correct documents.

​
Step 4: Load Upstream Items from Another Project or Document

To load upstream items from a specific document in another project, configure the typeProperties for the upstream work item type. Risksheet can load existing upstream items from other projects and documents via the typeProperties configuration, but the sheet itself always starts empty — items must be linked to Risk Records (or your configured main work item type) to appear. 
{
  "dataTypes": {
    "risk": {
      "type": "RiskRecord",
      "role": "addresses"
    }
  },
  "columns": [
    {
      "binding": "systemFunction",
      "header": "Function",
      "type": "itemLink",
      "isItemLink": true,
      "level": 1
    }
  ]
}
The upstream items are loaded based on the link role and type configuration. When these items reside in a document with its own Risksheet configuration, you can navigate to that nested Risksheet to view the full context.
You can have multiple different Risksheet configurations within one project. Each document can have its own risksheet.json with different column layouts, data types, and styling. This enables specialized views for HARA, FMEA, and other analysis types that cross-reference each other through nested navigation.

​
Step 5: Navigate Between Nested Risksheets Using LiveDoc Embedding

If you have embedded a Risksheet widget in a LiveDoc page, you can configure navigation between nested sheets using URL parameters:
ParameterDescription
documentTarget document path in the project
projectTarget project ID (for cross-project navigation)
revisionSpecific revision to view (optional)
See Embed Risksheet in LiveDoc for details on widget embedding.
Risksheet requires Risk Records (or configured main work item types) as the starting point. The grid starts empty, and items must be created or linked manually. You cannot auto-populate a Risksheet with all existing items from another document. Items must be associated through work item links to appear on the sheet. If you need to pre-populate a Functional Hazard Assessment (FHA) with existing Function items, you must first create Risk Records and then link the existing items as upstream references.

​
Context Menu Options Reference

The following context menu actions are available for navigating to linked items:
Menu ActionWhen AvailableBehavior
Open Row ItemAlwaysOpens the current row’s work item in Polarion
Open Linked ItemCell contains a valid item linkOpens the upstream linked item in Polarion
Open [Task Type]Cell contains a task linkOpens the downstream task item in Polarion
Freeze PaneAlwaysFreezes columns left of current position
The Open Linked Item option only appears when the cell contains a valid item link (the item ID must not start with *, which indicates an unsaved item). Unsaved items must be saved before they can be opened in Polarion.

​
Verification

You should now see:
  • ✅ Linked items in upstream/downstream columns display work item IDs from the target document
  • ✅ Right-clicking a cell with a linked item shows Open Linked Item or the task type name in the context menu
  • ✅ Clicking the menu option opens the work item in the Polarion editor, from where you can navigate to the nested Risksheet
  • ✅ New items created via the Risksheet grid are stored according to the createInCurrentDocument setting

​
See Also

KB ArticlesSupport TicketsSource Code
  • risksheet.json
  • RisksheetProjectProperties.java
  • AppConfig.ts
  • OpenHelpCommand.ts
  • RisksheetProduct.java