...
Refer to this Jira ticket:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Use cases:
- Household registration
...
- (amenities) record should sync to server, only once Head of the Family Member's consent is verified. Like order of record syncing process should follow: Household registration >> Head of the Family Member registration >> Family Member registration; only once consent is verified.
- Successfully, OTP verified records should sync to server and indicate with green
...
- color symbol on beneficiary card as "consent is taken"
- Beneficiary records that are not verified with OTP, should not sync to server, should save as draft and indicate with orange
...
- color symbol on beneficiary card to notify "consent is due"
- Existing Beneficiary records that are already synced to server, but OTP consent is not verified earlier, should indicate with yellow
...
- color symbol on beneficiary card to notify "record is synced but consent is due"
- Beneficiary records should be flag based on the status of consent
- In Beneficiary line listing, should have a filter to sort the records based on the status of consent.
This feature should be implemented in the existing screens/ form of Head of the Family and Family Members registration.
...
For receiving the OTP on the Beneficiary's mobile number, verifying OTP, etc an API and SMS gateway integration is required, for these details refer to this Jira ticket:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...