Keeping a users state (disclosure of sections,. search parameters, recent items etc.)?
*Will retain collection states, disclosure, component state being maintained in current design. A closed tab will remain closed throughout the session until it’s changed by the user; validation will override that, but the general spirit is there.
*Sort order for collections isn’t currently retained, would have to look at that; might be tricky due to the data tables and client sidedness of collections.
*Recent items - seems like something we’d have to build into the framework, but would be very useful to the user. Views that you’ve visited at a minimum. History support done with path based breadcrumbs could help with that. This could be it's own JIRA we think.
Session support is lighter weight then complete a user preferences framework and will largely meet the needs that we've identified through M1-M5 design work, and recent ENR M5 Usability Study