Hi @Kenyuri … would you mind providing a bit more context about your user personas, the high level workflow, what a “Task” is in your example, and what types of edits you anticipate might need to be done?
There’s some nuance in the terminology and I think you are asking about editing and deleting Reports instead of Tasks, because it’s not possible to edit or delete a Task in the CHT. The terminology is a bit tricky because Tasks are completed by submitting a Report, and you can Edit/Delete those reports from the Reports page, but you can’t edit/delete a task.
Hello @michael , thank you for your response. I had initially confused the two terms but have since revised the post. I am developing a form where a CHW, who lacks the permission to edit a report, can request the necessary permissions and receive a response. Once a report is submitted, the CHW will no longer be able to edit it after it has been approved by the supervisor. Additionally, any report that remains unedited for more than a week after the reporting period cannot be modified
@Kenyuri can you please share a “happy path” example (ie the simplest version) of how you expect this to work and what you are trying to prevent or solve for? Why do you prevent CHWs from editing reports? Also, are CHWs and Supervisors both offline users?
Based on what you have mentioned, here is the workflow I understand you are looking to implement…
CHW submits a report
2 seconds after submitting it, the CHW realizes there is a typo
CHW requests authorization to edit the report from their supervisor
CHW waits for the supervisor’s response
Supervisor approves CHW’s request to edit
CHW receives notification that Supervisor approved request to edit
CHW fixes the typo by editing the report
Report is “locked”… no more edits can be made