Configuration Questions - Nextedy Documentation

What ships out-of-the-box with Risksheet?

Risksheet includes two default project templates that can be installed via Administration > Nextedy Risksheet > Setup: a standard risksheet_template for general FMEA risk analysis and a risksheet_templateHara for HARA workflows. These templates provide starting configurations with pre-built columns, formulas, and risk scales. However, most organizations customize the configuration to match their specific work item types, custom fields, and risk methodologies. Risksheet does not require specific work item types or mandatory Polarion fields — it adapts to your existing Polarion setup through the sheet configuration.

Where is the Risksheet configuration stored?

The configuration is stored in a file named risksheet.json attached to each Polarion LiveDoc document. If a document does not have its own sheet configuration, it inherits the configuration from its Polarion document template hierarchy. You can also define global templates that multiple documents inherit from. The sheet configuration file contains the complete configuration including columns, dataTypes, levels, formulas, styles, cellDecorators, views, global, reviews, and sortBy. Rating and enumerated values are not stored as top-level sections in the file — they are defined as Polarion enumerations and referenced from columns (for example via type: rating:<enumId>). You can edit it using the built-in configuration editor (accessible to users with canAdmin privileges) or by modifying the JSON attachment directly.

For more details, see Configuration Questions and the Getting Started tutorial.

How do I configure multiple risk analysis types in one project?

Risksheet supports multiple configurations per project. Each Risksheet document has its own sheet configuration, so you can create separate documents for each risk analysis type (e.g., one for FMEA, one for HARA, and one for STRIDE) and configure each independently. The dataTypes section determines which Polarion work item types appear as risk items and mitigation tasks:

dataTypes:
  risk:
    type: fmea_risk
    role: has_cause
  task:
    type: mitigation_action
    role: mitigates
    showInMenu: true

The template path configuration supports multiple paths separated by commas (default: Risks/Risk Specification), allowing you to organize different risk document types in different folders within your project.

Does Risksheet require specific work item types or fields?

No. Risksheet does not mandate specific Polarion work item types or custom fields. You configure which work item types to use through the dataTypes.risk.type and dataTypes.task.type properties in sheet configuration. Columns are bound to any Polarion field using the bindings property. The system supports all standard Polarion field types: text, integer, float, date, datetime, time, boolean, enum, multiEnum, duration, currency, rating, and user references. Custom fields are accessed the same way as built-in fields.

You can use any custom work item type as your risk or task type. Configure color coding via cellDecorators, merged cells via levels configuration, and risk scales via Polarion enumerations referenced from columns with type: rating:<enumId> — all without requiring predefined Polarion fields.

How do I customize the tool name and document labels?

Use project-level properties in Polarion administration to rebrand Risksheet for your organization:

Property	Default	Description
Tool name	`Risksheet`	Display name in the Polarion navigation UI. Change to match your methodology (e.g., “FMEA Tool”, “Risk Matrix”, “Safety Analysis”).
Document name (singular)	`Risk Analysis`	Singular form used in document creation dialogs and labels
Document name (plural)	`Risk Analyses`	Plural form used in document list headers and navigation

These properties are set at the project level and affect all Risksheet documents within that project.

How does the autocomplete search work for linking items?

The item suggester provides autocomplete when linking work items in item link and multi-item link columns. Several project-level properties control its behavior:

Setting	Default	Purpose
Fuzzy search	`true`	Allows approximate matches to help find items with slight spelling variations or typos
Wildcard search	`true`	Supports `*` and `?` wildcard patterns in search queries
Keyword mandatory	`false`	When `true`, requires keyword input before searching; when `false`, all matching items are shown
Result limit	`20`	Maximum number of suggestions displayed. Higher values may impact performance.
All-field search	`false`	When `true`, searches all fields of linked items rather than just primary fields. May impact performance.

You must type at least 3 characters to trigger the autocomplete search. Shorter input produces no results by design. Duplicate items cannot be selected — the system prevents adding an item that is already linked and shows a notification if you attempt to add a duplicate. You can further customize suggestions using queryFactory functions on individual columns or data types.

How do I create items within the current document?

Use the createInCurrentDocument parameter to store newly created upstream items within the same LiveDoc document rather than in a separate location. This is configured in the dataTypes section of sheet configuration and reduces context switching when building traceability chains.

The exact parameter name and behavior should be verified against your Risksheet version’s configuration reference, as this feature may have additional options or constraints.

Does Risksheet support branching?

Yes. Risksheet supports Polarion branched documents. Enable branching support by setting the project property:

nextedy.risksheet.branchingSupport = true

The property name uses a lowercase n in nextedy. This is case-sensitive — using an uppercase N (e.g., Nextedy.risksheet.branchingSupport) will not enable branching support. Double-check the exact casing in your project properties configuration.

Can I disable suspect link marking for Risksheet changes?

Yes. By default, changes made through Risksheet trigger Polarion’s automatic suspect link marking on traceability relationships. To disable this behavior, set the auto-suspect disabling property to true in project administration. When enabled, edits made in Risksheet will not flag upstream or downstream linked items as suspect. This may be desirable in workflows where Risksheet edits are considered routine updates that should not require re-verification of linked items.

Can I protect approved or verified work items from editing?

Yes. Item protection for approved or verified work items is supported through a combination of Polarion permission management and Risksheet configuration properties. Certain system fields (id, status, type, project, outlineNumber, author, resolution, created, updated) are always read-only in Risksheet. Additionally, any column can be marked as readOnly in the column configuration, and the entire grid can be set to read-only using the top-level readonly property.

The specific configuration for protecting items based on workflow status (e.g., approved, verified) should be verified against your Risksheet version’s permission management documentation.

Do catalogs work with Risksheet?

Catalogs used with Risksheet must be work item collections, not plain text in documents. Risksheet operates on Polarion work items, so any catalog data must be stored as work items that can be queried and linked through the standard Polarion data model.

​See Also

See Also