Skip to main content

Three Layers of Configuration

Think of the configuration hierarchy like CSS specificity — the most specific setting wins. Nextedy GANTT resolves every configurable property by checking three layers in order: diagram

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:
PropertyDefault Value
Default scaleW (Week view)
Progress coloringtrue
Drag childrentrue
Show today markertrue
Max items100
Start fieldgantt_start
Duration fieldgantt_duration
Progress fieldgantt_progress
Show unplannedtrue
Undo steps10

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 propertiesnextedy.gantt.<property> applies globally regardless of Gantt mode.
  • Work Items Gantt defaultsnextedy.gantt.workitems.default.<property> sets defaults for Work Items Gantt instances.
  • Plans Gantt defaultsnextedy.gantt.plans.default.<property> sets defaults for Plans Gantt instances.
For example, to make auto-scheduling default to enabled across all Work Items Gantt instances in a project:
nextedy.gantt.default.auto_scheduling=true
Or to change the default scale for all Work Items Gantt instances:
nextedy.gantt.workitems.default.scale=M
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:
PropertyScopePurpose
nextedy.gantt.default.auto_schedulingAdmin onlyToggle auto-scheduling default
nextedy.gantt.default.critical_pathAdmin onlyToggle critical path visualization default
nextedy.gantt.workitems.default.forward_dependencyAdmin onlyReverse dependency direction
nextedy.gantt.workitems.default_durationAdmin onlyDefault task duration in days (default: 10)
nextedy.gantt.workitems.default.link_lagAdmin onlyDefault dependency link lag (default: 0)
nextedy.gantt.workitems.resolved_readonlyAdmin onlyPrevent editing resolved items (default: true)
nextedy.gantt.teamManagementProjectIdAdmin onlyExternal team management project
nextedy.gantt.workitemCalendar.projectIdAdmin onlyWork item calendar project
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
This cascading visibility means you will not see advanced options until you enable the features they belong to.

Gantt Config Script and Item Script

Beyond the structured parameter system, Nextedy GANTT provides two scripting hooks for advanced customization:
  • Gantt Config Script — JavaScript executed once during chart initialization. Configures global chart behavior (colors, working hours, scale settings).
  • Item Script — JavaScript executed for each work item during data loading. Customizes individual task properties (colors, dates, read-only flags).
Scripts provide the most flexibility but bypass the standard configuration validation. They execute in addition to — not instead of — the configuration hierarchy.
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.
KB ArticlesSource Code
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/Config.java
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/impl/types/TypeConfigWidgetParameters.java
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/util/WidgetPropertiesAccess.java
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/js/config.js
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/columns/Table.java