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

Problems with "Future Action Requests" involving initiator routing


    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.3
    • Fix Version/s: Backlog
    • Component/s: User Interface
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-3603After a document is saved but before it is routed, the "Future Action Requests" tab on the doc's route log does not display any of the ad hoc requests
      KULRICE-3978time/date is irrelevant for future action requests
      KULRICE-2729The "Future Action Requests" tab on the Route Log does not work properly with a client application using "embedded" mode
      KULRICE-370Route Log panel shrinks when viewing future requests
      KULRICE-749Still seeing problems with orphaned Action Requests
      KULRICE-2641Future Action Requests section of route log shows all requests
      KULRICE-7451Future Action Requests tab does not work when using standalone Rice server
      KULRICE-6887RouteLog: Pending and Future Action Requests showing duplicate requests for the same account
      KULRICE-3577WorkflowUtilityWebServiceImpl.getPrincipalIdsInRouteLog does not return principal ids for group members who have action requests "on the route log"
      KULRICE-2158Action Request shows up in Route Log under pending, but not in Route Report
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:


      In Rice 2.x, the SimulationEngine appears to be forcibly setting the simulated doc header's initiator principal ID to "simulation". When viewing the route log's "Future Action Requests" for documents with routeHeader-based initiator routing, this can cause the tab to either fail the simulation routing or cause the wrong user (or no user) requests to be displayed at the initiator routing points in the doc's route path.

      Updating the SimulationEngine to not forcibly replace the initiator workflow/principal ID when it's already non-blank is one workaround for this issue.


        There are no comments yet on this issue.


          • Assignee:
            Chad Hagstrom
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Structure Helper Panel