Skip to main content

​
Prerequisites

  • RISKSHEET installed in all target projects
  • Administrative access to all projects
  • Understanding of configuration hierarchy

​
Architecture Overview

Multi-project setups typically follow one of two patterns: diagram

​
Option 1: Set Up Centralized Template

Create a global template project that other projects reference for shared configuration.

​
Step 1: Create Template Project

  1. Create a new Polarion project named GlobalLibrary (or similar)
  2. Install RISKSHEET demo project via Administration > Extensions > RISKSHEET Setup
  3. Navigate to the demo template document
  4. Copy configuration to your template project

​
Step 2: Configure Template Document

In GlobalLibrary, create a template document with shared configuration: 
{
  "columns": [
    {"binding": "id", "header": "ID", "width": 100},
    {"binding": "title", "header": "Risk Description", "width": 300},
    {"binding": "severity", "header": "Severity", "width": 120},
    {"binding": "occurrence", "header": "Occurrence", "width": 120}
  ],
  "formulas": {
    "rpn": "severity * occurrence * detection"
  },
  "ratings": {
    "severity": [1, 2, 4, 6, 8, 10],
    "occurrence": [1, 2, 3, 4, 5, 6]
  }
}

​
Step 3: Configure Custom Field Type

For global templates (cross-project references), the templateDoc custom field must be STRING type, not Enum:Document. Projects with Enum:Document field type can only reference templates within the same project.
Create a custom field in consuming projects:
  • Field ID: templateDoc
  • Field Type: String
  • Scope: Document level

​
Step 4: Reference Template in Consuming Projects

In each consuming project, create a RISKSHEET document and set the templateDoc custom field: Value format: PROJECTID:TEMPLATE_PATH Example: GlobalLibrary:Risks/StandardTemplate

​
Step 5: Verify Template Loading

  1. Open the RISKSHEET in the consuming project
  2. Check Menu > Configuration > Edit Risksheet Configuration
  3. Verify configuration loads from GlobalLibrary project
  4. Confirm columns and formulas match the template
Documents using templates inherit all configuration. Use document-specific overrides to customize individual sheets while maintaining template baseline.

​
Option 2: Configure Cross-Project Linking

Enable RISKSHEET columns to fetch linked work items from multiple projects. Use space-separated Velocity snippets in typeProperties to query multiple projects: 
{
  "columns": [
    {
      "binding": "linkedRequirements",
      "type": "multiItemLink",
      "header": "Related Requirements",
      "typeProperties": "$config.projectA_linkType $config.projectB_linkType"
    }
  ]
}
Set configuration properties for each project: 
{
  "projectA_linkType": "relates_to@ProjectA",
  "projectB_linkType": "relates_to@ProjectB",
  "fallbackProject": "ProjectC"
}
Configuration property variables cannot be empty. Fallback projects must use hardcoded project IDs, not variable references like $config.fallbackProject. Use literal project ID strings instead.

​
Step 3: Configure Search Scope

Enable all-project search for linked items: 
{
  "columns": [
    {
      "binding": "upstreamItems",
      "type": "itemLink",
      "typeProperties": {
        "searchScope": "NextedyAll"
      }
    }
  ]
}
Search Scopes:
  • NextedyAll — Search across all projects
  • NextedyNextPhase — Search current and downstream projects

​
Option 3: Add RISKSHEET to Existing Project

Integrate RISKSHEET into a project that wasn’t created from a template.

​
Step 1: Install Demo Project

The demo project must be installed first via Administration > Extensions > RISKSHEET Setup before the risksheet topic becomes available for configuration.
  1. Navigate to Administration > Extensions
  2. Locate RISKSHEET Setup
  3. Click Install Demo Project
  4. Wait for installation to complete

​
Step 2: Configure Work Item Type

Create or modify a work item type for risk items:
  1. Go to Administration > Work Items > Types
  2. Create or edit type (e.g., risk, fmea, hara)
  3. Add required fields: severity, occurrence, detection, rpn

​
Step 3: Configure Document Type

Set the nextedy.risksheet.riskDocumentType property on document types:
  1. Navigate to Administration > Documents > Types
  2. Edit the document type that will contain RISKSHEET
  3. Add custom property:
    • Key: nextedy.risksheet.riskDocumentType
    • Value: true

​
Step 4: Add RISKSHEET Topic

  1. Go to Administration > Portal > Topic Configuration
  2. Add new topic with ID: nextedy.risksheet
  3. Configure topic visibility and permissions
  4. Save and refresh the portal

​
Step 5: Create First Document

  1. Create a new document of the configured type
  2. Open the document
  3. Add the RISKSHEET topic from available topics
  4. Configure columns and settings via Configuration Editor

​
Common Pitfalls

Users must have project-level access to both the template project and the consuming project to see and use global templates. Missing permissions cause “Template not appearing” errors.
Using Enum:Document instead of String for the templateDoc field restricts template references to the same project only. Cross-project templates require String type.
In multi-node Polarion deployments, configuration changes may not propagate immediately. Restart all nodes or clear application cache if configuration updates don’t appear.

​
Verification

After configuring multi-project setup, verify:
  1. Template loading: Open Configuration Editor and confirm settings match template
  2. Cross-project links: Create a link column and verify items from other projects appear in autocomplete
  3. Permissions: Test with different user roles to ensure proper access control
  4. Search scope: Verify linked items resolve correctly across project boundaries
You should now see RISKSHEET documents loading configuration from centralized templates and/or displaying linked items from multiple Polarion projects.

​
See Also

Support TicketsSource Code
  • RisksheetProjectProperties.java
  • CellEditorFormatter.ts
  • RisksheetDataStorage.java
  • SuggestionServlet.java
  • RisksheetSetupService.java