JOC Cockpit should consider a failed store operation in the Configuration Editor

Current Situation

Currently the Configuration Editor stores changes automatically.

• If such a store operation fails, then JOC Cockpit receives an HTTP 420 status code, but does not take the occurrence of the error into account when the user leaves the editor.
• JOC Cockpit still assumes that the configuration was stored while the current state of the configuration has not been persisted.
• Addtionally, JOC Cockpit vaildates the current status of the configuration from memory and shows the outcome of validation on top of the editor.
  • While the current status of the configuration (from memory) might be valid and displayed, the persisted object in the database may not be valid, because of the failed store operation.
  • The deploy button shown on top of the editor is subsequently active and a user gets the impression that the current status is deployable.
  • Trying to deploy the current persistant status of the configuration will result in the next error.

Desired Behavior

• JOC Cockpit should recognize the occurence of a failed store operation and should not assume that the configuration was stored and persisted successfully in case of an error.
• It should be clear to the user that the current status of the configuration visible in the editor is not persisted yet and cannot be deployed.