Closed iperdomo closed 4 years ago
Ideally, we should autosave everything in Flow, for each change not just for creating new things (like for editing questions, or cascades) but we do not. If we had autosave, we could remove the save
button and do what Lumen does and just show when things are being saved.
How much effort would autosave require?
To keep things consistent with other Flow 'not-so-user-friendly-workflows' when leaving the page, it should mean the changes do not get saved. This is not ideal but it is how other parts of Flow work.
How much effort would autosave require?
As you pointed out, we need to make it consistent across the Dashboard, so a "project" itself. Meaning, no trivial. Autosave has come before I mentioned to @muloem that if we want/need autosave, IMHO we also need/want "Undo", meaning a way to rollback what the user did and we saved.
To keep things consistent with other Flow 'not-so-user-friendly-workflows' when leaving the page, it should mean the changes do not get saved. This is not ideal but it is how other parts of Flow work.
It seems this is an old behaviour - https://github.com/akvo/akvo-flow/issues/1223
Duplicate of #1223
Context
There is no UI to cancel the current editing assignment. If the user moves away to a different tab. We detect that the Assignment has been changed and we attempt to autosave it, leading to a "Missing required parameters" message.
Problem or idea
Attempt to autosave the edits in an Assigment.
Solution or next step