dhis2-devs team mailing list archive

[Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>]

Hello devs,

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?


-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!