Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-8866

Improved sessions support (restore when session dies, multiple user tab support)

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 2.2
    • Fix Version/s: 2.3.0-m2, 2.3
    • Component/s: Development, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-1352form is not restored from session for multipart request
      KULRICE-9705Create Smoke tests to validate Session restore.
      KULRICE-9379Add support for rendering views in KRAD without requiring a session to be established
      KULRICE-1036Support Session Scope for Kuali Documents
      KULRICE-12505JS Error with session storage when using Safari in private browsing mode
      KULRICE-8427Handling of Session Timeouts
      KULRICE-8573KualiHttpSessionListener.sessionDestroyed(..) assumes only one document locked by user
      KULRICE-8428Improved support for KRAD modules
      KULRICE-13159Rice placing HTTP request into session scope - prevents session replication/restore
      KULRICE-5341UserSession gets bound to a thread, and eDocLite documents are not establishing user session properly
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Session
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Issue Links

        Activity

        Hide
        Matt Sargent added a comment -

        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

        Show
        Matt Sargent added a comment - 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
        Hide
        Larry Symms added a comment -

        Session restore. Save pertinent session info: current view, current page, history(at least last page), possibly current page form data.

        Show
        Larry Symms added a comment - Session restore. Save pertinent session info: current view, current page, history(at least last page), possibly current page form data.
        Hide
        Larry Symms added a comment -

        Multiple user. We need the ability to act on behalf of other users (not only as if we were that user). The best example of this is advisors and registrars changing enrollment for a student on behalf of that student. Also need the ability to see exactly what the user is seeing without authenticating as them. In many cases students are blocked from registration and the registrar can't see the blocks so being able to act as that student allows them to diagnose exactly which blocks exist.

        Show
        Larry Symms added a comment - Multiple user. We need the ability to act on behalf of other users (not only as if we were that user). The best example of this is advisors and registrars changing enrollment for a student on behalf of that student. Also need the ability to see exactly what the user is seeing without authenticating as them. In many cases students are blocked from registration and the registrar can't see the blocks so being able to act as that student allows them to diagnose exactly which blocks exist.
        Hide
        William Washington (Inactive) added a comment -

        I read through: https://wiki.kuali.org/display/KULRICE/Improved+Session+Handling and I'm not seeing support for keeping user's state as described in the original requirements doc: "Would help keeping user state: disclosure states, Recent Items, search parameters, ordering of items." (From: https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AkWqIx6WhWnHdE5NMW5ZYmE3d2dzdTRMVUtyWGRNS0E#gid=12) Will this be a part of this work or another?

        Also, are the comments Larry left above also to be a part of this work?

        Show
        William Washington (Inactive) added a comment - I read through: https://wiki.kuali.org/display/KULRICE/Improved+Session+Handling and I'm not seeing support for keeping user's state as described in the original requirements doc: "Would help keeping user state: disclosure states, Recent Items, search parameters, ordering of items." (From: https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AkWqIx6WhWnHdE5NMW5ZYmE3d2dzdTRMVUtyWGRNS0E#gid=12 ) Will this be a part of this work or another? Also, are the comments Larry left above also to be a part of this work?
        Hide
        Matt Sargent added a comment -

        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.

        Show
        Matt Sargent added a comment - 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.
        Hide
        William Washington (Inactive) added a comment -

        The items that should be kept track of during the session are:

        • Disclosure states
        • Progressively disclosed/hidden items
        • Collection columns sort order
        • Search parameters

        (Recent Items requirements are being defined here: https://jira.kuali.org/browse/KULRICE-9219)

        Show
        William Washington (Inactive) added a comment - The items that should be kept track of during the session are: Disclosure states Progressively disclosed/hidden items Collection columns sort order Search parameters (Recent Items requirements are being defined here: https://jira.kuali.org/browse/KULRICE-9219 )
        Hide
        Jerry Neal (Inactive) added a comment -

        Hi William,

        What about tab groups? Should we maintain the currently opened tab across session?

        thanks,
        Jerry

        Show
        Jerry Neal (Inactive) added a comment - Hi William, What about tab groups? Should we maintain the currently opened tab across session? thanks, Jerry

          People

          • Assignee:
            Jerry Neal (Inactive)
            Reporter:
            William Washington (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel