Skip to main content

​
Common Issues and Solutions

​
Empty Setup or License Pages

Symptom: After installing or updating Risksheet, the Setup and License pages in Administration are empty or fail to load. Cause: Plugin caches were not cleared after the update. Fix:
  1. Stop the Polarion server.
  2. Delete the [POLARION_INSTALL]/data/workspace/.config directory.
  3. Restart the Polarion server.
  4. Navigate to Administration > Nextedy Risksheet > Setup to verify.
This is the most common post-installation issue. Delete [POLARION_INSTALL]/data/workspace/.config after every Risksheet installation or update.

​
Risksheet Menu Not Appearing

Symptom: The Risksheet entry does not appear in the project navigation after installation or update. Cause: Either two plugin versions exist in the extensions folder, or the Risksheet topic is not configured for the user’s view/role. Fix:
  1. Check [POLARION_INSTALL]/polarion/extensions/ for duplicate Risksheet folders. Delete the old version.
  2. Verify Administration > Topics includes the Risksheet topic for all relevant views and roles.
  3. If the .metadata folder exists in the extensions directory, delete it.

​
UnsupportedOperationException in Server Logs

Symptom: Server logs show UnsupportedOperationException related to document field rendering (for example, renderingLayouts) when opening a Risksheet. Cause: A known document field rendering issue, particularly after upgrading to Polarion 2310. Fix: This error has no functional impact on Risksheet. The system skips failed fields and continues normally. Update to Risksheet 24.7.0+ to suppress these log entries.
SymptomCauseResolution
Empty Admin PagesCorrupted workspace configDelete data/workspace/.config, restart Polarion
Menu MissingDuplicate extensions or missing topic configCheck extensions/ for duplicates, verify Topics configuration
UnsupportedOperationExceptionKnown document field rendering issueNon-harmful — update to Risksheet 24.7.0+ to suppress
StringIndexOutOfBoundsMisconfigured risksheet.jsonCheck risksheet.json syntax with JSON linter
Query Parse ErrorsInvalid Polarion configurationCheck Polarion config settings
License Shows 0 UsersMissing user groupCreate nextedy_powersheet_users group or restart Polarion

​
Velocity Template Errors

Symptom: StringIndexOutOfBoundsException appears in server logs, possibly related to topPanel.vm or other Velocity templates. Cause: Misconfigured risksheet.json or custom Velocity template files. Fix:
  1. Review your risksheet.json for syntax errors.
  2. Check any custom topPanel.vm template for malformed Velocity expressions.
  3. Validate JSON syntax using a JSON linter.

​
License Shows 0 Named Users

Symptom: The License page shows 0 named users despite users being in the nextedy_risksheet_users group. Cause: Either the license needs to be refreshed, a service restart is required, or the user group name is wrong after a version upgrade. Fix:
  1. Reopen the Administration > Nextedy Risksheet > License page.
  2. If still 0, restart the Polarion service.
  3. If both Risksheet and POWERSHEET are installed (v25.11.0+), create a nextedy_powersheet_users group and add users to it.
If your team needs access to internal documentation, configure the settings.global.help property in your risksheet.json to point to your organization’s documentation URL. The default points to the official Nextedy support portal.

​
Verification

After resolving any of the above issues, you should now see the Risksheet administration pages loading correctly, the navigation menu appearing for all configured user roles, and the License page displaying the correct version and user counts.

​
See Also

Support TicketsSource Code
  • OpenHelpCommand.ts
  • PolarionAppConfigManager.java