Skip to main content

​
Supported Polarion Versions

Exact minimum and maximum Polarion version requirements may vary by Risksheet release. Always check the release notes for your specific Risksheet version before upgrading Polarion.
Risksheet VersionMinimum Polarion VersionKey Changes
24.7.0+Polarion 2310Suppresses harmless UnsupportedOperationException for renderingLayouts document field rendering
24.7.2Polarion 2310Additional bug fix release; recommended over 24.7.0
24.11.0Polarion 2310+Fixes for backLink parameter (NPT-608), baseline comparison (NPT-614, NPT-615), and comparison features (NPT-604)
25.xPolarion 2310+Check release notes for specific compatibility; includes license unification changes
25.11.0+Polarion 2310+License group change: nextedy_powersheet_users replaces nextedy_risksheet_users when Powersheet is also installed
26.1.0Polarion 2310+License flow improvements, Powersheet license alignment

​
Version Compatibility Architecture

diagram

​
Known Compatibility Issues by Polarion Version

​
Polarion 2310

Upgrading to Polarion 2310 causes an UnsupportedOperationException in server logs when the system attempts to render document fields like renderingLayouts. This error has no functional impact on Risksheet operations. The system skips failed fields and continues normally.
Symptoms:
  • java.lang.UnsupportedOperationException in Polarion server logs during Risksheet loading
  • Error message references the renderingLayouts document field
  • No visible impact on Risksheet functionality, grid rendering, or data operations
  • Error appears each time a Risksheet document is opened
Resolution: Update Risksheet to version 24.7.0 or later, which suppresses the document field rendering error. Version 24.7.2 is recommended as it also includes an unrelated bug fix. Affected versions: Risksheet versions prior to 24.7.0 running on Polarion 2310.

​
Polarion 2410

After upgrading Polarion to 2410 and updating Risksheet plugins, users may encounter unparseable query errors that prevent access to LiveDoc documents. These errors frequently originate from Polarion’s Auto Assignment feature with invalid inputs, not from Risksheet itself.
Symptoms:
  • Unparseable query errors preventing access to live documents (particularly in demo projects)
  • Stack traces referencing data service interceptors and Nextedy components
  • Errors appearing in server logs that mention Risksheet hooks even though the root cause is Polarion configuration
Root cause: Polarion’s Auto Assignment feature may contain invalid field references or user assignments that produce malformed Lucene queries. Risksheet data service hooks appear in the stack trace because they intercept data service calls, but they are not the source of the error. Resolution:
  1. Investigate Polarion configuration first, particularly Administration > Work Items > Auto Assignment
  2. Verify that all Auto Assignment rules contain valid field references and user assignments
  3. Check that custom queries in risksheet.json use valid Lucene syntax compatible with Polarion 2410
  4. Update Risksheet to the latest version compatible with Polarion 2410
Risksheet components such as data service hooks appear in error stack traces for any data service exception, even when Risksheet is not the cause. Always examine the actual error message and the originating query text to determine the true source of the problem.

​
Runtime Configuration Properties

The following properties are loaded from the Polarion runtime context and reflect version and environment information. These values are available in the browser via the window.risksheet object:
PropertyTypeDefaultDescription
versionstringSee applicationFull version string of the Risksheet application including build metadata
shortVersionstringSee applicationShortened version identifier without build metadata for display purposes
baseUrlstringSee applicationBase URL for the Risksheet application, used to construct data service endpoints and navigation URLs
projectIdstringSee applicationPolarion project identifier used in API endpoints and URL construction
revisionstring"" (empty)Document revision identifier. Empty string indicates current/head revision; non-empty value forces read-only mode automatically
currentRevisionstringSee applicationThe latest revision number of the document, used to determine if viewing current or historical version
canAdminbooleanfalsePermission flag indicating whether the current user has administrative privileges to modify configuration
settings.readonlybooleanfalseControls whether the grid allows editing. Automatically set to true when viewing historical revisions (when revision is non-empty).

​
Configuration Source Tracking

The configuration loading system tracks where each configuration was loaded from, which is essential for debugging after version upgrades:
PropertyTypeDefaultDescription
sourcestringnullPath to configuration source file (document or template) used to load the Risksheet configuration
templateNamestringnullName of template when configuration is loaded from a global template rather than document-specific config
fromTemplatebooleanfalseWhether the configuration was inherited from a template document
configPathstringNoneURI path to the configuration attachment that was actually loaded
configEditUrlstring${baseUrl}/risksheet/configuration/URL to the Risksheet configuration editor interface
documentUrlstringConstructedDirect URL to the source Polarion document in the standard Polarion UI

​
Project-Level Properties

