Embed Risksheet in LiveDoc

​

Prerequisites

• A Risksheet document with a valid sheet configuration
• A target LiveDoc page where you want the entry point to appear
• Polarion editing permissions for the LiveDoc page

1

Open the Target LiveDoc Page

Navigate to the LiveDoc page where you want the entry point. Open it in edit mode and place the cursor where the hyperlink block should appear (typically at the top of a chapter or section that describes the risk analysis).

2

Insert the Velocity Hyperlink Block

Paste the following Velocity snippet into the page. It builds a deep link to the Risksheet view for the current document, including the document revision when one is in effect:

#set($revisionPar = "")
#if($document.getRevision())
  #set($revisionPar = "&revision=" + $document.getRevision())
#end
<a href="/risksheet/polarion/#/project/$document.getProjectId()/risksheet?document=$document.getRelativePath()$revisionPar"
   style="display:inline-block;padding:10px 16px;background:#fff4fb;border:2px solid #860251;border-radius:8px;text-decoration:none;color:#860251;font-weight:600;">
  Open Risksheet
</a>

This pattern is documented in the Nextedy Support Portal article Open Risksheet from LiveDoc (KB #48001199473). It uses standard Polarion Velocity context variables — $document.getProjectId(), $document.getRelativePath(), $document.getRevision() — so no additional setup is required.

3

Save and Verify

Save the LiveDoc page and switch to read mode. Click the Open Risksheet button — Polarion navigates to the interactive Risksheet view for the current document, with the full grid, all configured columns, levels, and styling.When a historical revision of the LiveDoc is open, the link automatically includes the &revision=... parameter, so the Risksheet view opens at the same revision.

4

Scope Linked Items to a Document

If the sheet configuration loads downstream tasks (for example, mitigations or safety requirements), restrict the task scope to a specific LiveDoc using the document property under dataTypes.task. Without it, every matching work item in the project becomes a candidate, which is rarely what you want in projects with many risk documents:

dataTypes:
  task:
    type: mitigationAction
    role: mitigates
    document: Risks/FMEA Analysis

The same pattern works for upstream item libraries through typeProperties.document on an itemLink column — for example, restricting an autocomplete to a shared harms library document.

Risksheet does not maintain a separate data store: every value you see is a Polarion work item, queried live. Scoping by document keeps suggestion lists relevant and avoids accidental cross-document linking.

​

Alternative: PDF for Static Distribution

1. Open the Risksheet view and use the Export to PDF function to produce a styled PDF of the grid, including cell decorators and headers.
2. Export the LiveDoc to PDF separately from Polarion.
3. Merge the two PDFs with an external tool.

​

Working with Templates

• Template approach: Attach the sheet configuration to a LiveDoc template. Documents created from that template inherit the configuration, and updates to the template propagate.
• Polarion Reuse: Nextedy does not recommend using Polarion’s Reuse function for risksheet documents — it duplicates the configuration attachment and complicates updates (KB #48001219133).

​

See Also

• Navigate to Risksheet from LiveDoc — variants of the deep-link pattern
• Export to PDF — produce a styled PDF for distribution
• Set Up Global Templates — template-based configuration management
• Override Template Configuration — per-document configuration overrides