-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Affects Version/s: None
-
None
-
STOP TB Sprint 8
The BenConsent (Beneficiary Consent) field is not being correctly saved/collected in the database. Regardless of the actual consent input/action performed by the user, the stored value always shows as 0, indicating the consent status is not being captured or persisted correctly.
This is a data integrity issue — if consent is genuinely being given by beneficiaries (e.g., via a checkbox, toggle, or digital signature step) but not reflected in the database, it creates a compliance/audit risk, since there'd be no accurate record of whether consent was actually obtained.
Steps to Reproduce:
- Navigate to [screen/form where BenConsent is captured — e.g., registration form]
- Provide consent as the beneficiary (e.g., check "Yes"/select consent option)
- Submit the form