Navigation Behavior: persistent state between applications
Description
Environment
Potential Workaround
Checklist
hideTestRail: Results
Activity
Mike Taylor June 8, 2017 at 1:53 PM
I'll be getting onto that release this afternoon. See .
Cate Boerema June 8, 2017 at 10:02 AM
Oops. Missed that.
I think we are going to go through the planned demo work in the Roundup today so it might be good to wait until after that to roll the release.
Mike Taylor June 8, 2017 at 9:57 AM
if I am editing an Item record and navigate away and back, I am not returned to edit mode for that item. This is only a problem with the item record. Things work perfectly for the user record.
That's correct: see my comment immediately before yours
We'll get an Items release before the demo.
Do we have any further Items work scheduled for the present sprint? It doesn't look like it, based on https://folio-org.atlassian.net/issues/?jql=project%20%3D%20UIIT%20AND%20status%20in%20(Draft%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Open%2C%20%22In%20Review%22%2C%20Blocked)%20AND%20labels%20%3D%20sprint15 – the only Items issues in this sprint are , 14, 15 and 17, which are all closed. if that's right, there's no reason for me (or someone) not to go ahead and roll the release.
Cate Boerema June 8, 2017 at 9:34 AM
Hi . I'm testing this in demo (not demo-test) as I think that has the newest code. Anyway, it is working great in general with one exception. Scenario 3: if I am editing an Item record and navigate away and back, I am not returned to edit mode for that item. This is only a problem with the item record. Things work perfectly for the user record.
On a side note, I kind of hate the way scenario 2 feels in reality (it feels really disorienting). Other users may or may not feel the same way. When I spoke with Filip about these scenarios he fully recognized that some of this stuff may need to change as we get feedback from users. It might just be worth mentioning that in the demo.
Thanks!
Mike Taylor June 7, 2017 at 12:48 AM
I released stripes-core v1.9.0, updated stripes-demo-platform to include it, and rebuilt the stripes-demo site. Most of the scenarios above should now be working on the demo site. (Exception: edit mode is not persistent in the Items module, as that has not yet been released.)
Details
Details
Assignee
Reporter
Priority
P3
Purpose: To modify FOLIO as needed to ensure that, when you navigate out of an app and return, you are returned to the previously displaying state
Scenarios:
Scenario
Given I navigate away from a viewing a record (e.g. a User A in the Users app) into another app
When I navigate back to the original app (Users app, in above example)
Then I should be viewing the previously viewed record (User A in above example)
Scenario
Given I navigate away from a new record form with no data populated (e.g. New User or New Item) into another app
When I navigate back to the app
Then I should be returned to the new record form (this is working already at the time the story was written)
Scenario
Given I navigate away from an edit record form (e.g. edit User or edit Item) in which no changes have been made into another app
When I return to the app
Then I should be returned to the edit record form (displaying most recently saved data)
Scenario
Given I have applied filters and navigate out of the app
When I return to the app
Then the previously applied filters should be retained
Scenario
Given I have entered a search term and navigate out of the app
When I return to the app
Then previously entered search term should be retained
Scenario
Given I have entered a patron in scan but not clicked "add patron"
When I navigate out of the app and then return to scan
Then the patron value entered should be cleared out (this is already working at the time the story was written)
Scenario
Given I have entered an item in scan but not clicked "add item"
When I navigate out of the app and then return to scan
Then the item value entered should be cleared out (this is already working at the time the story was written)
Scenario
Given a patron and/or loan(s) are displaying in Scan
When I navigate out of the app and then return to scan
Then the patron and/or loan(s) should continue to display (they should remain until the page is explicitly cleared using the "done" button) (Again, this is already working at the time the story was written)
Scenario
Given I navigate away from a page in settings into another app
When I return to Settings
Then I should be returned to the page I was previously viewing