Thank you for taking this on, @grzesiek2010! The settings at the app level has been ready for some time and needs feedback before it can be integrated and released. To be clear, this is a first step and similar functionality will likely be added at the form and question level in the future. If someone wants to contribute that, it would be most welcome. The first step (and probably the most difficult one!) will be to make a proposal for how this would be indicated in the form.
For those who would like to see the code or try it out: https://github.com/opendatakit/collect/pull/1457
The current implementation adds a setting in the
User interface general settings menu:
This can be shown or hidden in the "user settings" part of administrator settings:
When it is unchecked, the user can only move forward in a form and not backwards.
Typically organizations will want to combine this with an administrator password. They will also want to hide the "edit saved forms" button from the main screen and the "go to prompt" button from form entry. This combination of settings will ensure that users can only open a form once and can only navigate forward in it.
It's not clear to me that this setting is useful without an administrator password. That is, if an enumerator sets Collect not to allow going backwards, they can always change it again to allow it. I think it might make more sense to only allow the administrator to enable or disable going backwards, just like with the goto prompt. This would mean adding a single setting in the "form entry settings" section of administrator settings.
What do others think? @Nikhil_Patil @Dr_Jaideep_Gupte @Gunn777