Three Layers of Configuration
Think of the configuration hierarchy like CSS specificity — the most specific setting wins. Gantt resolves every configurable property by checking three layers in order:
Layer 1: Built-in Defaults
Every configurable property has a hardcoded default value. These defaults provide a working Gantt chart out of the box without any configuration. Key defaults include:Layer 2: Administration Properties
Administrators can override defaults system-wide or per-project by setting Configuration Properties in Polarion’s administration console (Administration > Configuration Properties). These properties follow a naming convention:- General properties —
nextedy.gantt.<property>applies globally regardless of Gantt mode. - Work Items Gantt defaults —
nextedy.gantt.workitems.default.<property>sets defaults for Work Items Gantt instances. - Plans Gantt defaults —
nextedy.gantt.plans.default.<property>sets defaults for Plans Gantt instances.
Administration property defaults are used as the initial value when you add a new Gantt chart to a page. Once the chart is placed, its own parameter values take precedence. Changing an administration default does not retroactively update existing charts that already have explicit values set.
Layer 3: Per-Instance Parameters
Per-instance parameters are set directly on each Gantt chart through the Polarion wiki page editor. They represent the most specific level of configuration and always take precedence when set. These parameters are organized into sections in the configuration panel:- Data set — which work items or plans to display
- Data Mapping — field mappings for start, end, duration, progress
- Work Item Types — presentation modes, parent rules, create-new settings
- Resource View — resource field, load mode, allocation colors
- Working Calendars — global calendar, user calendars, team assignments
- Advanced — scripts, read-only mode, always-edit, toolbar visibility
Properties That Only Exist at One Level
Some configuration properties exist only as administration properties and cannot be set per instance:
Conversely, certain settings are only available as per-instance parameters because they are inherently instance-specific (e.g., the data set query, scripts, sidebar fields).
Progressive Disclosure in the Configuration Panel
The parameter editor uses progressive disclosure to reduce complexity. Sub-parameters are only visible when their parent feature is enabled:- Load User Calendars appears only when Use Working Calendar is enabled
- Load Team Assignments appears only when Load User Calendars is enabled
- Deadline Field and Passed Deadline Color appear only when Show Deadlines is enabled
- Compare to date appears only when Show Baselines is enabled
Gantt Config Script and Item Script
Beyond the structured parameter system, Gantt provides scripting hooks for advanced customization. The two that interact with configuration are:- Gantt Config Script — client-side JavaScript executed once during chart initialization. Configures global chart behavior (colors, working hours, scale settings).
- Item Script — server-side JavaScript executed for each work item during data loading. Customizes individual task properties (colors, dates, read-only flags).
Read-Only Mode Has Three Sources
Read-Only Mode Has Three Sources
A Gantt chart can become read-only from three different sources: (1) the
readonly parameter is set to true, (2) the current user is not licensed, or (3) a Polarion baseline snapshot is active. All three conditions are checked independently and any one will trigger read-only mode.Related Pages
- Architecture and Data Flow — how configuration flows from server to client
- User Settings and Local Storage Persistence — how per-user preferences layer on top
- Data Mapping and Field Resolution — the field mapping subset of configuration