I think it is a great idea to review this page as you said.
I had witnessed situations where collectors for more than one year had not been submitting forms to the server because they taught after clicking on mark as finalized, the form was sent to the server automatically and no one noticed that until review. Luckily for that situation, the finalized forms were still all in the phone.
The default configuration when configuring from Central QR code is to auto-send on finalization and that's generally what we recommend. We have not changed the default for other configurations for continuity but maybe that's something to consider. Would you be up for a conversation about finalization more broadly?
If you're not using Central, you have a few options to turn on auto-send:
I wanted data collector to finalized form as soon as the form was filled because:
There is constraint-check when finalized form. Despite there is within page constraint-check when navigate from page-to-page, but hierarchical navigation could actually bypass the check. Hence, to ensure near-time correction can be made, the form has to be finalized soon after completion.
If data collector wants to finalize it, check it otherwise save form for later use. The saved form shall be always editable.
Sometimes, data collector finalized form but edit it again. This approach is not encouraged as 'finalized' means no more editing. I do have the 'auto-send' turned on by default. Hence, during offline mode, the data collector might still be able to edit the finalized form before it is sent. To me, finalized form is a container that place the form which are ready to send when there is internet connectivity.
Should I consider finalizing form only when accessibility to internet connectivity is certain?
Sometimes, the connectivity is weak in the outdoor. It is worrisome when the finalized form stalled to send during connectivity is cut-off and not continuing to send after re-gain the internet connectivity. If there was no one do a check whether form was successfully sent, it will be too late to discover one day. I have reservation on the app whether it is robust to ensure all finalized form and its attachments could send completely without further intervention. What is the mechanism behind that enable it?
In my case, the instance name of form is set by the form definition. Data collector do not require to specify it.
Thanks for the feedback. We really appreciate you taking the time to share your experiences, as this will help inform the next iteration of the designs!
I'm curious to hear more about point #3 and why the data collectors are editing once the form is finalized. Could you tell us why they are coming back and editing the form? Are they opening the form to save it or to make edits because they learnt something new?