You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Already have an Abha number should be there till the end of registration
Add support to use Abha address for linking (check if this is directly possible)
Describe the bug
When a user initiates a ABHA generation process for a patient, only realising at the phase of entering "ABHA adress" that the patient already has a ABHA no. Then there is no way of going back to the form to link existing ABHA.
Finally the pop window will allow user to enter ABHA address. However, if the patient already has ABHA against the aadhar, an error at the bottom of the field says " Existing ABHA Address is used if ABHA Number already exists." CARE will not allow user to generate a new ABHA address.
Now if the patient doesn't remember the ABHA address (but has access to the ABHA Number), there is nothing more user can do.
Even if the user closes the pop-up and again going to patient dashboard and clicks on "Link ABHA" to restart the process, this time to link existing ABHA, the same old pop-up with ABHA address input field appears.
<img width="395" alt="Screenshot 2024-01-09 at 2 36 53 PM"
Refreshing the patient dashboard and then taking the "Link ABHA" option fixes the problem. However user may not remember to refreash.
The text was updated successfully, but these errors were encountered:
Todo:
Already have an Abha number
should be there till the end of registrationDescribe the bug
When a user initiates a ABHA generation process for a patient, only realising at the phase of entering "ABHA adress" that the patient already has a ABHA no. Then there is no way of going back to the form to link existing ABHA.
To Reproduce
Steps to reproduce the behavior:
<img width="395" alt="Screenshot 2024-01-09 at 2 36 53 PM"
Refreshing the patient dashboard and then taking the "Link ABHA" option fixes the problem. However user may not remember to refreash.
The text was updated successfully, but these errors were encountered: