[Uganda project - Technoforte team] Correction flow validates hidden required field when DOB changes

[dibik96]

Description

In the Birth Registration correction flow, validation fails when a field that was previously visible and required becomes hidden due to a change in Date of Birth (DOB).

The field child.reason (Reason for Late Registration) continues to be validated as required even after it is no longer applicable, causing the correction request to fail and record stuck in the outbox

---

Steps to Reproduce

1. Declare a birth where:

   • child.dob is beyond the late registration threshold
   • child.reason becomes visible and a value is selected

2. Submit the declaration

3. Initiate a correction

4. Update child.dob to a value within the allowed registration period

   • child.reason is now hidden

5. Submit the correction

6. Record stuck in the outbox

   Additional Notes

   • Does not occur during initial declaration
   • Reproducible only in correction flow

---

Observed Behavior

Correction request fails with validation error:

[
  {
    "id": "child.reason",
    "message": "Required",
    "value": null
  }
]

Endpoint:

POST /event.actions.correction.request.request

---

Expected Behavior

When a field is hidden due to conditional logic:

• It should not be validated as required, or
• Its value should be cleared before validation

Correction should succeed when child.reason is no longer applicable.

---

Analysis

• child.reason is defined with:

  • required: true
  • Conditional SHOW logic based on DOB

• In the correction flow:

  • The field becomes hidden
  • The stored value is null
  • Backend validation still enforces required: true

Required validation is applied even when the field is not visible.

---

Possible Improvements

1. Clear values of hidden fields before validation
2. Introduce support for conditional required validation

---

Environment

• OpenCRVS Core: v1.9.4
• Flow: Correction → Request

---

[prinzab]

@dibik96 This issue does not exist in core so it must be a configuration issue. Please check again, ensure you are on the latest version (1.9.5) and you have done the configuration properly. I am going to go ahead and close this discussion.

CC: @euanmillar

[dibik96]

@prinzab Issue is not replicating in 1.9.5. So I will close this ticket.