Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Responsible Person: | |||||||||||||
Other parties to review/input: | |||||||||||||
FYI: | |||||||||||||
Targeted release date: |
| ||||||||||||
Jira Status: |
|
...
(DT comment: Christina Riley, I think this feature is straightforward enough to skip CHAI review step, but please indicate there are specific clarifications needed from CHAI, e.g., which fields should be editable vs. non-editable)
# | Step | Status | |
---|---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | COMPLETE Christina Riley | |
2 | |||
3 | Get VW review | COMPLETE: Pierre Dane | REVIEW:
|
4 | Get Ona feedback | FYI - ready for review: Craig Appl | |
5 | Responsible - 1 iteration for feedback | ||
6 | Ona sign off | ||
7 | Ona tech spec scoping | ||
8 | Ona LOE | Large to X-Large | |
9 | Ona scheduling |
Notes
- Summary: Need editable and non-editable fields
- Relevant for both Bednet Distribution and Blood Screening forms
- Mosquito Breeding Site and Mosquito Collection Site forms, and PAOT forms can be re-completed numerous times and do not require this feature
...
- Family View > Tasks list (DT comment: Craig Appl / Pierre Dane: does a list of all Reveal views already exist? Want to ensure we are using the same terminology to reference possible views)
- QUESTION/RECOMMENDATION: Do we want to indicate Indicate under each task status in the Family List View that a task was edited (i.e. under 'COMPLETE' the user could see in smaller font 'Edited mm/dd')
- Add "Edit" button to top of bednet distribution form and blood screening form
...
Form Editing View
Edited Date View
Software Requirements Specification
This section contains notes on what needs to be developed that were generated 23rd July to support estimating:
- Project activities:
- Verify the data dictionary to ensure the editable fields are appropriate
- We need to identify the underlying business logic when an edit form is completed compared to the first time that we need to
- We need to design the interactions (Roger's input is required)
- We need to decide whether we should prepopulate the form or ask them to resubmit all together (this may mess up skip logic)
- Android client
- We need to add a view to display and edit the form information
- We need to update the form loading actions to ensure we can link these edited forms to tasks that were marked complete.
- We need to update post save actions for edited forms
- We need to update the form JSON in both languages to identify which forms should be edited.
- Web UI
- We need to update the data warehouse tables to make previous versions available for querying
- We need to update the ETL to ensure the information is mapped appropriately
- We need to display the latest version of the form and possibly some indicator of the total number of versions submitted.
Justification
Thailand wants to be able to make corrections when mistakes are made during form completion, and add any additional information as necessary.
...