These project-level settings are managed through Polarion administration and interact with version compatibility:
PropertyDefaultDescription
Template pathRisks/Risk SpecificationDefault document template path. Multiple paths can be comma-separated.
Tool nameRisksheetDisplay name for the tool in the Polarion navigation UI
Document name (singular)Risk AnalysisSingular form of the document type label
Document names (plural)Risk AnalysesPlural form of the document type label
Auto-suspect disabledfalseWhen true, changes made through Risksheet do not trigger suspect link marking
Suggester fuzzy searchtrueEnables approximate matching in the item suggester
Suggester wildcard searchtrueEnables wildcard characters (* and ?) in item search
Suggester result limit20Maximum number of suggestions shown when searching for items to link
Admin check bypassfalseSetting nextedy.risksheet.disable_admin_check=true bypasses admin permission requirement

​
Upgrade Procedure

​
Pre-Upgrade Checklist

StepActionDetails
1Check release notesReview both Polarion and Risksheet release notes for version compatibility
2Back up configurationsSave all risksheet.json files, Velocity templates, and project-level settings
3Test in stagingDeploy the upgrade to a non-production environment first
4Verify custom queriesTest that custom Lucene queries in risksheet.json parse correctly on the new Polarion version
5Check license groupsFor upgrades to v25.11.0+, verify user group assignments (see License Group Changes below)

​
Upgrade Steps

  1. Download the new Risksheet version from the Nextedy website
  2. Stop the Polarion server
  3. Delete the previous plugin version from the Extensions folder — do not copy the new version over the old one
  4. Copy the new plugin version into the Extensions folder (only one version folder per product should exist)
  5. Delete the cache directory at [POLARION_INSTALL]/data/workspace/.config to clear plugin caches
  6. Start the Polarion server
  7. Verify installation by checking the Risksheet Setup and License pages in Polarion Administration
A common update mistake is copying the new plugin folder over the old one, resulting in two plugin versions in the Extensions directory. This causes the Risksheet menu to disappear from the Polarion navigation. Always delete the old version folder before copying the new one.
After installing or updating Risksheet, you must delete [POLARION_INSTALL]/data/workspace/.config to clear plugin caches. Failure to do so causes empty Setup and License pages in the Polarion administration interface.

​
Post-Upgrade Verification

After upgrading, verify the following:
  1. Risksheet menu appears in the Polarion navigation panel for all projects
  2. Existing Risksheet documents open without errors
  3. The Setup page in Administration shows the correct version number
  4. The License page shows valid license status with the expected number of named users
  5. Server logs are free of unexpected exceptions (the renderingLayouts exception is harmless on versions prior to 24.7.0)
  6. Custom Velocity templates (risksheetTopPanel.vm, risksheetPdfExport.vm) render correctly
Risksheet releases can occasionally be pulled back due to discovered regressions. Always deploy updates to a staging or test environment before production to verify compatibility with your specific configuration and workflows.

​
License Group Changes in Major Upgrades

​
v25.11.0+ with Powersheet Installed

When both Risksheet and Powersheet are installed with production licenses, Risksheet v25.11.0 and later reads user assignments from the nextedy_powersheet_users group instead of nextedy_risksheet_users. This license unification change can cause all Risksheet licenses to appear inactive after upgrading. Symptoms after upgrading to v25.11.0+ or v26.1.0:
  • License page shows 0 named users configured
  • All Risksheet licenses appear inactive
  • Users cannot access Risksheet despite being in the nextedy_risksheet_users group
Resolution:
  1. Create a nextedy_powersheet_users group in Polarion
  2. Add all users from the nextedy_risksheet_users group to nextedy_powersheet_users
  3. Verify the License page shows the correct number of named users
Risksheet VersionLicense Group (Risksheet only)License Group (with Powersheet)
Pre-25.11.0nextedy_risksheet_usersnextedy_risksheet_users
25.11.0+nextedy_risksheet_usersnextedy_powersheet_users

​
Template Installation After Upgrade

After upgrading Risksheet, you may need to reinstall project templates to get updated defaults:
TemplateDescription
risksheet_templateStandard Risksheet project template for FMEA workflows
risksheet_templateHaraHARA-specific project template for hazard analysis per ISO 26262
Template installation is available via POST /admin/setup or through the Administration interface. The system detects existing templates and removes them before installing fresh versions.

​
URL Patterns

Risksheet URLs include version and project context: 
# Document view
https://polarion.example.com/polarion/risksheet/view?project=MyProject&document=Risks/FMEA

# Historical revision (read-only)
https://polarion.example.com/polarion/risksheet/view?project=MyProject&document=Risks/FMEA&revision=123

# Configuration editor
https://polarion.example.com/polarion/risksheet/configuration/?project=MyProject&document=Risks/FMEA&type=columns

​
See Also

KB ArticlesSupport TicketsSource Code
  • AppConfigParser.ts
  • ApprovalBasedReview.java
  • IReview.java
  • AppConfig.ts
  • WorkItemBasedReview.java