Skip to main content

​
What You Will Achieve

By the end of this tutorial, you will have Risksheet installed in your Polarion ALM environment with the administration pages accessible and the Risksheet topic visible in your project navigation. You will be ready to create your first risk analysis document.

​
Prerequisites

Before you begin, confirm the following:
  • Polarion ALM is installed and running (supported version)
  • You have administrator access to the Polarion server (file system access and Polarion admin role)
  • You have the Risksheet installation package (.zip or .jar file) provided by Nextedy
  • You have a valid Risksheet license file (or plan to use the evaluation period)
  • Server restart capability (you will need to restart Polarion during the process)
If you are adding Risksheet to a Polarion instance that already has projects, you will need to configure each project individually after installation. This tutorial covers the server-level installation. See Add Risksheet to Existing Project for project-level setup.

​
Installation Steps

​
Step 1: Deploy the Plugin Files

Copy the Risksheet plugin files to your Polarion extensions directory: 
[POLARION_INSTALL]/polarion/extensions/
Place the Risksheet .jar files and any accompanying resources into this directory. If you received a .zip archive, extract its contents into the extensions folder. You should see the Risksheet plugin files listed in the extensions directory alongside any other Polarion extensions you have installed.

​
Step 2: Delete the Configuration Cache

This step is critical. Remove the cached configuration directory to ensure Polarion detects the new plugin: 
[POLARION_INSTALL]/data/workspace/.config
Delete the entire .config directory (not just its contents). Polarion will regenerate this directory on the next startup.
Failing to delete [POLARION_INSTALL]/data/workspace/.config is the most common cause of installation problems. If you skip this step, the Risksheet Setup and License pages in Polarion administration will appear empty with no content. This step is required both for fresh installations and for updates to newer versions.

​
Step 3: Restart Polarion

Restart the Polarion server to load the new plugin: diagram Depending on your environment, use the appropriate service command:
  • Linux: systemctl restart polarion or the Polarion-provided startup script
  • Windows: Restart the Polarion service through Services management console
Wait for Polarion to fully start. The startup process may take several minutes depending on your server configuration and the number of installed extensions.

​
Step 4: Install the Demo Project

After Polarion restarts, log in as an administrator and navigate to: Administration > Risksheet > Setup Click the Install button to install the Nextedy demo project and default templates. This step provisions:
  • The Risksheet topic definition (required for navigation)
  • Default document templates for FMEA and HARA
  • Sample risk work item types and custom fields
  • Example risksheet.json configurations
The Nextedy demo project must be installed before the Risksheet topic becomes available in any project. Without this step, you cannot add the Risksheet navigation entry to your projects. Even if you plan to create entirely custom configurations, the demo project provides the foundational topic definition.
You should see a success message confirming the templates have been installed.

​
Step 5: Verify the License Page

Navigate to Administration > Risksheet > License to verify your license status. You should see:
  • Your license type (Evaluation, Named, or Unlimited)
  • The number of server users detected
  • The expiration date (if applicable)
  • The license status showing as Active
If the License page appears empty with no content, return to Step 2 and confirm the .config directory was fully deleted, then restart Polarion again.

​
Step 6: Configure the Risksheet Topic for Your Project

Navigate to your target project and open Administration > Topics. Add the Risksheet topic entry to your project’s navigation views: 
<topic id='risksheet'/>
This entry must be present in every Polarion view (hat) where users need to access Risksheet. Without it, users assigned to that view will be redirected to the space home page when attempting to open a Risksheet document.
If your Polarion instance uses multiple views (hats) for different roles, add the <topic id='risksheet'/> entry to each view that should have Risksheet access. Missing the topic in a specific view is the most common reason users report that Risksheet is not working for them while it works for others.
You should see “Risksheet” (or your configured tool name) appear in the project navigation sidebar after saving the Topics configuration.

​
Step 7: Verify the Installation

Open a project where you configured the Risksheet topic and click the Risksheet entry in the navigation sidebar. You should see the Risksheet home page showing:
  • Available folders for creating new risk documents
  • Template selection options
  • Any existing risk analysis documents in the project
If you are redirected to the space home page instead, verify the topic configuration in Step 6 for the view your user account is assigned to.

​
Post-Installation Checklist

ItemStatus
Plugin files deployed to extensions/Verify files exist
.config directory deleted and regeneratedCheck after restart
Polarion restarted successfullyCheck Polarion logs
Demo project installed via Setup pageSetup page shows success
License page shows active licenseLicense page loads with data
Risksheet topic added to project viewsTopic visible in sidebar
Risksheet home page accessibleNo redirect to space home

​
Next Steps

With Risksheet installed and accessible, proceed to: