Prerequisites
- Administrative access to your Polarion project
- Nextedy RISKSHEET installed and configured in the project
Step 1: Understand the Default Path
Risksheet ships with a default template path:Risks/Risk Specification folder. If this folder does not exist in your project, create it in Polarion before users attempt to create documents.
Step 2: Set a Custom Template Path
To change where users can create risk documents:- Open Polarion Administration for your project
- Navigate to the Risksheet project properties section
- Set the
nextedy.risksheet.risksheetTemplatePathproperty to your desired folder:
- Save the changes
Safety/FMEA Documents folder.
Step 3: Configure Multiple Paths
To support multiple risk methodologies in separate folders, specify comma-separated paths:Step 4: Customize Document Labels
Along with template paths, you can customize how risk documents are labeled throughout the Risksheet interface:
These labels appear on the home page and in navigation menus. Customize them to match your organization’s terminology.
Path Format Rules
When specifying template paths:- Use forward slashes (
/) as path separators - Paths are relative to the project root
- Separate multiple paths with commas (no spaces after commas)
- Path names must match the actual Polarion folder structure exactly (case-sensitive)
How Document Creation Uses Template Paths
When a user creates a new document through the Risksheet home page:- The home page displays available folders based on the configured template paths
- The user selects a folder and enters a document name
- The user chooses a template (FMEA, HARA, or custom)
- Risksheet creates the LiveDoc in the selected folder with the chosen template’s sheet configuration
Step 5: Verify the Configuration
After saving your template path changes:- Open the Risksheet home page in your project
- Click to create a new document
- Verify that all configured folders appear as options in the creation wizard
- Create a test document in one of the configured paths
See Also
- Set Up Global Templates — create reusable configurations for template folders
- Override Template Configuration — detach individual documents from templates
- Configure Multi-Project Setup — share templates across projects
- Find Configuration Files — locate configuration sources