-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 2.0, 2.1
-
None
-
FLW Sprint 25, FLW Sprint 26
-
FLW Mobile App
-
All
There’s an issue where a single ABHA number is being patched to multiple beneficiaries, which is causing discrepancies in beneficiary data. Ideally, each ABHA should be associated with a unique beneficiary, and the patching process should ensure this one-to-one mapping.
Steps to Reproduce:
- Initiate the patching process for a single ABHA number.
- Attempt to assign or patch this ABHA number to multiple beneficiaries.
- Observe the incorrect association of a single ABHA number to multiple beneficiaries.
Expected Result:
Each ABHA number should be patched to only one beneficiary at a time, ensuring a correct mapping of ABHA to the beneficiary.
Actual Result:
The ABHA number is being associated with multiple beneficiaries
Acceptance Criteria:
- Patching a single ABHA number should ensure it is linked to one beneficiary only.
- If an ABHA number is already assigned to a beneficiary, it should not be available for patching to another beneficiary without explicit disassociation.
- An error message or warning should be displayed if an ABHA is patched to multiple beneficiaries.
- The system should validate that no ABHA number is duplicated in the beneficiary records.