Skip to main content

​
Field Types and Configuration

Field Mapping — Understand how RISKSHEET binds Polarion fields to columns, including nested field access, custom field references, and field type inference. Supported Field Types — Complete reference of Polarion field types that RISKSHEET can display and edit, including native types and custom field extensions. Lightbox Fields — Configure and display lightbox fields for work item selection, editing, and rich property access in RISKSHEET columns. System Fields — Reference for Polarion system fields (id, status, type, project, created, updated, etc.) and their read-only behavior in RISKSHEET.

​
Field Type Decision Matrix

Data NeedField TypeColumn Type
Single text value (titles, descriptions)String fieldCustom field type
Enumeration selection (status, category)Enum fieldCustom field type
Work item reference (linked risk, document)Lightbox or Link fieldSpecial type
User assignment (assignee, reviewer)User fieldSpecial type
Numeric values (ratings, counts)Integer/Decimal fieldCustom field type
Date tracking (milestones, deadlines)Date/DateTime fieldCustom field type

​
Common Field Patterns in Risk Management

​
Risk Item Fields (FMEA/HARA)

FieldTypePurposeExample
Risk IDString (read-only)Unique identifier”RISK-001”
Risk TitleStringRisk description”Power supply failure”
SeverityEnum (1-5)Risk impact level”5 - Critical”
OccurrenceEnum (1-5)Probability of occurrence”3 - Medium”
DetectionEnum (1-5)Ability to detect”2 - Low”
RPNCalculated (read-only)Risk priority number75 (5×3×2)
MitigationString/LightboxLinked mitigation actionLink to task
StatusEnum (read-only)Workflow state”Open”, “Closed”
Assigned ToUserOwneruser@example.com

​
Mitigation/Task Fields

FieldTypePurposeExample
Task IDString (read-only)Unique identifier”TASK-001”
TitleStringAction description”Implement backup”
PriorityEnumAction urgency”High”
Due DateDateTarget completion2026-03-15
Assigned ToUserResponsible personjohn.doe@company.com
StatusEnum (read-only)Progress state”In Progress”
Linked RiskLightbox (read-only)Parent riskLink to risk

​
Field Binding Syntax

FIELDS are referenced in column configuration using binding paths:

​
Direct Field References

{
  "binding": "title",
  "binding": "description",
  "binding": "status"
}

​
Custom Field References

{
  "binding": "customFields/riskSeverity",
  "binding": "customFields/mitigationStatus"
}

​
Nested Field References (Linked Items)

{
  "binding": "linkedRisk.title",
  "binding": "linkedRisk.customFields/severity",
  "binding": "relatedTask.assignee"
}

​
System Field References

{
  "binding": "id",
  "binding": "created",
  "binding": "updated",
  "binding": "author"
}

​
Field Types at a Glance

CategoryField TypeEditablePurpose
IdentificationString, IDVariesUnique identifiers, titles
EnumerationEnum, Multi-EnumYesSelection from predefined options
ReferenceLightbox, LinkYesLinks to other work items
NumericInteger, Decimal, CurrencyYesNumerical data, calculations
TemporalDate, DateTime, TimeYesTime-based tracking
TextString, Text, RichTextYesFree-form text content
UserUser, AssigneeYesPerson assignments
SystemID, Status, Type, ProjectRead-onlyBuilt-in Polarion fields
MetadataCreated, Updated, AuthorRead-onlyAutomatic tracking fields

​
Field Configuration Best Practices

​
1. Preserve System Fields as Read-Only

System fields (id, status, type, project, created, updated) should always remain read-only in your configuration: 
{
  "header": "Risk ID",
  "binding": "id",
  "readOnly": true
}

​
2. Use Custom Fields for Risk Management Data

Create custom fields for FMEA/HARA-specific data: 
{
  "binding": "customFields/riskSeverity",
  "type": "enum:severity_enum_id"
}

​
3. Handle Linked Items with Lightbox Fields

For linking to other work items, use lightbox fields: 
{
  "binding": "mitigationTask",
  "type": "lightbox:taskId"
}

​
4. Map User Assignment Properly

User fields require special configuration: 
{
  "binding": "assignee",
  "type": "user"
}

​
Field Display Formats

Different field types have specific display format options:

​
Enum Fields

OptionEffect
Show IDDisplays enumeration ID
Show NameDisplays human-readable name
Show DescriptionIncludes detailed description

​
Date Fields

FormatExample
Default locale2/12/2026 (US) or 12.02.2026 (DE)
ISO 86012026-02-12
Custom format12 Feb 2026

​
Numeric Fields

TypeFormat
Integer75, 1000, -5
Decimal75.5, 1000.25
Currency$75.00, €1000,50
Rating⭐⭐⭐⭐⭐ (1-5 visual)

​
Field Permissions and Read-Only Status

Fields automatically become read-only when:
  1. System field protection — id, status, type, project, outlineNumber
  2. Calculated field — formula property set
  3. Server-rendered — serverRender property set
  4. User permission denied — User lacks edit permission in Polarion
  5. Explicit configuration — readOnly: true in column definition
Source Code
  • AppConfig.ts
  • GetSetUtil.java
  • TextEditor.ts
  • SystemConsts.java