1

Resolved

Don't clear values in most disabled fields

description

The following behavior is mostly already present in the long form for sections 3 and 4, and is needed in the short form for sectios 3, 4, and 7, and in the long form for section 7. For form sections 3 (hospitalization), 4 (epi risk factors), and 7 (patient outcome), there are many fields that are enabled or disabled based on the initial answer (yes/no) to a particular question. If yes is checked, corresponding fields are then filled out, and then yes is cleared or no is checked, we do not want to the already filled out fields to be cleared, only disabled (mostly because the user may mistakenly uncheck something and we don't want them to lose everything already entered). The only exception to this is the date of death in the patient outcome section. As previous described, the date of death should be cleared if dead is unchecked/unselected (this already happens).

comments

sgattamneni wrote Nov 26, 2014 at 4:13 PM

Couple of issues noted in the long form for section 7 (Patient Outcome Info.):
  1. Changing "final status of the patient" from 'dead' to 'alive' causes the already filled out fields to be cleared.
Steps to reproduce:
a. Select "final status of the patient" as '1-Dead' from the dropdown
b. Enter values into the associated fields
c. Again select "final status of the patient" as '2-Alive' from the dropdown
  1. Issue with enabling an associated field when the initial answer is 'Yes'
Steps to reproduce:
a. Select "Did the patient have signs of unexplained bleeding at any time during their illness" = Yes, so that the field "If yes, please specify" should be enabled

Noted "If yes, please specify" field is not enabled unless you click the mouse on some other field first. It works fine when you tab through the fields

sgattamneni wrote Nov 26, 2014 at 4:50 PM

Issues noted in the long form for section 7 (Patient Outcome Info.):
  1. Changing "final status of the patient" from 'dead' to 'alive' and viseversa causes the already filled out fields to be cleared.
Steps to reproduce:
a. Select "final status of the patient" as '1-Dead' from the dropdown
b. Enter values into the associated fields of "If the patient is dead:"
c. Again select "final status of the patient" as '2-Alive' from the dropdown
  1. Issue with enabling an associated field when the initial answer is 'Yes'
Steps to reproduce:
a. Select "Did the patient have signs of unexplained bleeding at any time during their illness" = Yes Noted "If yes, please specify" field is not enabled unless you click the mouse on some other field first. It works fine when you tab through the fields

*Note: This is happening with 'Fever' and "Other non-hemorragic clinical sysmptoms" fields. Also the isssue is there with other similar fields on other pages of the form also, please fix them aswell.
  1. Village/Town label is overlapping and not aligned properly -- give space between "Village/Town" label and actual text field

wrote Nov 26, 2014 at 7:44 PM

den4 wrote Dec 15, 2014 at 10:35 PM

Checked in changes to Epi 7 long forms for -en and -fr to prevent most of the clearing of field values when other fields' values contradict.

den4 wrote Dec 15, 2014 at 10:43 PM

Mausman - Short forms
den4 - Long forms
Status changed to 'Resolved'.

lushilu wrote Dec 31, 2014 at 2:34 PM

Remaining issues as of 9.5.5:

Short form:
  1. In section 4, if a source case's status is changed from "Dead" to "Alive" in the right-most column, the date of death clears. The same thing happens if the source case's status is changed from "Alive and dead" to "Alive". These dates of death should not be cleared when the source case's status is changed (note that this is different from the request that the date of death clear that is described in the requirement - that applies specifically to the case's date of death in section 7).

wrote Dec 31, 2014 at 2:35 PM

wrote Jan 5, 2015 at 3:19 PM