Manage Global Configuration - Nextedy Documentation

Prerequisites

Administrator access to the Polarion server
SVN access to the global repository (.polarion directory at repository root)
Familiarity with YAML syntax and Powersheet sheet configuration concepts

Understand the Configuration Hierarchy

Powersheet resolves configuration at three levels. Global configuration provides defaults that project-level and document-level settings can override.

-- Locate the Global Configuration Directory

Global configuration is stored in the SVN repository root, not inside any individual project. Access it via the Polarion administration UI or directly through SVN.Via Polarion UI:

Navigate to Administration > Nextedy Powersheet
Open the Global Settings section
Review the data models and sheet configurations listed

Via SVN:The global configuration resides at the repository root level:

<svn-root>/
  .polarion/
    nextedy/
      models/               # Global data models
        default_model.yaml
      sheet-configurations/  # Global sheet configurations
        default_sheet.yaml

The global .polarion/nextedy/ directory must be at the SVN repository root, not inside a project folder. Placing it inside a project makes it a project-level configuration, not a global one.

-- Edit the Global Data Model

The global data model defines entity types and relationships available to all projects that do not declare their own model.

Check out the repository root via SVN:

svn checkout https://your-polarion-server/svn/ --depth immediates
svn update .polarion/nextedy/models/ --set-depth infinity

Open the global data model YAML file and edit the entity types:

# .polarion/nextedy/models/default_model.yaml
domainModelTypes:
  - name: UserNeed
    polarionType: requirement
    prefix: UN
    icon: requirement

  - name: SystemRequirement
    polarionType: requirement
    prefix: SR
    icon: requirement

  - name: DesignRequirement
    polarionType: requirement
    prefix: DR
    icon: requirement

  - name: Hazard
    polarionType: hazard
    prefix: HZ
    icon: risk

  - name: RiskControl
    polarionType: riskControl
    prefix: RC
    icon: shield

relationships:
  - name: systemRequirements
    from: UserNeed
    to: SystemRequirement
    linkRole: relates_to
    cardinality: oneToMany
    direct: systemRequirements
    back: userNeeds

Save and commit:

svn commit -m "Update global data model"

Define entity type names in PascalCase (e.g., UserNeed, SystemRequirement). This convention keeps binding paths readable across sheet configurations and expansion paths.

-- Edit the Global Sheet Configuration

Global sheet configurations define default column layouts available across all projects.

Open the global sheet configuration file:

# .polarion/nextedy/sheet-configurations/default_sheet.yaml
columns:
  - key: id
    header: ID
    width: 80
    isReadOnly: true

  - key: title
    header: Title
    width: 300

  - key: status
    header: Status
    width: 120
    isReadOnly: true

  - key: severity
    header: Severity
    width: 100

views:
  - name: Default
    visibleColumns:
      - id
      - title
      - status

  - name: Full Detail
    visibleColumns:
      - id
      - title
      - status
      - severity

Adjust columns, widths, and views as needed for your organization’s defaults.
Commit via SVN.

The exact set of global sheet configuration properties may vary by Powersheet version. Test your changes in a non-production environment first.

-- Override Global Settings at Project Level

When a project needs different behavior, create a project-level configuration that overrides the global one.

Navigate to the project’s SVN directory:

&lt;svn-root&gt;/&lt;ProjectGroup&gt;/&lt;ProjectId&gt;/.polarion/nextedy/

Create or edit the model and sheet configuration files inside the project’s .polarion/nextedy/ directory.
Any entity types, relationships, or columns defined at the project level replace the corresponding global definitions for that project.

Scope	Location	Applies to
Global	`<svn-root>/.polarion/nextedy/`	All projects without their own config
Project	`<project>/.polarion/nextedy/`	Single project only
Document	Widget parameters in LiveDoc	Single document only

-- Validate and Reload

After committing global configuration changes:

Trigger a reload --- In Polarion, navigate to Administration > Nextedy Powersheet and click Reload Configuration (or restart the Polarion service if no reload button is available).
Verify in a project --- Open a project that relies on global configuration. Open a sheet and confirm:
- Entity types from the global data model appear in expansion paths
- Global columns display with the expected headers and widths
- Views defined globally are selectable in the sheet toolbar
Check for conflicts --- If a project has its own configuration, verify that the project-level settings take precedence as expected.

Polarion may cache configuration from SVN. If changes do not appear after committing, perform a server-side cache refresh or restart the Polarion service.

Common Pitfalls

If a project defines its own data model, the global model is not merged --- it is replaced entirely. Ensure project-level models include all entity types the project needs, even those that were inherited from the global model.

When checking out the repository root, use --depth immediates to avoid downloading all project data. Then selectively deepen only the .polarion/nextedy/ directory.

Since all configuration lives in SVN, you get full version history automatically. Use meaningful commit messages to track why changes were made, making it easy to roll back if a configuration change causes issues.

Verification

You should now see:

Global data model entity types available in any project that does not define its own model
Global sheet configuration columns and views appearing as defaults in sheets across your Polarion instance
Project-level overrides correctly replacing global settings where defined

​Prerequisites

​Understand the Configuration Hierarchy

​Common Pitfalls

​Verification

​See Also

Prerequisites

Understand the Configuration Hierarchy

Common Pitfalls

Verification

See Also