Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-4105

Returning from a document loaded from the action list returns the user to the first page

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.1.1
    • Fix Version/s: None
    • Component/s: User Interface
    • Epic Link:
    • Rice Module:
      KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Review Completed

      Description

      When a user is finished with a document loaded from the action list, the framework returns the user to the action list (good)

      But, it does not preserve the user's location in the action list (nor any filters applied - haven't verified this part), so the user is always returned to the first page, even if the document they took action upon was on the last. (As when the user is taking care of the oldest documents first.) This forces the user to re-page through the action list to get back to the page they were on.

        Attachments

          Activity

          Hide
          ewestfal Eric Westfall added a comment -

          This behavior needs to be reviewed at the KAI. Is it desirable that current state of the action list is saved in the session across multiple page requests?

          Jonathan, I assume this is what you are referring to here?

          Show
          ewestfal Eric Westfall added a comment - This behavior needs to be reviewed at the KAI. Is it desirable that current state of the action list is saved in the session across multiple page requests? Jonathan, I assume this is what you are referring to here?
          Hide
          jkeller Jonathan Keller added a comment -

          Yes. This came up during our testing. If you have a long action list and are working from the bottom (oldest items first), being reset to the top of the list every time you return can be annoying to the users. The issue is actually two-fold.

          If you view the route log from the action list, there is no way to return from it to the action list, as it opens in the same window. Going back will often (probably depending on browser) reload the page since it is not cached.

          When opening a document - it opens in a different window. However, when the document is closed by using one of the in-document buttons (as by approving it), the user is returned to the action list - but in the new window! And at the top of the action list. (Which is my guess of where this came from.) That's almost a bigger issue, where users don't realize that the new window has opened and after processing a few documents are likely to have a series of action list windows open.

          Show
          jkeller Jonathan Keller added a comment - Yes. This came up during our testing. If you have a long action list and are working from the bottom (oldest items first), being reset to the top of the list every time you return can be annoying to the users. The issue is actually two-fold. If you view the route log from the action list, there is no way to return from it to the action list, as it opens in the same window. Going back will often (probably depending on browser) reload the page since it is not cached. When opening a document - it opens in a different window. However, when the document is closed by using one of the in-document buttons (as by approving it), the user is returned to the action list - but in the new window! And at the top of the action list. (Which is my guess of where this came from.) That's almost a bigger issue, where users don't realize that the new window has opened and after processing a few documents are likely to have a series of action list windows open.
          Hide
          ewestfal Eric Westfall added a comment -

          This was reviewed by the KAI on September 2nd at this meeting:

          https://wiki.kuali.org/display/KULRICE/September+2,+2010+meeting

          The decision made by the group was that, yes, the action list should preserve it's current context (including filter, current sort, and current page) even when someone navigates away and comes back (meaning essentially that the current state will need to be stored in the session).

          Show
          ewestfal Eric Westfall added a comment - This was reviewed by the KAI on September 2nd at this meeting: https://wiki.kuali.org/display/KULRICE/September+2,+2010+meeting The decision made by the group was that, yes, the action list should preserve it's current context (including filter, current sort, and current page) even when someone navigates away and comes back (meaning essentially that the current state will need to be stored in the session).
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.
          Hide
          ewestfal Eric Westfall added a comment - - edited

          Closing really old action list jira as what it is mentioning here should be addressed as part of a new action list as opposed to changing behavior of the old one. Was sure to note the idea in action list document:

          https://docs.google.com/a/kuali.org/document/d/1pnJh2EdTw_DDL1Pp947VP1OFjf8_lMvEaabbth_pveM/edit

          Show
          ewestfal Eric Westfall added a comment - - edited Closing really old action list jira as what it is mentioning here should be addressed as part of a new action list as opposed to changing behavior of the old one. Was sure to note the idea in action list document: https://docs.google.com/a/kuali.org/document/d/1pnJh2EdTw_DDL1Pp947VP1OFjf8_lMvEaabbth_pveM/edit

            People

            • Assignee:
              Unassigned
              Reporter:
              jkeller Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: