Currently, when a user goes back from the encounter details to the encounters list, the users position in the list is not saved. This means the user has to rescroll through all of the previous months data in order till they reach the intended encounter.
We want to change this so that the users state is stored when they return back to the encounters list.
Outcomes
Discover how to implement saving user state
Acceptance Criteria
Given User has list of Encounters
When user Clicks on the Load Previous Month button
AND Clicks on an Encounter from previous month
AND Clicks on return to encounter list
Then User can see the previously loaded months Encounters
description
Currently, when a user goes back from the encounter details to the encounters list, the users position in the list is not saved. This means the user has to rescroll through all of the previous months data in order till they reach the intended encounter. We want to change this so that the users state is stored when they return back to the encounters list.
Outcomes
Discover how to implement saving user state
Acceptance Criteria
Given User has list of Encounters When user Clicks on the Load Previous Month button AND Clicks on an Encounter from previous month AND Clicks on return to encounter list Then User can see the previously loaded months Encounters