Configuration environments in the Config Editor

An instance's Config Editor displays the "Environments" drop-down after enabling the feature for the instance:

• Marks the environment of the instance the config editor is running on (instance environment)
• "Shared - all environments" marks the configuration shared among all environments
• The Config Editor always shows the values for the selected environment

To "create" a new environment, use the "Environments" drop-down item "- Add environment -".

To define an environment-specific value the environment:

1. Select the environment in the "Environments" drop-down
2. Select the plugin to be edited (via a plugin tree, search result or error list)
3. Define the environment-specific value for the selected environment by overriding the current value clicking on 

All properties with environment-specific values for the selected environment can be reviewed in the "Env Properties" Panel.

Click on an entry to open the corresponding plugin:

By the default an exported configuration contains the values for all environments (and can therefore be applied as is to all other instances).

In some situations it is not suitable to export all environments' values.

For example:

• do not expose productive configuration information to a tester debugging a problem
• you may not want any values from the "test" environment in your live systems (even if they are not used there)

Select option "Export with values for specific environment(s)" to do so:

Using Ctrl + Left Mouse Button any subset of the environment(s) can be selected.

In the above example all plugins and properties that are relevant for the Production environment are NOT included in the exported configuration.

As the warning in the dialog hints, this process is not reversible: A derived configuration can NOT be imported back into the configuration it was derived from.