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

If no "Resolve Exception" responsibility is defined for a particular document type (or one of it's parents) then the document will silently fail to go into exception routing

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-6991Improve the ability for "last ditch effort" exception routing to fall back to an administrator group or role in situations where other attempts to do exception routing fail
      KULRICE-7943Implement ability define a custom process "flow" for exception routing cases
      KULRICE-8538Responsibility Required routing flag not working unless responsibility defined for exact document
      KULRICE-4493sometimes documents route to nowhere
      KULRICE-2456Implement support for specification of an "exception" process for exception routing
      KULRICE-2415implement KR-WKFLW permission and responsibility checks
      KULRICE-3344Parent Responsibility and NullPointerException problems on the "Delegate Routing Rule Creation" screen.
      KULRICE-11034Context Document Save-Then-Route failing with optimistic lock exception
      KULRICE-11905Unable to copy document types - documents go into exception; doc title incorrect when copying multiple types of docs
      KULRICE-6994Parameter document routes to exception upon submission
    • Rice Module:
      KEW, KIM
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      This is obviously a problem because no one will know that this document has entered exception routing which is a bad thing.

      Here is David's email regarding this:

      I don't know if this is still the case in Rice 1.0.2.1 but I have seen this happen when I've been trying to use KIM exception routing for a document type but I don't have a "Resolve Exception" Responsibility set up properly in the system. The first time I saw the problem it was a document type hierarchy issue where I didn't have the hierarchy of my document type set up properly but the "Resolve Exception" responsibility was correctly on the parent document.

      If you are using KIM exception routing you should be able to verify that the "Resolve Exception" responsibility is set up properly finding your document type on the "Routing and Identity Management Document Type Hierarchy" page on your Rice server. Use the "View Document Configuration" link.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Structure Helper Panel