> ## Documentation Index > Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt > Use this file to discover all available pages before exploring further. # Open Nested Risksheets > Navigate from a cell on one Nextedy RISKSHEET document directly into another risksheet that contains the linked work item, enabling drill-down workflows across hierarchically related risk analyses. export const LastReviewed = ({date}) => { if (!date) return null; const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", { year: "numeric", month: "long", day: "numeric", timeZone: "UTC" }); return

Last reviewed on {formatted}

; }; ## Prerequisites * Two or more risksheet documents configured in your Siemens Polarion ALM project * Upstream or downstream link columns connecting work items between the documents * The target document must have its own sheet configuration attached ## How Nested Navigation Works When a risksheet contains columns that reference work items stored in another risksheet document, you can open that target document directly from the grid. All linked data lives in Polarion work items — Risksheet does not maintain a separate data store, so navigation always resolves to actual Polarion items, subject to Polarion authorization and audit. Nested navigation is useful for multi-level analyses across any methodology — Failure Mode and Effects Analysis (FMEA), Hazard Analysis and Risk Assessment (HARA), Threat Analysis and Risk Assessment (TARA), STRIDE, or generic traceability matrices: * 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 * A requirements matrix linking to test case sheets diagram Ensure the column that links to items in another document is properly configured in the sheet configuration. The linked items must reside in a document that has its own sheet configuration. For an upstream column that loads items from another document, declare an `itemLink` (or `multiItemLink`) column and provide `typeProperties` to scope the lookup. The full set of `typeProperties` sub-properties is: | Sub-property | Type | Purpose | | --------------- | ------- | ---------------------------------------------------------------------- | | `linkRole` | string | Polarion link role connecting the row item to the linked item | | `linkTypes` | string | Comma-separated list of allowed work item type IDs | | `linkDirection` | string | Set to `back` to traverse the link in reverse | | `backLink` | boolean | Render the column as a back-link (read-only view of incoming links) | | `itemTemplate` | string | Velocity template for customizing how each item is rendered | | `queryFactory` | string | Name of a `queryFactories` entry that filters autocomplete suggestions | Two further sub-properties scope the lookup to other documents or projects when you need to point a column at a shared upstream library: | Sub-property | Type | Purpose | | ------------ | ------ | ---------------------------------------------------------------------------------------------- | | `document` | string | Restrict autocomplete to items in a specific LiveDoc (for example a harms or function library) | | `project` | string | Space-separated list of project IDs; `$projectId` resolves to the current project | Example column definition in the sheet configuration: ```yaml theme={null} columns: - id: systemRequirement bindings: systemRequirement header: System Requirement type: itemLink level: 1 typeProperties: linkRole: refines linkTypes: requirement,systemRequirement linkDirection: back itemTemplate: $item.id - $item.title ``` For downstream task columns that reference items in a separate document, configure `dataTypes.task`: ```yaml theme={null} dataTypes: task: type: mitigationAction role: mitigates document: Risks/Mitigations ``` 1. Right-click a cell that contains a linked work item reference. 2. From the context menu, select **Open \[Column] Item** (the label embeds the column name, e.g. **Open Item/Func 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 is derived from the level definition or the column header. For task items, the label uses `dataTypes.task.name` if set, otherwise it defaults to **Task**. When the linked work item resides in a document that has its own sheet configuration, you can open the work item from the editor and then open the containing LiveDoc directly in Risksheet view. For master-detail architectures, configure the downstream task type so the task ID column becomes a clickable hyperlink that opens the child risksheet: ```yaml theme={null} dataTypes: task: type: risk role: relates_to linkToRisksheet: true document: Risks/Detailed_Risk_Analysis ``` With `linkToRisksheet: true`, clicking the task ID in the parent grid navigates straight to the child risksheet document defined by `dataTypes.task.document`. This is the recommended pattern for hierarchical analyses — a master risksheet lists hazards, and each row links to a child risksheet with detailed mitigation analysis. When users create new items directly from the grid, `createInCurrentDocument` controls whether new items land in the current document or are created externally. To keep new items inside the current risksheet: ```yaml theme={null} dataTypes: risk: type: riskRecord createInCurrentDocument: true ``` For task creation in a specific target document (v24.8.1+): ```yaml theme={null} dataTypes: task: type: mitigationAction role: mitigates createInDocument: Risks/Mitigations ``` If `createInCurrentDocument` and `createInDocument` are not configured, new items may be created outside the intended document. Navigation will then open the standard Polarion work item editor instead of a child risksheet. Plan your document structure so linked items land in the expected sheets. To load upstream items from a shared library or another project, use the `typeProperties.document` and `typeProperties.project` sub-properties on the column. The grid still starts empty — items must be linked to the row work items (for example Risk Records) to appear. ```yaml theme={null} columns: - id: harm bindings: harm header: Harm type: itemLink level: 1 typeProperties: linkRole: addresses linkTypes: harm document: 02 - Risk Management File/Harms Library project: $projectId GlobalLibrary ``` In this example the autocomplete picks items from the Harms Library document, falling back to a shared project as well as the current one. A project can host many sheet configurations side by side. Each LiveDoc has its own sheet configuration with its own columns, data types, and styling — enabling specialised views for HARA, FMEA, TARA, and generic traceability matrices that cross-reference each other through nested navigation. If you embed a Risksheet widget in a LiveDoc page, you can drive navigation between nested sheets using URL parameters: | Parameter | Description | | ---------- | ------------------------------------------------ | | `document` | Target document path within the project | | `project` | Target project ID (for cross-project navigation) | | `revision` | Specific revision to view (optional) | See [Embed Risksheet in LiveDoc](/risksheet/guides/integration/livedoc-embedding) for widget configuration details. Risksheet requires risk items (row work items of the configured `dataTypes.risk.type`) as the starting point. The grid starts empty and items must be created or linked manually. There is no auto-population of items from another document. To pre-populate a Functional Hazard Assessment (FHA) with existing Function items, create the FHA risk items first and link the Functions as upstream references. ## Context Menu Options Reference The following context menu actions are available for navigating to linked items: | Menu Action | When Available | Behavior | | ----------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------- | | **Open Row Item** | Always | Opens the current row's work item in Polarion | | **Open \[Column] Item** | Cell contains a valid item link | Opens the upstream linked item in Polarion (the label embeds the column name, e.g. **Open Item/Func Item**) | | **Open \[Task Type]** | Cell contains a task link | Opens the downstream task item in Polarion | **Open \[Column] Item** (the label embeds the column name, e.g. **Open Item/Func Item**) 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 and downstream columns display work item IDs from the target document * ✅ Right-clicking a cell with a linked item shows **Open \[Column] Item** (the label embeds the column name, e.g. **Open Item/Func Item**) or the task type name in the context menu * ✅ Selecting the menu option opens the work item in the Polarion editor, from where you can navigate to the child risksheet * ✅ With `linkToRisksheet: true`, the task ID column is rendered as a hyperlink that opens the configured child document directly * ✅ New items created from the grid are stored according to `createInCurrentDocument` and `createInDocument` ## See Also * [Embed Risksheet in LiveDoc](/risksheet/guides/integration/livedoc-embedding) — configure widget embedding for nested views * [Navigate to Risksheet from LiveDoc](/risksheet/guides/integration/livedoc-navigation) — open Risksheet from LiveDoc links * [Configure Upstream Traceability Columns](/risksheet/guides/columns/upstream-traceability) — set up upstream item references * [Configure Downstream Traceability Columns](/risksheet/guides/columns/downstream-traceability) — set up downstream task references * [Configure Cross-Project Linking](/risksheet/guides/advanced/cross-project-linking) — link items across project boundaries * [Work with Branched Documents](/risksheet/guides/integration/branched-documents) — handle branched document references