| Page Properties | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
- As a system administrator, I would like to be able to create and update Reveal forms without needing to compile and release a new APK
- Changes will include new form fields, hiding of forms fields but not updates to existing form fields (e.g. data type or the meaning of the form field)
- Changes can include modifications to calculated fields, and changes to skip logic
- Changes will also include the workflow rules for task generation based on form actions (Dynamic Tasking in the Client)
There should be a UI for form development- Forms will be authored and updated in the undelaying JSON documents
- Changes to form fields should be reflected in the data warehouse
- The forms available to each implementation should be configurable
- Form changes should be immediately testable in a realtime test application (as opposed to Android Studio or other IDEs where code needs to be compiled)
- A minimum dataset should be defined for each form which will be used for dashboard reports and should not be changed
Definitions
Mock-Ups
Views
Justification
Dependencies
...
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?
Test Case
# | Step | Pass / Fail | Comment |
|---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |
...