A5d2 nomensage enable

[mlan225]

Resolves #250

Review checklist

• Inputting a valid value of 10 - 70 or 99 in NOMENSAGE (7b) enables checkboxes in 7c
• Inputting an invalid value that IS NOT 10 - 70 or 99 will disable the checkboxes in 7c
• Finalizing a packet with a value of 9988 in NOMENSAGE (7b) and no checkboxes selected in 7c will not produce an error message for no selected checkboxes
• Finalizing a packet with a value of NOT 99 in NOMENSAGE (7b) and no checkboxes selected will produce an error message to select a checkbox

Allow for NOMENSAGE to be 99 and enable checkboxes in 7c of the A5D2

99 = enable checkboxes

88 = disable checkboxes

valid range error for NOMENSAGE

Validation error if no checkbox is selected when checkboxes are enabled (and NOT 99)

[mlan225]

hey @ashleybot , Unless im overlooking somethig, Im having a hard time replicating your result. Is it possible that the old javascript was still cached and not causing the new disable to occur in the checkboxes?

Here are my results on the branch

[ashleybot]

This is incorrect:

Finalizing a packet with a value of 99 in NOMENSAGE (7b) and no checkboxes selected in 7c will not produce an error message for no selected checkboxes

@mlan225 NOMENSAGE = 99 should require at least one checkbox.

[mlan225]

• Added validation to require checkbox selection when NOMENSAGE == 99

[mlan225]

Adding a comment about it here @ashleybot , but currently NOMENSAGE has no requirement attributes and may be a worthy of an issue card.

If i am reading the documentation correctly, it appears that NOMENSAGE has a "conditional missingness", which i interpret as "will sometimes be required under certain conditions".
https://github.com/naccdata/uniform-data-set/blob/main/forms/uds/a5d2/form_a5d2_ivp_questions_and_vars.csv

[ashleybot]

Adding a comment about it here @ashleybot , but currently NOMENSAGE has no requirement attributes and may be a worthy of an issue card.

If i am reading the documentation correctly, it appears that NOMENSAGE has a "conditional missingness", which i interpret as "will sometimes be required under certain conditions". https://github.com/naccdata/uniform-data-set/blob/main/forms/uds/a5d2/form_a5d2_ivp_questions_and_vars.csv

@mlan225 Yep, this is correct and it would be a quick fix in this feature branch. So, the rules should follow

• NOMENSAGE RequiredIfRange MENARCHE 5-25
• NOMENSAGE RequiredIf MENARCHE = 99

References

If MENARCHE in (5-25, 99) then NOMENSAGE must be present

https://github.com/naccdata/uniform-data-set/blob/main/forms/uds/a5d2/form_a5d2_ivp_error_checks_mc.csv

[ashleybot]

@mlan225 Realized this morning that the RequiredIf annotations are already being added in this PR #261

[ashleybot]

@mlan225 NOMENSAGE changes look good! Good to bump to 5.0.2.