Entity Master: button SAVE to provide a visual cue in a case of errors

[01es]

Description

Validation results are always associated with some entity property, which in turn get displayed as toast messages and as errors, warnings, or informative messages underneath corresponding property editors.

However, there are cases where more computationally intensive validations take place upon companion object's save. If such validations result in errors or in case of some other errors, only a toast message gets displayed to users. And a toast message vanishes relatively quickly, potentially leaving users guessing as to what has just happened, if they got interrupted and did not see the toast.

In order to improve this situation, it is proposed to change the background colour of button SAVE to red and text to white (i.e., to have the same aesthetics as for the error toast). This is to provide a visual cue to users that their attempt to SAVE changes did not succeed.

There is no need to make SAVE red in case of validation errors that happen upon entity validation lifecycle - only in case of errors upon save. This also means that after an unsuccessful save, potentially due to an unresolved property validation error, button SAVE should become red. But as soon as the user changes some property values, button SAVE should assume its non-erroneous state (green for change and white in case of no change).

Expected outcome

Improved indication of errors upon saving changes/running actions.