Make default Server Settings more robust

Who would benefit?

Any Control Center user, as well as any business stakeholder who wants to reduce risk

What impact would it make?

Improvement suggestion: Divide editing of settings in two parts: one for built-in settings and one for custom settings. For the custom settings, the same grid as today might be used (initially). The first obvious advantage with this is to highlight which settings are managed by inriver.

The reason for this dividing is that there are certain properties of built-in settings which would gain from special treatment.

How should it work?

Properties of built-in settings:

• Should not be able to change the name (key)

• Should not be able to delete

• Can be of different datatypes. For datatypes other than plain text, different UI objects should be used for editing. Examples: yes/no values, true/false values, single or multiple choice from a set of values, numeric values, CHANNEL_FILTER should be treated in a specially designed page with validation and support for making choices

• Validation should be performed to avoid invalid values

• An information text should be available (as tooltip, info-symbol or similar) to inform about use and possible values

Why is it needed?

Reduce risk and increase user friendliness