Activity #1276
closed
Added by Thara S Pillai almost 3 years ago.
Updated almost 3 years ago.
Category:
Development-WebAPI
Description
This can be addressed only after updating the unique key constraint in the database table level by SDHM team
eHealth to provide requested design inputs (Ref: Mail on 27.09.2023 and CDAC-eHealth MoM - 21.07.2023)
- Copied from Bug #1234: Aadhar duplication – existing in member survey (both app and API level ) added
- Subject changed from Aadhar duplication – existing in member survey (both app and API level ) to Aadhar duplication – existing in member survey (API level )
- Category changed from Development-App to Development-WebAPI
- Assignee changed from Jiji P B to Shameera S L
- % Done changed from 100 to 0
- Due date changed from 10/04/2023 to 10/09/2023
- Priority changed from Normal to High
- Start date changed from 10/03/2023 to 10/09/2023
eHealth shares logic for handling Aadhaar duplication on 04.10.2023.'
Talk with eHealth for further clarification.
Adding Unique Constraint is not possible since there exist duplicate aadhaar data.
Aadhaar Trigger function Implemented by SDHM on insert or update in member survey. Kindly handle this function return errors on APIs.
If insert or update failed, following error msg return for member survey upload failed.
This aadhaar_no already exists, please enter a different aadhaar_no!
or
Aadhaar Already Exist Please Upload Valid Details!
Existing app shows sync failed which is not correct msg. Intimate the user regarding sync failed due to aadhaar duplication against the particular member and there should be a provision to delete duplicate member from app since it is not uploaded.
- Due date changed from 10/09/2023 to 10/10/2023
- Parent task changed from #1267 to #1285
- Parent task changed from #1285 to #1288
- Tracker changed from Bug to Activity
- Status changed from New to Closed
Also available in: Atom
PDF