You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A "save" symbol is prominently located in each form's title bar.
Some of our users confused this for a "save and send" button. This led to data being stuck on devices until rediscovered during training for the next season.
In the same vein, "mark as finalized" means far less to the occasional user (not fluent with ODK technical terms) than "ready to upload" (="mark as finalized") or "request review" (=untick mark as finalized). I'm sure other ODK admins will find other phrases that are more meaningful to their use case.
Also, the tick box could be a bit further away from the "Save form and exit" button.
Expected behavior
A system setting should allow to toggle the visibility of the "save" symbol in the form title bar.
A possible layout for the final screen could be:
One button "Save and send" (marks as finalized and closes form)
One button "Save and request review" (marks as not finalized and closes form)
This is just an observation based on feedback I got from my ODK admins, not a breaking bug.
The text was updated successfully, but these errors were encountered:
Problem description
A "save" symbol is prominently located in each form's title bar.
Some of our users confused this for a "save and send" button. This led to data being stuck on devices until rediscovered during training for the next season.
In the same vein, "mark as finalized" means far less to the occasional user (not fluent with ODK technical terms) than "ready to upload" (="mark as finalized") or "request review" (=untick mark as finalized). I'm sure other ODK admins will find other phrases that are more meaningful to their use case.
Also, the tick box could be a bit further away from the "Save form and exit" button.
Expected behavior
A system setting should allow to toggle the visibility of the "save" symbol in the form title bar.
A possible layout for the final screen could be:
This is just an observation based on feedback I got from my ODK admins, not a breaking bug.
The text was updated successfully, but these errors were encountered: