The properties on this page are configured at the Polarion project administration layer, not in the per-document sheet configuration file. They are read by Risksheet at server startup and on project-property changes. Configuration of grid behavior (columns, levels, formulas, styles) lives in the sheet configuration — see the Sheet Configuration Format.
Property Domains
Property Format
Properties live in Polarion’scontext.properties file. Each property is a key=value pair on a single line. Comments start with #.

PDF Export Properties
risksheet.pdf.additionalFonts
Defines which additional font detection areas are enabled during PDF export. The value is passed as a list of font area names. Items can be separated by spaces, commas, or semicolons.
Supported font area values:
Behavior:
- When the value is empty, contains only whitespace, or the setting is missing, only the latin font area is detected.
latinis always enabled, even if it is not listed explicitly. The latin area also covers the math font fallback used for mathematical symbols.- Unsupported values are ignored for font detection and are logged to the browser console during PDF export.
latin, chinese, and japanese.
latin, hebrew, thai, and arabic (semicolon delimiter).
latin, chinese, japanese, and korean (space delimiter).
Unsupported entries (typos, removed scripts) are silently ignored at detection time. Open the browser console during PDF export to see ignored values.
Permission and Visibility Properties
These properties control read/write visibility of work items and fields in the Risksheet grid. All are prefixednextedy.risksheet..
nextedy.risksheet.upstreamSubColumnsReadonly
Controls whether sub-columns derived from upstream linked items (e.g.,
bindings: harm.title) are rendered as read-only. When true, the grid prevents editing of fields that belong to upstream work items reached through an itemLink or multiItemLink column.
nextedy.risksheet.checkPrototypePermissions
Controls whether the grid checks the user’s permissions against the prototype (work item type definition) when rendering editable cells. When
true, fields the user cannot edit at the prototype level are rendered read-only.
nextedy.risksheet.editableReferencedWorkItems
When
true, allows editing of fields belonging to upstream/downstream referenced work items directly in the grid (subject to user permissions).
This property is a project administration setting, not a sheet configuration property. It cannot be set in the sheet configuration file.
nextedy.risksheet.checkInstanceFieldPermissions
When
true, the grid checks per-instance field permissions in addition to prototype permissions. Cells that the user cannot edit on a specific work item instance are rendered read-only.
nextedy.risksheet.moduleOnlyPermissions
When
true, permission checks consider only the module (LiveDoc) context, not the global project context.
Workflow and Compliance Properties
nextedy.risksheet.checkLinkRoleCompliance
When
true, the grid validates that link roles used in itemLink and multiItemLink columns comply with the Polarion link role definitions. Non-compliant links are flagged.
nextedy.risksheet.branchingSupport
When
true, enables Risksheet behavior compatible with Polarion’s branching feature. Risk items in branched documents are handled with branch-aware loading.
nextedy.risksheet.downstreamFromRevision
When
true, downstream task items are loaded as of a specific revision (used together with revision-based document viewing).
nextedy.risksheet.loadTasksFromDocument
When
true, downstream task items are loaded from documents (LiveDocs) rather than from a free-form query. Use together with dataTypes.task.document in the sheet configuration to scope task loading to a specific document. See Document Configuration Override.
Template Path Properties
nextedy.risksheet.risksheetTemplatePath
Specifies the default template document path used when creating a new Risksheet document. Format is
PROJECTID:TEMPLATE_PATH to point at a template located in another Polarion project (typically a global library), or a plain path (Risks/Risk Specification) for the current project.
templateDoc custom field on documents, which holds the connection between a Risksheet document and its template. See Template Path Configuration.
Suggester (Autocomplete) Properties
These properties tune the behavior of autocomplete suggestions used by itemLink and multiItemLink columns.nextedy.risksheet.isSuggesterFuzzySearching
When
true, the suggester applies fuzzy matching so close-but-imperfect typos still return matching items.
nextedy.risksheet.isSuggesterWildcardSearching
When
true, the suggester treats user input as a wildcard pattern, expanding the search to match anywhere in the indexed field.
nextedy.risksheet.isSuggesterKeywordsMandatory
When
true, every entered keyword must match (logical AND). When false, any match is acceptable (logical OR).
Property Decision Reference
Use this matrix to pick the right behavior knob for common requirements.Versioned Property Summary
Complete Example
A fullcontext.properties block configuring a multi-script regulated environment (medical devices ISO 14971) with a global template library, strict permission checks, and Chinese/Japanese/Korean PDF export support:
Related Topics
- Configuration Properties Index — alphabetical index of all configuration properties
- Default Configuration Values — defaults for sheet configuration sections
- Sheet Configuration Format — per-document configuration (columns, levels, formulas)
- Template Path Configuration — template document resolution
- Document Configuration Override — document-level configuration override
- Configuration Reference Index — entry point for all configuration topics