KIX 18 Practice
UI configuration 2.0
With the KIX Pro version 18.18, a new module will be available that supports the editing of the UI configuration in a visualized manner.
Up to now it was necessary to look for the individual keys in the flat structure of the Sys-Config and then to edit the complex value - mostly with the help of an external editor. To do this, you had to know the structure, structure and relationships of the UI configuration. Not anymore!
In the new module, the UI configurations are now sorted hierarchically in a tree and the value can also be edited using the JSON editor.
The tree has three basic root nodes:
- List of all context configurations, grouped according to their context type (e.g. dashboard, details, ...)
- List of configured widgets for the context grouped according to their area of application
- List of all form configurations, grouped by form context
Not referenced configurations
- List of all configurations that are not assigned in context or form
- Other application configurations (e.g. ticket-details-print-config)
The nodes of the tree are enriched with metadata so that the tree can be specifically filtered:
- according to configuration type (all form fields)
- to "ticket details" (all configurations belonging to ticket details)
- after "modified" (all changed configurations)
A JSON editor is now used to display and edit the configuration value.
This offers useful features:
- format JSON
- collapse JSON
- undo / redo
Save: saves the value in the Sys-Config key
Cancel: resets the changes to the value of the saved Sys-Config key
Reset to Default: resets the value to the default value of the Sys-Config key
Show Default Value: Display of the default value, which is stored in the Sys-Config definition (blue = processed value, green = default value)
Corresponding JSON schemes are stored for some basic configurations, which the JSON editor uses to validate the JSON.
Application of changes
If you have adjusted the desired configurations, they are not directly active. The front-end cache must first be rebuilt. There is also the action "Reload Frontend Configuration" known from Sys-Config. After this has been carried out, the configuration tree is also rebuilt in the UI on the basis of the new cache.