Top-Level Properties
The sheet configuration supports the following top-level sections. All sections are optional unless noted; missing sections receive the defaults below.Risksheet does not define rating scales or enumerations in the sheet configuration. Rating scales and enums are defined as Polarion enumerations under Administration > Enumerations. A custom field on the risk work item type binds to the enum, then a column uses
type: rating:<enumId> (or type: enum:<enumId> / type: multiEnum:<enumId>) with bindings: <fieldId>. The server loads the enum values automatically — no top-level config section is required.Column Property Defaults
When a column entry in thecolumns array omits optional properties, these defaults apply:
Multi-line behavior and text wrapping are controlled through CSS classes in the
styles section and applied via cellCss on the column or through a cellDecorator. They are not column-level boolean properties.Levels Property Defaults
Each entry in thelevels array defines one visual hierarchy level. Every level entry should declare three properties — name, controlColumn, and zoomColumn — with showInMenu controlling whether the level appears in the row-creation menu:
DataTypes Property Defaults
ThedataTypes object configures the two work item entities of the Risksheet data model: risk (the main rows) and task (downstream linked items).
Risk Data Type Defaults
Task Data Type Defaults
Header Property Defaults
Global Settings Defaults
Additional
global properties (help URL, refresh behavior, menu organization) have defaults that may vary by Risksheet version. Consult the Configuration Properties Index for the complete list.Review Configuration Defaults
Risksheet’s approval-based review records approval-tagged comments. It does not trigger Polarion’s formal approval state transitions (draft to reviewed to approved). For full Polarion approval workflow, configure the document workflow separately.
Auto-Read-Only Rules
Risksheet automatically overrides thereadOnly default (false) to true for columns matching these conditions, regardless of your explicit configuration:
Runtime Properties (Server-Managed)
The following properties appear in the runtime configuration object but are set by the server at request time and must not be authored in the sheet configuration. They are listed here for completeness only:
Do not set these in the sheet configuration — values you provide will be overwritten by the server.
Configuration File Location
The sheet configuration is stored as an attachment on the Polarion LiveDoc document. The configuration resolution order is:- Document-specific sheet configuration — attached directly to the LiveDoc.
- Template-based — loaded from a global template referenced by the document’s
templateDoccustom field. - Defaults applied — factory defaults fill in any missing properties.
Complete Minimal Example
The smallest valid sheet configuration that produces a working FMEA risksheet. All other properties use their documented defaults. Theseverity and occurrence rating scales are defined as Polarion enumerations under Administration > Enumerations, with matching custom fields (sev, occ) on the failureMode work item type:
columns[].idis auto-generated frombindings(for example,title,sev,occ).columns[].typeis auto-detected for thetitlecolumn (becomestext) and explicitly set for rating columns.columns[].leveldefaults to1for all columns.columns[].readOnlydefaults tofalse.columns[].filterabledefaults totrue.levels[].showInMenudefaults totruefor both levels.dataTypes.risk.removeStrategydefaults todelete.dataTypes.risk.rejectedActiondefaults toreject.global.culturedefaults toen(shown explicitly for clarity).reviews.reviewManagerdefaults toCommentBased.
severity and occurrence rating values come from the Polarion enumerations of the same name — the server loads them automatically when a column uses type: rating:<enumId>.
Related Pages
- Sheet Configuration Format — full sheet configuration format reference
- Configuration Properties Index — alphabetical property listing
- Configuration Validation Rules — validation rules and error messages
- Document Configuration Override — document-level config overrides
- Template Path Configuration — template inheritance
- Column Type Reference — column definition properties
- Data Types — data type behavior and field mapping
- Levels Configuration — hierarchical level setup