Skip to main content
This page documents both currently supported features and known limitations. Feature availability may change with new releases. Check your installed version’s release notes for the latest status.

​
Column and Data Entry

Dependent enums — where the available options in one dropdown column are filtered based on the selection in a parent column — are supported as a column-level feature in recent releases (v25.3.1+). They are configured directly on the dependent enum column (typically through a queryFactory or column-level dependency declaration), not as a top-level configuration section. The available options in the child column are filtered at runtime based on the value selected in the parent enum column.Note that severity, occurrence, and detection scales use integer IDs (for example, 1 through 10 for an FMEA severity scale), unlike regular Polarion enumerations which use string IDs. This distinction is important when configuring risk parameter columns: define the scale as a Polarion enumeration with integer IDs and bind a custom field on the work item type to it, then reference it from the column with type: rating:<enumId> and bindings: <fieldId>.
Cascading dropdown behaviour depends on the installed Risksheet version. Check your current release notes for the exact column-level syntax supported in your build.
No. Drag and drop is not supported for inserting existing work items into the Risksheet grid. To link existing Polarion work items, use the item link column editor which provides autocomplete-based search. Type at least 3 characters to trigger a search that matches work items by ID and type. The editor also prevents duplicate selections — if you attempt to link an item that is already present, you receive a notification.For multi-item link columns, the same autocomplete behavior applies, with additional support for selecting multiple items in a single cell.
No. Risksheet intentionally does not enforce Polarion mandatory fields during item creation. This is a deliberate design decision to simplify data entry — the assumption is that mandatory fields are enforced at later workflow statuses via Polarion’s built-in workflow validation rules, not at the point of initial data entry.To visually indicate which fields are required, use cellDecorators and styles in the sheet configuration to highlight mandatory column backgrounds with conditional formatting:
Use conditional formatting via cellDecorators to apply a colored background or left border to mandatory columns when they are empty. This gives users a visual cue about required data without blocking their data entry workflow. See Apply Conditional Formatting for detailed setup instructions.
No. The first “Item Id” column in the Risksheet grid cannot be renamed. This is a known limitation of the column configuration system. The systemItemId binding is a reserved system column that always displays as “Item Id” in the grid header.

​
Risk Analysis Workflows

Yes. Risksheet is a generic risk analysis tool and can be configured for Safety FMEA (SFMEA), Design FMEA (DFMEA), Process FMEA (PFMEA), and other FMEA variants. The column layout, risk parameters, and hierarchy levels are fully configurable through the sheet configuration. Each FMEA type uses the same underlying structure but with different column bindings, severity/occurrence/detection scales, and formula definitions appropriate to the analysis type.You can maintain multiple Risksheet configurations within a single Polarion project — each LiveDoc document can have its own sheet configuration with an independent column layout and risk parameter setup. Rather than starting from a blank configuration, pick the closest Nextedy solution template for your industry and methodology and modify it to match your process. See Configure FMEA Workflows for setup details.
Yes. Risksheet is methodology-agnostic and supports any risk analysis approach, including Failure Mode and Effects Analysis (FMEA), Hazard Analysis and Risk Assessment (HARA), Threat Analysis and Risk Assessment (TARA), STRIDE, and Common Vulnerability Scoring System (CVSS). Because Risksheet has no mandatory fields or hard-coded work item types, you can configure custom column layouts, threat categories, and severity scales that align with the STRIDE methodology (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege). Start from the closest solution template and adapt the columns and scales to STRIDE. See Implement STRIDE Analysis for configuration guidance.
Yes. Multiple Risksheet configurations per project are fully supported. Each Polarion LiveDoc document that contains a Risksheet has its own sheet configuration attached as a document attachment. This means you can have separate FMEA, HARA, and TARA analyses in the same project, each with completely independent column layouts, risk parameters, and styling.Additionally, you can use template-based configuration inheritance where a global template provides shared settings and each document overrides only the properties that differ. See Set Up Global Templates for details.

​
Document and Integration Scope

Yes. Risksheet is designed as a visual representation of a single Polarion LiveDoc document. It cannot aggregate or route work items from multiple documents based on naming patterns or other criteria. Each Risksheet instance corresponds to one document. All risk items are stored as standard Polarion work items belonging to that document — Risksheet visualises and edits Polarion data, it does not maintain a separate data store.However, you can create multiple Risksheet documents per project with independent configurations, and use cross-project linking to reference items across documents and projects. The createInCurrentDocument parameter controls whether newly created items are stored in the current document.
diagram
Collection awareness — filtering work items by collection membership and displaying correct revisions — is not currently available in Risksheet. This is a recognized feature request from enterprise customers who use Polarion collections for release management. The feature is under consideration and may appear in a future release.
Collection support is being prioritized. Check the latest release notes for current status. As a workaround, use document-level filtering to restrict the scope of displayed work items.
Electronic signatures are not supported directly in Risksheet because the Polarion API does not expose electronic signature capabilities for programmatic access. If your regulatory process requires signatures when rejecting items, the recommended workaround is to split the action into two steps:
  1. In Risksheet: Execute the rejection workflow action (without signature)
  2. In Polarion: Execute a separate workflow action that requires the electronic signature
This separation ensures the signature requirement is met through Polarion’s native signature mechanism while allowing the initial rejection to be performed efficiently within the Risksheet grid.

​
Approval and Review Workflows

Review columns are available for three review modes via the reviews section of the sheet configuration: comment-based reviews, work-item-based reviews, and approval reviews. You can set reviews.reviewManager to "CommentBased" for comment-based reviews, or configure the approval review variant to capture approver decisions inline in the grid.
Risksheet approval review creates approval-tagged comments on the reviewed work items but does not trigger Polarion’s formal approval workflow (draft → reviewed → approved). Status transitions still have to be performed through Polarion’s own workflow actions. For full approval workflows that require status transitions, navigate to the individual work item or use the Polarion document view. Workflow approval actions executed from within the Risksheet grid are planned for a future release.
See Set Up Review Process for current review capabilities and configuration details.
Risksheet supports freeze columns (keeping left-side columns visible during horizontal scrolling) but does not currently support freeze rows (pinning specific rows at the top during vertical scrolling). Column freezing is available through the right-click context menu or sheet configuration. Freeze rows is a recognized feature request and may be implemented in a future release.For freeze column configuration, see Configure Freeze Panes.

​
Feature Availability Summary

FeatureStatusNotes
Dependent enums (cascading dropdowns)✅ Supported (column-level)Configured per column in recent versions; not a top-level config section
Drag and drop❌ Not supportedUse autocomplete link editor instead
Mandatory field enforcement❌ Not enforced (by design)Use cellDecorators for visual highlighting
Item Id column rename❌ Not supportedsystemItemId is a reserved system column
Electronic signatures❌ Not supportedPolarion API limitation; use split workflow
Multi-document aggregation❌ Not supportedOne document per Risksheet instance
Collection awarenessPlannedHigh-priority feature request
Full Polarion approval workflow from gridPlannedApproval review tags comments only; status transitions happen in Polarion
Freeze rowsPlannedFreeze columns currently supported
Freeze columns✅ SupportedVia context menu or configuration
Review columns✅ SupportedComment-based, work-item-based, and approval-based
SFMEA/DFMEA/PFMEA✅ SupportedFully configurable per FMEA type
STRIDE, HARA, TARA, CVSS✅ SupportedRisksheet is methodology-agnostic
Multiple configs per project✅ SupportedEach document has its own sheet configuration
createInCurrentDocument✅ SupportedControls where new items are stored

​
See Also

Last modified on June 30, 2026