...
The user adds a point (current behaviour)
The user opens the form (current behaviour)
The user long presses the location
Perform the following logic:
If the task status = “Ready”
A modal window pops up with the following:
Title: Mark Location Inactive
Text: Please confirm that this location should be marked inactive.
Options (Confirm or Cancel)
The user taps “Confirm”
If the user taps cancel, the modal is closed
The system performs the following business logic
Change the location.properties.status to “Inactive”
Loop through any tasks assigned to it change the status to “Cancelled”
If the task status != “Ready”
Display a toast message stating “You can not make this structure inactive because tasks are completed against it.
Note: If a task was assigned to that location and it was cancelled, the location will display as grey and the user will not be able to interact with it.
Workflow 2: Mark Location Ineligible for Register Family Task (status = Ready)
...
The user taps the yellow structure and the register family form displays (current behaviour)
The first question asks “Is this location eligible to register a family?” with the default value = Yes
All other fields are automatically displayed as is the current behaviour
The user changes the value to “No”, all fields hide.
Step 2 of the form is also hidden
The “Next” button in the top right changes to “Submit”
The user taps submit and the form is saved.
The user is redirected back to the map view
The user can tap on the location and a card displays with information that’s currently available if they tap on a different location type (PAOT, larval dipping, mosquito collection point)
The user can view the task in the task list view with a black button labeled “Ineligible”
Workflow 3: Mark Family Member Ineligible for Blood Screening Task
...
Update every form to add eligibility skip logic to it. (i.e. “is this person eligible for _____?” default = yes)
Register Family
Add Family Member
Update Family
Update Family Member
Bednet Distribution
Blood Screening
BCC
Mosquito Collection
Larval dipping
PAOT
Add logic to the post form save action to support ineligible skip logic in the forms Add Archive Family Member formdefined in 1 above
Add a card view to the location when a register family task is marked as ineligible
Make sure this button opens the register family form so that a user can register a family
Add Archive Family Member to the option menu
Add the loops that archive the family member as defined in Workflow 5 above
Add Archive Family to the option menu
Add the loops that archive the family as defined in Workflow 6 above
Add support for displaying locations in black that have been marked as ineligible in the map view
Add support for displaying buttons in black background with white text that have been marked as ineligible in the family module’s task list view and the task list view
Update the family name that’s displayed in the task list view if the register family task is marked as ineligible.
By default, it displays “Unenumerated structure” (current behaviour)
If a family is registered, it says the name of the household (current behaviour)
If marked as ineligible display “Ineligible Location”
Add support for marking a location as Inactive as defined in Workflow 2
long press interaction
add a modal
perform the business logic once made inactive as defined in workflow 2
(Samuel Githengi , I’m not sure if this is already done) Create an archival process that:
Marks the “Client” as archived (family or family member)
Marks the task as archived
Marks the event as archived
Update the sync process to sync these archived items from the Android client to the server
Update the server side sync process to exclude archived tasks, events and clients from syncing to new clients