Skip to main content
diagram

Item Identity Fields

These bindings track work item identity across revisions and enable baseline comparison. Risksheet uses them to maintain item relationships when viewing historical revisions or comparing baselines.
NameTypeDefaultDescription
systemItemIdstringServer-assignedThe Polarion work item ID. Used for cross-reference, linking, and grouping tasks under parent items. This is the primary identifier that links grid rows to Polarion work items. Tasks use this field to reference their parent risk item.
systemOriginalItemIdstringServer-assignedThe original item identifier preserved across revisions. When viewing historical document versions, this field maintains the identity of the item even when its revision changes. Enables Risksheet to track an item across its entire revision history.
systemItemProjectIdstringCurrent projectThe project ID where the work item resides. Used in cross-project Risksheet configurations to identify which project a particular item belongs to. Critical when the grid displays items from multiple projects.
systemItemRevisionstringCurrent revisionThe specific version/revision of the work item. Used in baseline comparison workflows to identify which revision of an item is being displayed. When viewing a specific document revision, this field reflects the item’s state at that point in time.
systemItemFrozenRevisionstringNoneThe frozen revision identifier for baseline snapshots. Set when a document baseline is created, locking the item to a specific revision for traceability purposes.
When viewing a historical document revision (i.e., when the revision parameter is set in the URL), the entire Risksheet grid is automatically forced into read-only mode. This is controlled by the configuration parser, which sets readonly to true whenever a non-empty revision is detected.

Standard Item Data Bindings

These bindings provide access to common work item properties that appear in grid columns and drive navigation behavior.
NameTypeDefaultDescription
IDstringServer-assignedStandard binding key used to identify unique work items in the grid data model. Displayed in ID columns. For newly created items, this shows a temporary ID prefixed with * until the item is saved.
tempIdstringGeneratedTemporary identifier assigned to newly created items before server assignment. Visible in the grid until the first save operation, after which it is replaced by the permanent Polarion work item ID.
revisionstringCurrentThe current revision number of the work item. Appears in the grid when viewing historical document versions.
idNewbooleantrue for new itemsFlag indicating the item has not been saved to the server yet. Items with idNew set to true show the temporary *-prefixed ID. After saving, this flag is cleared and the permanent ID is assigned.
linkstringGenerated URLHyperlink URL to the Polarion work item in the standard Polarion editor. Enables click-to-navigate behavior in the grid — clicking an item ID or using the Open Row Item context menu action opens this URL.
titlestringEmptyThe work item title text. Bound to the title column in the grid.
labelstringEmptyDisplay text label for the work item. Used for rendering item references in link columns and autocomplete suggestions.
For columns that reference linked work items, Risksheet uses a naming convention with a _link suffix.
NameTypeDefaultDescription
{binding}_linkstringServer-rendered HTMLAppended to any column binding name to access the pre-rendered HTML link for that linked item. For example, a column with binding sysReq has a corresponding sysReq_link property containing the HTML hyperlink. This suffix is used for both item link and task link column types.
The _link suffix convention applies throughout Risksheet. When you define an item link column with "id": "sysReq", the system automatically creates a companion property sysReq_link containing the rendered HTML for that link. The same pattern applies to task link columns — a column with "id": "taskId" generates taskId_link.

Read-Only State Fields

These fields control which items and cells can be edited in the Risksheet grid. Read-only state operates at multiple levels: grid-level, item-level, field-level, and task-specific.

Item-Level Read-Only

NameTypeDefaultDescription
systemReadOnlybooleanfalseMarks the entire item as non-editable. When true, all cells in the row are locked and cannot be modified by the user. This flag is set based on Polarion permissions, document state, or workflow conditions. The grid visually marks affected cells with a readonly CSS class.
systemReadOnlyFieldsarray[]Lists specific field names that are non-editable for this item, even if the item itself is otherwise editable. This enables fine-grained control where certain fields (e.g., fields controlled by workflow transitions) are locked while others remain editable. Each entry is a string matching a column binding ID.

Task-Level Read-Only

NameTypeDefaultDescription
systemTaskReadOnlybooleanfalseMarks linked task items as non-editable, separate from the parent risk item’s read-only state. When true, all task-specific columns in the task row are locked. This allows a risk item to be editable while its associated mitigation tasks are read-only (or vice versa).
systemTaskReadOnlyFieldsarray[]Lists specific fields that are non-editable in linked task items. Allows field-level control over task editing permissions independently from the parent risk item’s permissions.
The Polarion resolution field cannot be edited from within Risksheet. This field is typically a mandatory field during status transitions, and status changes from Risksheet only work when all transition conditions are met without mandatory field requirements. If you need to set the resolution, use the Polarion work item editor directly.

Read-Only State Hierarchy

