Problem:
As unfortunately not all states are displayed always property on the client side (which node is actively clicked in the tree view) and also the move operation via the mouse is not very precise this can lead to the following error:
A users tries to move a node in config app/workspace, but moves more nodes than expected, or into a wrong place.

As the config workspace is crucial for the system, one can easily break the while instance like this.
Accessing and operating on live in the content app is done for example when creating virtualURIMappings or any live ad-hoc needed changes.

Solution:
A property that can be set (for example in magnolia.properties) which declares that the system is a live system.
This has the result in the config app that:

• Any move operation needs a confirmation (as deletion).
  • All nodes that will be moved
  • The source path
  • The destination path