- form name comes from the document portal type action
- for now, path to action is hardcoded. It will come from a allDocs query (not implemented yet in appcachestorage sync)

- new parameter added for this scenario

- the test failed the same with both attempts

- even is it committed, test fails due to "can't get manifest"

- attempt to fix test

- this new parameter disable permission check when hateoas is called by bootloader
- appcache storage sync is canceled if storage requires authentication
- WIP: redirect to login not working

- needed to get the form definition from hateoas script

- new appcachestorage hash layer is created when new storage is selected

- editable view is generic enough for form editing, so it will be kept
- but submit handling is done in controller gadget

- configurations like form definitions are saved as objects into data-storage.metadata to allow jio.get

- this prevents the appcache-local storage sync to store unnecessary resources like gadgets