Enable aktin.properties Configuration via UI

akomii commented 3 weeks ago

Currently, the configuration for aktin.properties must be edited directly on the server as a file, which can be time-consuming and requires server access. To improve usability and streamline the configuration process, it would be beneficial to enable aktin.properties settings to be configured directly from the UI.

Feature Request

Introduce a new settings section in the UI dedicated to configuring aktin.properties
Allow users to edit key fields
Provide a button to save changes (the new value are written to the aktin.properties file)
Provide a function to restart the wildfly server to apply the new settings

LongusBongus commented 2 weeks ago

Additionally we need to...

check if given value is valid
revert uncommitted changes and reload current settings
introduce a access system, so only admitted users can change properties
provide a way for IT personal to edit the file manually and let changes display in ui

LongusBongus commented 2 weeks ago

Here the first ideas:

Case 1: No according user rights mockup_no_permission

Case 2: Wrong input mockup_type_error

Case 3: Empty field mockup_null_error

Case 4: Correct changes and restart button mockup_restert

simhue commented 2 weeks ago

Questions:

If I have the necessary rights, is the configuration tab automatically in edit mode?

Remarks

in case of missing edit rights in case 1, a hint is obsolete imho. Any buttons and fields should just be hidden.
in case 1 radio buttons should be replaced by a simple text
error messages should be in german
Try to avoid negations in error messages, i.e. instead of "XY must not be empty", rather write "XY is required"
Avoid exclamation marks in messages to the user
I like the toast to display messages
Dedicated buttons for saving & rebooting, canceling and maybe just saving in case the user is not able to restart the server right away

LongusBongus commented 2 weeks ago

To answer the question, if a user without the correct permissions opens the page, he wont be shown editable fields. Instead he will get plain text elements.

New Mockup Case 1: No permission Mockup_no_rights

Case 2: Wrong Input Mockup_empty_error Mockup_type_error

Case 3: Changes Correct, save prompt Mockup_correct_changes

Case 4: Restart Server Request after saving changes Mockup_server_restart

simhue commented 2 weeks ago

I think there should be 2 views

first as readonly for everyone
second as editable view for people with elevated rights, after clicking a dedicated "Edit" button. Cancelling the edit would return the user to the readonly view. But this is up for debate.

Case 3: According to Material Design dismissive actions should always be to the left of confirming actions https://m3.material.io/components/dialogs/guidelines#befd7f4d-1029-4957-b1b5-da13fc0bbf3c

Edit: Try to keep the button labels short and concise, e.g. "Verwerfen" instead of "Änderungen verwerfen".

LongusBongus commented 5 days ago

Not editable view Visible_only

When trying to acess editing mode, but dont have the permission no_permission

Editing mode edit_mode

Editing mode with valid changed attributes correct_changes

Editing mode with unvalidated changes, here: Wrong input and no input wrong_input no_input

A flow chart, to demonstrate how the editing workflow should look like Ablauf drawio

simhue commented 5 days ago

Looks fine, but hide the edit button, when lacking edit rights

aktin / dwh-admin

Enable aktin.properties Configuration via UI #4