Skip to main content

Standard Project Templates

Standard templates are stored within individual projects and duplicated when creating new documents.

Step 1: Create a Template Document

  1. Navigate to the space where you want to store templates (e.g., Risks/)
  2. Create a new LiveDoc with your desired document type (e.g., riskSpecification)
  3. Name it descriptively (e.g., “FMEA Template” or “HARA Template”)
  4. Configure the RISKSHEET as needed (columns, data types, risk matrices, etc.)

Step 2: Configure the Template Field

  1. Open Administration > Documents & Pages > Document Custom Fields
  2. Select your document type (e.g., Risk Specification)
  3. Ensure the templateDoc field exists with type Enum:Document
  4. Open your template document
  5. In Document Properties, set templateDoc to the path of itself (e.g., Risks/FMEA Template)

Step 3: Register the Template Path

  1. Navigate to Administration > Configuration Properties
  2. Add or update the property:
nextedy.risksheet.risksheetTemplatePath=Risks/FMEA Template
For multiple templates, use comma-separated paths:
nextedy.risksheet.risksheetTemplatePath=Risks/FMEA Template,Risks/HARA Template,Risks/STRIDE Template

Step 4: Create Documents from Templates

  1. Open the Risksheet topic from the Polarion sidebar
  2. Click + New Blank Document
  3. Select your template from the list
  4. Enter a document name and location
  5. Click Create
The new document inherits the full RISKSHEET configuration from the template.

Global Templates (Cross-Project)

Global templates allow you to share RISKSHEET configurations across multiple projects from a central repository.

Step 1: Create a Global Template Project

  1. Create a Polarion project dedicated to templates (e.g., GlobalLibrary)
  2. In this project, create your RISKSHEET template documents
  3. Critical difference: Change the templateDoc field type to STRING (not Enum:Document):
    • Administration > Documents & Pages > Document Custom Fields
    • Select your document type
    • Change templateDoc type from Enum:Document to STRING
Global templates require the templateDoc field to be of type STRING to support the PROJECTID:path syntax. Using Enum:Document will cause template resolution to fail.
  1. Set the templateDoc property using the format PROJECTID:path:
GlobalLibrary:Risks/FMEA Template

Step 2: Configure Target Projects

  1. In each project that will use the global template, change the templateDoc field type to STRING
  2. Add the configuration property pointing to the global template:
nextedy.risksheet.risksheetTemplatePath=GlobalLibrary:Risks/FMEA Template
Multiple global templates:
nextedy.risksheet.risksheetTemplatePath=GlobalLibrary:Risks/FMEA Template,GlobalLibrary:Risks/HARA Template

Step 3: Verify Global Template Access

  1. Open the Risksheet topic in a target project
  2. Click + New Blank Document
  3. You should see templates from the GlobalLibrary project
  4. Create a document and open Configuration (gear icon)
  5. The configuration editor should indicate it’s loading from another project

Template Selection Flow

diagram
When updating a template, existing documents created from that template do NOT automatically update. To propagate changes, users must manually copy configuration from the updated template using Configuration > Copy from Template.
Do not use Polarion’s LiveDoc Reuse function to duplicate RISKSHEET templates. This creates full document copies with duplicate configuration attachments, leading to maintenance overhead. Always use + New Blank Document from the Risksheet topic.

Verify the Setup

For standard templates:
  1. Open the Risksheet topic
  2. Click + New Blank Document
  3. You should see your configured templates in the selection list
  4. Create a document and verify it inherits the expected configuration
For global templates:
  1. Verify the template appears in projects other than the GlobalLibrary project
  2. Create a document from the global template
  3. Open Configuration and confirm it shows the source project in the title (e.g., “Configuration from GlobalLibrary”)

See Also

KB ArticlesSupport TicketsSource Code
  • RisksheetProduct.java
  • DocumentConfigProvider.java
  • RisksheetSetupService.java
  • AppConfig.ts
  • RisksheetViewServlet.java