Skip to main content
A risksheet normally opens in its own interactive view, but the risk table can also be rendered directly into the body of a Polarion LiveDoc. That is what you want when the analysis has to read as part of a document — a risk analysis report that carries its table alongside the surrounding narrative, in one Polarion document that can be reviewed, baselined, and exported as a single artifact. Risksheet supports any risk management methodology — Failure Mode and Effects Analysis (FMEA), Hazard Analysis and Risk Assessment (HARA), Threat Analysis and Risk Assessment (TARA), STRIDE, and CVSS — so this guide applies to any LiveDoc that presents or references a risksheet document.

​
Prerequisites

  • A Risksheet document with a valid sheet configuration
  • A target LiveDoc page where the risk table should appear
  • Polarion editing permissions for the LiveDoc page
1

Open the Target LiveDoc Page

Open the LiveDoc in edit mode and place the cursor where the risk table should appear — typically inside the chapter that describes the analysis.
2

Insert a Wiki Content Block

From the document toolbar’s insert menu, choose Wiki Content.
The Polarion LiveDoc insert menu with the Wiki Content entry highlighted
3

Enter the Renderer Call

Polarion opens the Wiki Content dialog. Enter this single Velocity call and confirm with OK:
The Polarion Wiki Content dialog containing the risksheetDocRenderer render call
$risksheetDocRenderer is the renderer Risksheet contributes to Polarion’s LiveDoc rendering context, and $document is Polarion’s standard reference to the document being rendered. The block therefore always renders the risk table of the document it sits in — there is nothing to parameterise, and no change to the sheet configuration.
4

Save and Verify

Save the LiveDoc. The risk table is rendered in place of the Wiki content block, with the sheet’s columns as table headers and one row per risk and task work item.
An FMEA risk table rendered inside a Polarion LiveDoc page
The block is evaluated each time the page is rendered, so the table reflects the document’s work items as they stand when a reader opens the page.

​
What the Inline Render Carries

The rendered table is built for reading, printing, and document export — it is not a second copy of the interactive grid:
The rendered table does not carry cell colouring. Conditional formatting — risk-priority colouring, ASIL highlighting, anything driven by cellDecorators and styles — is applied by the grid in the browser and is not reproduced in the LiveDoc table. When a fully styled, coloured table is the deliverable, use the PDF route below instead.
When the reader needs to work in the grid rather than read a snapshot, put a link in the LiveDoc that opens the Risksheet view for the same document — either instead of the rendered table or next to it. Navigate to Risksheet from LiveDoc covers that pattern, including how the link carries the document revision so a baselined document opens the matching read-only risksheet.
diagram

​
Alternative: PDF for Static Distribution

If you need a self-contained snapshot that keeps the grid’s full visual formatting — for an external auditor, a customer deliverable, or a controlled archive — export each artifact to PDF and combine them externally:
  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.
This is the route that preserves cell colouring and grid styling. The inline render is the route that keeps everything inside one Polarion document.

​
Working with Templates

Configuration changes scale best when they live on a LiveDoc template:
  • 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.
Start from a solution template. Do not assemble a sheet configuration from scratch. Pick the closest Nextedy solution template (functional safety, automotive HARA, medical risk file, cybersecurity TARA), then adapt its columns, levels, and formulas to your process.

​
See Also

Last modified on August 24, 2026