Read-only state is determined at multiple levels, with the most restrictive level taking precedence:
LevelSourceEffect
Grid-levelreadonly: true in risksheet.jsonAll cells in the entire grid are non-editable
Revision-basedNon-empty revision URL parameterForces readonly: true for the entire grid
Downstream-leveldownstreamReadonly: true in risksheet.jsonItems from linked documents are non-editable; task creation is blocked for those items
Reviewer modereviewer: true in risksheet.jsonRestricts editing and shows review-specific UI controls
Item-levelsystemReadOnly flag on the itemAll cells in that specific row are locked
Field-levelsystemReadOnlyFields array on the itemOnly the listed fields are locked; other fields in the row remain editable
Column-levelreadOnly property in column definitionAll cells in that column are locked regardless of item permissions
Formula columnsformula property set on columnCells are automatically read-only because values are calculated
Server render columnsserverRender property set on columnCells are read-only because content is rendered server-side
Task item-levelsystemTaskReadOnly flagAll task-specific cells in that task row are locked
Task field-levelsystemTaskReadOnlyFields arrayOnly the listed task fields are locked

System-Managed Fields

The following fields are always read-only because they are managed by Polarion:
FieldReason
authorSystem-managed creation metadata — set when the item is first created
resolutionControlled by workflow transitions — cannot be set directly from Risksheet
createdSystem-managed timestamp — set at creation time
updatedSystem-managed timestamp — set on every modification
typeWork item type is immutable after creation

System Fields Excluded During Paste Operations

When using the Insert Rows Below command to paste items from the clipboard, the following system fields are automatically excluded from the pasted data to ensure proper identity generation for new items:
FieldReason
systemItemIdNew items receive fresh IDs
systemReadOnlyPermissions are re-evaluated for new items
systemReadOnlyFieldsField-level permissions are re-evaluated
systemTaskReadOnlyFieldsTask permissions are re-evaluated

Reference Item Fields

NameTypeDefaultDescription
systemReferenceTypestringNoneIdentifies items that are external references from other projects or spaces in cross-project Risksheet configurations. Possible values: reference (read-only external item displayed with special indicators) or overwrite (local copy that allows modifications).
Right-click a referenced item (where systemReferenceType is reference) and select Overwrite Row Item from the context menu. This changes the value to overwrite, converting the item to a local copy that you can modify. This option requires refreshOnSave to be enabled (the default).

Review Workflow Fields

These bindings enable the review workflow features in the Risksheet grid. They are available when the reviews section is configured in risksheet.json.
NameTypeDefaultDescription
reviewsRenderedstringEmptyColumn binding that displays review status and approval information for work items. Shows formatted review entries including reviewer name, timestamp, and comment text. The display format depends on the configured reviewManager (CommentBased, ApprovalBased, or WorkItemBased).
reviewsAddstringEmptyColumn binding that provides UI controls to add new reviews or approvals to work items. When the review workflow is configured, this binding creates an interactive control in the grid row for initiating new review entries.

Review Manager Types

The reviews.reviewManager property determines which review strategy is used:
ValueBehavior
CommentBasedReviews are created as Polarion comments attached to the work item
ApprovalBasedReviews use Polarion’s native approval comment system with fixed title Approval comment
WorkItemBasedReviews are created as separate Polarion work items linked to the reviewed item via configured link roles

Complete Example

The following risksheet.json excerpt demonstrates how system fields interact with column configuration and permission settings:
{
  "readonly": false,
  "downstreamReadonly": true,
  "reviewer": false,
  "columns": [
    {
      "id": "ID",
      "header": "ID",
      "width": 80,
      "readOnly": true
    },
    {
      "id": "title",
      "header": "Failure Mode",
      "width": 200,
      "readOnly": false
    },
    {
      "id": "severity",
      "header": "Severity",
      "width": 80,
      "type": "rating:severity"
    },
    {
      "id": "rpn",
      "header": "RPN",
      "width": 80,
      "formula": "commonRpn"
    },
    {
      "id": "sysReq",
      "header": "System Requirement",
      "width": 150,
      "type": "itemLink",
      "readOnly": true
    }
  ],
  "reviews": {
    "reviewManager": "ApprovalBased"
  }
}
In this configuration:
  • readonly: false allows grid-level editing
  • downstreamReadonly: true prevents editing of linked items from other documents and blocks task creation for downstream items
  • The ID column is explicitly read-only via the column-level readOnly property
  • The rpn column is automatically read-only because it has a formula property
  • The sysReq column has a companion sysReq_link binding available via the _link suffix convention
  • Review columns (reviewsRendered, reviewsAdd) are implicitly available because reviews is configured
  • Items with systemReadOnly: true override all column-level settings and lock the entire row
  • Items with systemReferenceType: "reference" appear as read-only cross-project references with an Overwrite Row Item context menu option
Support TicketsSource Code
  • SystemConsts.java
  • SheetConstants.ts
  • AddTaskCommand.ts
  • RiskSheetContextMenu.ts
  • InsertRowsBelowCommand.ts