When an already registered child in OpenSRP has been enrolled into mvacc or SMS reminders, the code does not cater for the fact that:
they might not have previous states in the Rapid Pro state table
They might have previous REGISTRATION_DATA states which have not been synced to RapidPro which has UNPROCESSED_UUID. This happens when the client syncs both birth registration and update registration events of the same client within the same batch, time between 2 RapidPro syncs, which is going to be processed by the RapidProEventService before syncing to RapidPro. The code does not update the UUIDs of the UPDATE_REGISTRATION_DATA records.
Tasks
[ ] Add code to handle all the cases outline above
[ ] Write a script/query to update the current CHILD records of UPDATE_REGISTRATION_DATA with their correct UUIDs
When an already registered child in OpenSRP has been enrolled into mvacc or SMS reminders, the code does not cater for the fact that:
UPDATE_REGISTRATION_DATA
records.Tasks
CHILD
records ofUPDATE_REGISTRATION_DATA
with their correct UUIDs