Configuration Property
| Property | Type | Default | Description |
|---|
global.culture | string | en | Defines the culture/locale for the Risksheet interface, affecting date formats, number formats, and localization |
Setting the Culture
Configure the culture in the sheet configuration file (risksheet.json) under the global object:
How Culture Affects the Grid
The global.culture value is applied to the client-side grid renderer. It changes how cell values are formatted on display (dates, numbers, separators), but it does not change how data is stored in Polarion. Picking the closest culture for your team standardizes how risk records read across locales.
Supported Culture Codes
The Risksheet release supports exactly the following 18 culture codes. Use the code as-is in global.culture.
| Code | Language / Region |
|---|
ar-AE | Arabic (United Arab Emirates) |
zh | Chinese |
zh-HK | Chinese (Hong Kong) |
zh-TW | Chinese (Taiwan) |
en | English |
en-CA | English (Canada) |
en-GB | English (United Kingdom) |
fr | French |
fr-CA | French (Canada) |
de | German |
he | Hebrew |
hi | Hindi |
ja | Japanese |
ko | Korean |
pt | Portuguese |
ru | Russian |
es | Spanish |
tr | Turkish |
| Format | Example | Description |
|---|
ll | en, de, fr | Primary language code (ISO 639-1) |
ll-CC | en-GB, fr-CA | Language with country/region (ISO 3166-1 alpha-2) |
Use the primary language code (e.g., de) for the default regional variant. Use a regional code (e.g., en-GB) only when you need a specific regional format that differs from the language default.
Interaction with Polarion Locale
The Risksheet global.culture setting operates independently from Polarion’s server-level locale configuration. The Risksheet culture affects only the grid rendering, not the underlying Polarion data storage format. Dates and numbers are stored in Polarion’s internal format regardless of the display culture.
| Property | Type | Default | Description |
|---|
global | object | {} | Global Risksheet settings including culture/locale, help URL, refresh behavior, and menu organization |
headers.columnHeader.height | number | 32 | Height in pixels for column headers |
headers.columnGroupHeader.height | number | 32 | Height in pixels for column group headers |
Complete Example
A German-locale FMEA (Failure Mode and Effects Analysis) sheet configuration using German-language column headers:
global:
culture: de
headers:
columnHeader:
height: 32
columnGroupHeader:
height: 32
columns:
- id: riskId
header: ID
bindings: id
readOnly: true
- id: failureMode
header: Fehlerart
bindings: title
- id: severity
header: Bedeutung (B)
bindings: severity
type: rating
- id: occurrence
header: Auftreten (A)
bindings: occurrence
type: rating
- id: detection
header: Entdeckung (E)
bindings: detection
type: rating
- id: rpn
header: RPZ
formula: commonRpn
- id: dueDate
header: Faelligkeitsdatum
bindings: dueDate
type: date
formulas:
commonRpn: "function(info){ var value = info.item['occurrence']*info.item['detection']*info.item['severity']; return value?value:null;}"
culture: de:
- The
dueDate column displays dates as DD.MM.YYYY (e.g., 15.03.2025)
- The RPN (Risk Priority Number) column (
RPZ) formats numbers with German locale conventions (comma as decimal separator)
- Column headers use German terminology (
Bedeutung, Auftreten, Entdeckung)
Related Pages
