Inconsistent Validation and Alert Behavior Across Data Entry Fields

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: Medium
    • 2.0
    • Affects Version/s: None
    • None

      Multiple inconsistencies have been observed in field validation and system-triggered alerts, leading to an inconsistent user experience and potential business rule violations.

      *Issues Observed:*

      1. *Referral Alert Not Triggered Consistently*

      • The "Referral to HWC" alert is displayed when the temperature exceeds 99°F for the first time.
      • If the temperature is subsequently changed to a normal/hypothermia value and later updated again to >99°F, the referral alert is not displayed.

      2. *Inconsistent Text Input Behavior Across Fields*

      • Some text fields allow both uppercase and lowercase characters.
      • Other fields automatically convert entered text to uppercase.
      • Similar fields exhibit different behaviors without any apparent business rule, resulting in inconsistent data entry.

      *Actual Result:*

      • Referral alert is not triggered on subsequent updates when temperature again exceeds 99°F.
      • Text input behavior varies across fields, with inconsistent capitalization handling.

      *Expected Result:*

      • The "Referral to HWC" alert should be triggered every time the temperature value exceeds 99°F.
      • Similar text fields should follow a consistent capitalization and input validation behavior as per the defined requirements.

        1. image-2026-06-22-15-23-53-946.png
          image-2026-06-22-15-23-53-946.png
          133 kB
        2. MicrosoftTeams-video (2).mp4
          4.01 MB
        3. screenshot-1.png
          screenshot-1.png
          89 kB
        4. screenshot-2.png
          screenshot-2.png
          98 kB

              Assignee:
              Archita Verma
              Reporter:
              Puneet Sharma
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: