Override Template Configuration

​

Prerequisites

• Administrative privileges for the Polarion project
• A Risksheet document that currently inherits from a template

​

When to Override

Risksheet is a generic tool supporting any risk methodology — FMEA, HARA, TARA, STRIDE, and CVSS — so an override may be useful whenever a single document needs to diverge from the shared template configuration.

​

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 sheet configuration content and attaches it directly to the current document. The document now has its own independent sheet configuration, decoupled from the global template. After the override:

• The document has its own sheet configuration attachment
• Changes to the global template no longer affect this document
• The document continues to behave normally — only its configuration source has changed

​

Step 2: Edit the Overridden Configuration

Once a document has its own sheet configuration, edit it using either method. Using the configuration editor:

1. Open the Risksheet document
2. Click Menu > Configuration > Edit Risksheet Configuration
3. The editor opens with the document’s local sheet configuration
4. Make changes in the YAML editor (syntax highlighting and error detection are available since v25.5.0) and save

Using direct file editing:

1. Open the LiveDoc document in Polarion
2. Navigate to the document’s Attachments section
3. Download the sheet configuration attachment
4. Edit the file in a text editor
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 Revert to Template
4. Risksheet removes the document-specific sheet configuration attachment and restores the template link

​

Identify Configuration Source

You can determine whether a document uses its own sheet configuration or inherits from a template by inspecting the document attachments and the Risksheet toolbar:

​

Runtime Properties (Server-Managed)

When tooling or diagnostic views read a sheet configuration through the Risksheet server, several runtime properties are attached that describe the configuration’s provenance:

• fromTemplate — true when the document still inherits from a template, false when overridden
• templateName — the display name of the template (populated only while inheriting)
• source — the resolved attachment path (the template’s attachment while inheriting, the document’s own attachment after override)
• canAdmin — whether the current user is permitted to change the configuration source
• reviewer — populated when an approval review is in progress for the document

These properties are set by the server at runtime. They are not part of the user-editable sheet configuration and must not be written into the YAML. They appear in administrative tools and diagnostic views only.

​

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 the sheet configuration is present locally
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 sheet 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 sheet configuration attachment before restoring the template link

​

See Also

• Use the Configuration Editor — modify the overridden sheet 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