| Page Properties | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
Status
# | Step | Status | ||||||
|---|---|---|---|---|---|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc |
| ||||||
| 2 | Get CHAI review | |||||||
| 3 | Get Akros Review | |||||||
| 4 | Get Ona feedback | |||||||
| 5 | Responsible - 1 iteration for feedback | |||||||
| 6 | Ona sign off | |||||||
| 7 | Ona tech spec scoping | |||||||
| 8 | Ona LOE | |||||||
| 9 | Ona scheduling |
...
For larval dipping and mosquito collection, there is no business data. If business data changes the task status, then will require coding
Questions
1) Will a user be able to define an entirely new form by uploading JSON or will they only be able to modify existing forms?
2) To what extent will the Reveal Android code need to be modified per country implementation? My understanding is that there is branching logic in the Android code that is custom per country (please correct me if I am wrong). I would think that as a part of this requirement that no custom Android code would need to be written for an implementation unless such implementation had unique requirements. The JSON should specify everything the Android client needs.
3) Where else will changes need to be made to Reveal other than the JSON for customizing the application? We (TerraFrame) has not gotten into the details of the reporting stack (NiFi/Superset), but will adding a new field to the JSON require additional changes to the reporting stack as well?
...