-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
6.3.0
-
None
Steps to reproduce
- start the cloud instance with -Dlock.config.workspace=true
- open the configuration app
- edit a field using the inline editor
- confirm the change
Expected results
An error should occur saying that the node is locked.
Actual results
No visual feedback that the update cannot occur.
Workaround
Development notes
The value in the backend and in the frontend remain unchanged, as it should.
Acceptance criteria