-
Type:
Task
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
FLW Mobile App
-
All
What this is
Move consent data between the FLW app and the central server: download what is needed before going to the field, and upload consents, withdrawals, audit entries and access logs when back online.
Steps
- Download (when online, before going to the field): Get the latest notices (all languages), purposes, and the consent status of beneficiaries in the FLW user's area (AMM-2533).
- Upload (when back online): Send consents, withdrawals, audit entries and access logs from the device (AMM-2533). Proof files are uploaded separately (AMM-2510).
- A consent with the same device-made ID is a duplicate. It must not be saved twice.
- If an offline withdrawal and an online consent conflict, a withdrawal always wins over an older or equal consent. A later full consent stays current.
- The device deletes its local copy only after the server confirms the upload.
- Handle failed or partial uploads so that nothing is lost and a retry is safe.
Done when
- The FLW app can download everything it needs before going to the field.
- Uploading the same consent twice creates one record.
- A withdrawal wins over an older or equal consent.
- Local data is deleted only after the server confirms.
Dependencies: FLW-1271, AMM-2510, AMM-2533. Mirrors AMM-2533 (client side).
Open questions: [TBD/CLARIFICATION REQUIRED]
- AMM-2533 is designed for the STOP TB camp laptop (signed by a device key). Does the FLW app use the same endpoints and device-key signing, or a different path?
- Decision D-06: maximum age of downloaded data.
- How does this fit with the existing FLW sync (see 2.3 sync fixes)?
Source: DPDPA Compliance Proposal v14, sections 3.2.1, 3.2.2, 8 (M1, M6 to M12, M14)