We were looking at certain optimizations for the look and feel of the DHIS web app in terms of usability. We were particularly looking at the "Complete/Incomplete” and the “Validate” buttons.
We are not sure of the intended relevance of using the word “Complete", if what we are doing is a simple save. Initially we guess that Complete and Incomplete are supposed to indicate the status of the data, i.e. Complete indicates the data is saved, ready to be synced, and locked from further changes; whereas Incomplete indicates the data is ready to be updated/changed.
However, looking at the code and the changes in the DB it seems that on “Complete”, and even when not pressing complete, the values typed into the form are added to the “datavalue” table. In the case of the user clicking “Complete" we also add an entry in the “completedatasetregistration” table.
We were thinking of customizing this behavior (leveraging the custom js post) by having a single “Save” button. This button will be overloaded with the "update” behavior inherent in the Incomplete button, with a prompt asking for a confirmation in case a value is changed. (e.g. “Are you sure you want to change these values?”)
The Save button would also be overloaded with the Validation functionality, where clicking Save would generate running the Validate command.
Does this sound right? Or there is something that we are missing here?
On a related note, in the DHIS Android Event Capture app, there are again “Complete” and “Validate” buttons. On saving the event the status changes to “Incomplete”. This seems like confusing user experience. Any thoughts?
Data is sent to the the datavalue table as soon as the user leaves each and every single field, in other words, there is no need for a Save button, since everyting is already saved. The purpose of the Complete button is to indicate that you don’t have any more additions or changes to make.
Also, you can configure a group of users to receive a notification upon completeness:
Complete notification recipients: Sets which users should receive a message with a notification about this data set being marked as complete in data entry. In this list you can select a user group, and all members in this group will receive a notification. The message will be delivered through the DHIS messaging system.
We were looking at certain optimizations for the look and feel of the DHIS web app in terms of usability. We were particularly looking at the "Complete/Incomplete” and the “Validate” buttons.
We are not sure of the intended relevance of using the word “Complete", if what we are doing is a simple save. Initially we guess that Complete and Incomplete are supposed to indicate the status of the data, i.e. Complete indicates the data is saved, ready to be synced, and locked from further changes; whereas Incomplete indicates the data is ready to be updated/changed.
However, looking at the code and the changes in the DB it seems that on “Complete”, and even when not pressing complete, the values typed into the form are added to the “datavalue” table. In the case of the user clicking “Complete" we also add an entry in the “completedatasetregistration” table.
We were thinking of customizing this behavior (leveraging the custom js post) by having a single “Save” button. This button will be overloaded with the "update” behavior inherent in the Incomplete button, with a prompt asking for a confirmation in case a value is changed. (e.g. “Are you sure you want to change these values?”)
The Save button would also be overloaded with the Validation functionality, where clicking Save would generate running the Validate command.
Does this sound right? Or there is something that we are missing here?
On a related note, in the DHIS Android Event Capture app, there are again “Complete” and “Validate” buttons. On saving the event the status changes to “Incomplete”. This seems like confusing user experience. Any thoughts?