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

​
Does Risksheet support dependent enums (cascading dropdowns)?

Dependent enums — where the available options in one dropdown column are filtered based on the selection in a parent column — are not currently supported as a built-in feature. You can configure related enumerations using the relations array in risksheet.json to define parent-child relationships between enum definitions, but fully cascading multi-level dependent dropdown behavior is not available. Note that ratings use integers as IDs (for example, 1 through 10 for severity scales), unlike regular enumerations which use string IDs. This distinction is important when configuring risk parameter columns.
Dependent enum support may be added in future versions. Check your current release notes for updates on this feature.

​
Can I drag and drop existing work items into a Risksheet?

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.

​
Does Risksheet enforce Polarion mandatory fields?

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 or styles to highlight mandatory column backgrounds with conditional formatting: 
{
  "cellDecorators": {
    "requiredHighlight": "function(info){ if(!info.value){ $(info.cell).addClass('required-empty'); } }"
  },
  "styles": {
    ".required-empty": "background-color: #fff3e0 !important; border-left: 3px solid #e65100 !important;"
  }
}
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.

​
Can I rename the first “Item Id” column?

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

​
Can I configure Risksheet for different FMEA types (SFMEA, DFMEA, PFMEA)?

Yes. Risksheet 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 risksheet.json. Each FMEA type uses the same underlying configuration 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 risksheet.json with an independent column layout and risk parameter configuration. See Configure FMEA Workflows for setup details.

​
Does Risksheet support STRIDE analysis?

STRIDE threat analysis support is available through Risksheet’s flexible configuration. Since Risksheet has no mandatory fields or 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). See Implement STRIDE Analysis for configuration guidance.

​
Can I have multiple Risksheet configurations in one project?

Yes. Multiple Risksheet configurations per project are fully supported. Each Polarion LiveDoc document that contains a Risksheet has its own risksheet.json 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

​
Is Risksheet limited to a single document?

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. 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

​
Does Risksheet support Polarion collections?

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.

​
Does Risksheet support electronic signatures?

Electronic signatures are not supported 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

​
Can I approve work items directly from Risksheet?

Review columns are available for comment-based and approval-based review workflows via the reviews configuration in risksheet.json. You can set reviews.reviewManager to "CommentBased" for comment-based reviews. However, full workflow approval actions (changing work item status with approval signatures) executed directly from the grid are not yet available. Currently, for full approval workflows that require status transitions, navigate to the individual work item or use the Polarion document view. Workflow approval actions from within the Risksheet grid are planned for a future release. See Set Up Review Process for current review capabilities.

​
Does Risksheet support freeze rows?

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 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❌ Not supportedrelations array available but not cascading
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 approval workflowPlannedReview columns available now
Freeze rowsPlannedFreeze columns currently supported
Freeze columns✅ SupportedVia context menu or configuration
Review columns✅ SupportedComment-based and approval-based
SFMEA/DFMEA/PFMEA✅ SupportedFully configurable per FMEA type
STRIDE analysis✅ SupportedVia custom configuration
Multiple configs per project✅ SupportedEach document has independent config
createInCurrentDocument✅ SupportedControls where new items are stored

​
See Also

Support Tickets