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

Add ability for KEW to log and display detailed information about a document which is "on it's way" to exception routing

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-4013Add information about lack of ability to override inherited PKClass
      KULRICE-1293Add a tab to the route log which shows recent routing errors, number of time doc has been retried, etc.
      KULRICE-4407Route Log - detail missing on requested of workgroup
      KULRICE-809Create Functional Documentation for the Route Log
      KULRICE-5932Skip Routing for KEW
      KULRICE-2456Implement support for specification of an "exception" process for exception routing
      KULRICE-495Remove the code in DocumentAuthorizerBase which is preventing the "Routing Report" link from displaying
      KULRICE-14064People Flow does not add an annotation in Route Log
      KULRICE-1935Add information about the current node to eDocLite document state
      KULRICE-2781Create a way to visually display a routing process from a Document Type inquiry
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      This is something I just thought of coming out of a conversation on the Rice 2.1 team skype chat. Whenever a document is having trouble routing (for whatever reason) it's not very easy for people to debug it. First of all, depending on various settings, a document could get retried multiple times and take up to an hour to finally fall into exception routing. During this time, the document just looks like it's "ENROUTE" but not going anywhere.

      The solution to this is probably something to discuss and shop around to our various groups but I was thinking something along the lines of:

      • On the backend, we have a database table which stores detailed information about all the failed tries (including detailed stack trace/error message, detailed logs from the routing attempt, the node it was trying to route to, etc.)
      • Add a new tab to the route log called "Routing Errors" or something along those lines
      • This tab would be expanded and you can see a list of failed routing events with timestamps. If you click on those they will expand to show the full detail for the failed routing event.
      • If the document is currently having trouble routing put something near the top of the route log that says "this document is having trouble routing, it has been retried x times and will be retried y more times at 2:00, 3:30. Estimated time it will enter exception routing if problems are not corrected is x:xx. Please see Routing Errors section below for more details" or something along those lines.

      Seems this would be helpful for people, otherwise they need to have access to the logs in order to figure out why a document is having trouble routing.

      The only thing I would be concerned about here is that if we keep the full logs from failed routing attempts in the database, it may end up taking up a lot of space. Something to think about in terms of having a retention policy or something similar for this information.

        Activity

        Hide
        Jessica Coltrin (Inactive) added a comment -

        setting to 2.1 for 2.1 DMs to review.

        Show
        Jessica Coltrin (Inactive) added a comment - setting to 2.1 for 2.1 DMs to review.
        Hide
        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
        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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel