good morning dear
I would like to know how to solve the failure that DHIS2 for individualized “Tracker” data has presented, since I cannot audit the file, or identify who is the Community Agent who registered the beneficiary, in order to facilitate follow-up in case of identifying a bad registration.
Thank you in advance for your attention and help.
NB: We are using Version 2.61
Hi @IBitone,
Would you like explain a bit more about your use case? It comes in handy when thinking of a solution.
I would like to invite you to check out this topic discussion about audits, Remote support of Android devices
It would be interesting how you identify a bad registration and if using program rules as well as skip logic could help in preventing it from happening in the first place. Please feel free to share more info about this challenge.
Thank you!
1 Like