Prerequisites
- Polarion administrator access to set project administration properties
- An existing Risksheet document to branch from
- Familiarity with Polarion document branching
1
Enable Branching Support
Branching support is controlled at the project administration level, not in the sheet configuration. Navigate to Administration > Nextedy Risksheet > Setup and add the following project administration property:
2
Branch a Document
- Open the source LiveDoc containing your risk analysis in Polarion.
- Use Polarion’s standard branching mechanism to create a branch of the document.
- Open the branched document in Risksheet.
3
Enable Editing of Referenced Work Items (Optional)
If you need users to edit referenced items in branched documents without overwriting them, set the following project administration property (available since v23.3.3):When this property is enabled, referenced work items in branched documents become directly editable in the grid without requiring an overwrite operation. Verify the behavior in your Risksheet version before relying on it for production workflows, as changes may propagate to the source document depending on configuration.
editableReferencedWorkItems is a project administration property configured under Administration > Nextedy Risksheet > Setup (v23.3.3+). It is NOT a property of the sheet configuration. Setting it inside the sheet configuration has no effect — the engine reads it only from project administration.4
Overwrite Referenced Items
To create a local copy of a referenced risk item in your branched document:
- Right-click the referenced row in the Risksheet grid.
- Select Overwrite Row Item from the context menu.
- The item changes from reference mode to overwrite mode, becoming fully editable.
5
Handle Document Queries
When branching support is enabled, Risksheet automatically adjusts its data queries to use the
document.id parameter. This ensures that only work items belonging to the current branched document are displayed.Variant Management with Branches
For projects that need release-based filtering across branches, Risksheet supports theassignedReleases document custom field to filter downstream items by release version. This is useful in variant projects where you maintain separate branches per product release.
For detailed variant management configuration, see Configure Variant Management.
refreshOnSave Interaction
When using branched documents with the sheet configuration propertyrefreshOnSave set to false, be aware of two behaviors:
- A “Discard changes” popup may appear when navigating away, even though changes were saved successfully. This is a known side effect of the non-refresh mode.
- The overwrite context menu option requires
refreshOnSaveto be enabled (the default). If you have disabled it, the overwrite option will not appear.
Known Limitations
Verification
You should now see referenced items from the source document displayed in read-only mode when you open a branched Risksheet document. Verify that:- Referenced items appear with read-only styling in the grid
- Right-clicking a referenced item shows the Overwrite Row Item option
- Overwriting an item converts it to an editable local copy
- The “is branched from” link is preserved after overwriting
See Also
- Configure Variant Management — manage product variants with branched documents
- Configure Upstream Traceability Columns — set up traceability in risk tables
- Configure Cross-Project Linking — link work items across projects
- Troubleshoot Administration Issues — resolve common configuration issues