Hi Harm,
I assume you left "auto-save” of in this case?
We hear this question more often. For us this is a doubtable combination of settings from UX perspective.
As a developer you allow the user to directly start typing, but the changes should be saved or canceled manually. It may be feeling strange to the user if the interface blocks itself completely after the first character is typed. For a fast user he/she would probably already be focusing on the active tab page or task button, where the action is blocked while clicking on it.
Long story short, our advice is to enable auto-saving too. Is this an option for you?
Best regards,
Erik
Erik,
It is not that easy it will also depend on the kind of data.
In case of master data objects the user must always be aware that he/she has made changes to the data.
At this moment users cannot see whether a form is in edit mode and do not understand why details are disabled.
For now, I think it is better and more clear for users to not enable auto edit and auto save.
I hope you can find options to make the behavior of the Universal GUI more efficient and intuitive.
Best regards,
Harm