### Current state 

When configuring a file storage, we persist those new storages after each step of the form. This results in incomplete and erroneous storage objects in the database. Validation on the storage object is more difficult, as data can cause failures, which was already entered in the past and forgotten. The completeness of a storage is only derived from the presence of certain configuration data, not from the conscious user decision of clicking on "Done, complete setup".

### Goal

We want to Begin of the insertionredesignEnd of the insertion Begin of the deletion reworkEnd of the deletion the storage configuration forms to work like this:

* If the user clicks on "Done, complete setup" a full validation of the whole storage form data is done before persisting the storage object in the database. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Every storage object in the database is considered a configured storage. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Canceling the storage form does not leave a non-functional storage. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * A warning could be useful then, that on cancel the user looses the not submitted data. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * The multi-step configuration UI will be kept with this approach. Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion ### Motivation

* The contracts can be more strict about which data needs to be present. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * The handling of the storage lists to filter for incomplete storages will get reduced in complexity. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * The danger of having inconsistent or incomplete data in the database is reduced. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * The final validation can almost ensure, that a storage works for later usage in the projects. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Inserting confirmation and error dialogs into the form is easier, as they can work very specific on the storage form not on a storage object (which can have too many states right now).