Atm this takes the user via the available forms list, where only the Reg form is selectable.. A direct route to the form save the user time and cognitive effort.. -> This will be addressed here: https://github.com/akvo/akvo-flow-mobile/issues/1790
This also relates to editing an existing datapoint; on selecting an editable datapoint, Alph should be taken right back to the Reg form and spared the form(s) list detour.
This means that if possible, opening an editable datapoint should ideally take the user to the QG they were working on before exiting.. (but this might be a thought for another day
why is this important
This would also mean removing the redundant Reg form and its version info from the Forms tab for a created datapoint; it is redundant since the user cannot do anything with it - it is disabled. Besides the "registration form name and version" are also presented in the History tab, where they are close to the assumed context of seeing what version number was used to register the data (if any)
This will be the fundamental step into datapoint profile as it would be the first place were we indicate that first you create "a thing" and then you view or monitor it; not first you see how you may monitor "the thing" even before you create it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
whats this about
Atm this takes the user via the available forms list, where only the Reg form is selectable.. A direct route to the form save the user time and cognitive effort.. -> This will be addressed here: https://github.com/akvo/akvo-flow-mobile/issues/1790
This also relates to editing an existing datapoint; on selecting an editable datapoint, Alph should be taken right back to the Reg form and spared the form(s) list detour.
This means that if possible, opening an editable datapoint should ideally take the user to the QG they were working on before exiting.. (but this might be a thought for another day
why is this important
This would also mean removing the redundant Reg form and its version info from the Forms tab for a created datapoint; it is redundant since the user cannot do anything with it - it is disabled. Besides the "registration form name and version" are also presented in the History tab, where they are close to the assumed context of seeing what version number was used to register the data (if any)
This will be the fundamental step into datapoint profile as it would be the first place were we indicate that first you create "a thing" and then you view or monitor it; not first you see how you may monitor "the thing" even before you create it.