Override Template Configuration

​

Prerequisites

• Administrative privileges (canAdmin must be true for your account)
• A Risksheet document that currently inherits from a template

​

When to Override

​

Step 1: Override the Template

1. Open the Risksheet document in Polarion
2. Click the ☰ Menu button in the Risksheet toolbar
3. Select Override Template

Risksheet copies the template’s risksheet.json content and attaches it directly to the current document. The document now has its own independent configuration. After the override:

• fromTemplate is set to false
• templateName is cleared
• The source property points to the document’s own attachment
• Changes to the global template no longer affect this document

​

Step 2: Edit the Overridden Configuration

Once a document has its own configuration, edit it using either method: Using the Configuration Editor:

1. Open the Risksheet document
2. Click Menu > Configuration
3. The editor opens with the document’s local risksheet.json
4. Make changes and save

Using direct JSON editing:

1. Open the LiveDoc document in Polarion
2. Navigate to the document’s Attachments section
3. Download the risksheet.json file
4. Edit the JSON in a text editor (validate with a JSON linter)
5. Upload the modified file back as an attachment

​

Revert to Template Configuration

To re-link a document to its original template:

1. Open the Risksheet document
2. Click the ☰ Menu button
3. Select the option to revert to the template configuration
4. Risksheet removes the document-specific risksheet.json attachment and restores the template link

​

Identify Configuration Source

You can determine whether a document uses its own configuration or inherits from a template:

​

Step 3: Verify the Override

After overriding the template:

1. Open the Risksheet document and verify your custom configuration is active
2. Check the document attachments to confirm risksheet.json is present
3. Make a small change (such as hiding a column) and verify it persists after page refresh
4. Open another document linked to the same template and confirm it still shows the original template configuration

You should now see the document running with its own independent configuration, while other documents linked to the same template remain unaffected.

​

Best Practices

• Document the reason for overriding in the document’s description so team members understand why the configuration differs
• Review overridden documents periodically to determine if they can be re-linked to an updated template
• Back up before reverting — download the risksheet.json before restoring the template link

​

See Also

• Use the Configuration Editor — modify the overridden configuration
• Find Configuration Files — verify the configuration source
• Set Up Global Templates — understand the template you are overriding
• Configure Template Paths — control where documents are created

Sources

KB Articles

• Adjusting Risksheet configuration
• Risksheet Configuration Properties

Support Tickets

• #6596
• #6599
• #6836

Source Code

• DocumentConfigProvider.java
• AppConfig.ts
• RisksheetViewServlet.java
• OpenHelpCommand.ts
• PdfExportConfigurationService.java