...
# | Title | User Story | Label | Importance | Notes | JIRA Ticket | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Batch Approval for Requisitions | As a district-level (or any mid-level) requisition approver,
| Malawi | Nice to have | Core placeholder, implemented in Malawi
| |||||||||
Offline support | As a requisition approver, I want to start my approval process and be able to work on it over a number of sessions to approve the entire budget. This requires that I am able to work on the page while offline, and that I can trust the data will not disappear or become lost when turning off the computer. |
| ||||||||||||
Findable errors | As a requisition approver, I need to be able to view and remove errors from the large table that is hard to navigate. |
|
Open Questions
# | Issue | Resolution |
---|---|---|
1 | Really large table The batch requisition screen can be extremely large. Malawi estimates that a DIVO might have 20 facilities to approve, and some programs with over 300 orderables. There is no internal navigation to orient the user (ie how does a user find a specific orderable, or facility)
|
Diagrams
Here is a high-level overview of the batch approval process:
...