Configuration Editor - Nextedy Documentation

What scopes does the configuration editor support?

The built-in configuration editor supports three scopes for managing configuration files:

Scope	Description
`instance`	Per-instance override for a specific document
`template`	Template-level configuration shared across documents
`default`	Global defaults applied when no override exists

The scope control can be ENABLED, DISALLOWED, or DISABLED depending on your permissions and the current editing context.

Does the editor support JSON Schema validation?

Yes. The configuration editor can attach a JSON Schema to validate your YAML content as you type. This provides real-time feedback on configuration errors, missing required fields, and invalid property values. The schema is auto-generated from the data model definition, ensuring that your configuration references valid Polarion prototypes and entity types.

Can I switch between YAML and JSON in the editor?

The editor supports both YAML and JSON as configuration languages. You can switch between them, and the content is automatically converted when you change the language setting. By default, the editor uses YAML (lang: yaml). Your language preference is saved in your browser and persists across sessions.

Verify in applicationAdditional editor features such as line wrapping and keyboard mode preferences are available in the editor toolbar.