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

ActionRequestServiceImpl.saveActionRequest does not allow for documents to route to inactive groups.


    • 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-5824Added a check to deactivate the action request when it tries to route to an inactive group based on document type policy
      KULRICE-6108Document ability to configure deactivation of action requests when routing to an inactive group
      KULRICE-4285Allow rules to be routed to Groups with "All" approve policy
      KULRICE-1840Allow for exception routing group to be different based on document data
      KULRICE-1897Allow for further customization of exception routing
      KULRICE-8478Role Maintenance Document: Add ability to search on future or inactive assignees
      KULRICE-3341If a document routes to a node with no members then the document gets "stuck" there
      KULRICE-8091Adhoc routing tab utilizing Groups on all documents missing asterisks
      KULRICE-4217Add Group Description field to Group document
      KULRICE-14064People Flow does not add an annotation in Route Log
    • Rice Module:
    • Application Requirement:
    • KAI Review Status:
      Pending Review
    • KTI Review Status:
      Not Required


      At IU, one of our users ran into a situation involving routing to groups via custom role attribute. The criteria change, so new groups were set up and the old groups were emptied out and inactivated.

      When attempting to return documents that had once routed to now inactive group back to the start node the error "Routing to inactive workgroup. Putting document in
      exception routing." occurs. They were putting them back to the start node so that they could route to the newly created groups.

      Initially, we thought that the role was not re-evaluating correctly, but It turns out that this error is occurring before it can get to the re-evaluation of the role. ActionRequestServiceImpl.saveActionRequest (where the error is coming from) is called by revokeRequests, which is called by ReturnToPreviousNodeAction.recordAction. All of the old action requests on the document are revoked before the node change takes place, but in this case when it goes to save the revoked action requests, an error is thrown due to the fact that the group on the old action request is no longer active.

      From Eric Westfall:

      In general I think that the fact that we are doing this check on save of an action request is problematic. I think it would probably make more sense to allow for documents to continue to route to inactive groups (maybe make a doc type policy on the behavior) to prevent interruption of service. But then prevent people from assigning inactive groups to various things (rules and roles) from the UI. This is a good one to enter a Kuali Rice jira with the foundation for and the rice team can figure out how best to handle it (getting appropriate functional input).

      More info in JIRA : https://uisapp2.iu.edu/jira-prd/browse/WFR-12533 (Not sure everyone could see this, so I included the needed information in here.)

        Issue Links


          There are no comments yet on this issue.


            • Assignee:
              Shannon Hess
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:

                Structure Helper Panel