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

Change to Role membership from the Role document causes the affected enroute document to re-queue, while role membership changes from person doc does not


    • Type: Bug Fix Bug Fix
    • 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-8342Person document incorrectly validating "unique" attributes on role memberships
      KULRICE-13135Remove all membership mappings from GroupBo and RoleBo
      KULRICE-7749Unable to inactivate Role Assignment from a Person record when the qualifier data does not validate
      KULRICE-7930Person document is allowing add of role memberships with bad information
      KULRICE-9199Unable to inactivate roles of type unitHierarchy or unit from person maintenance docs
      KULRICE-11043Person document goes into exception when attempting to deactivate a Person with a single group membership
      KULRICE-7608Dynamic role membership being cached incorrectly
      KULRICE-7896NullPointerException if no role qualifier added on Person document
      KULRICE-3989UIDocumentService.loadRoleMemberQualifiers - is there a way to load qualifiers not associated with the role type
      KULRICE-4152KIM allows you to create infinite loops of role memberships
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      While working on some role membership changes we noticed that, if a role member ship is modified from the RoleDocument, it does re-queue the documents which are currently enroute. However, if we were to add a person to a role from the PersonDocument it does not re-queue the documents which are enroute.

      Looking into the code it seams like saving the person document calls UiDocumentServiceImpl.saveEntityPerson which saves all the business objects but does not re-queue the document. On the other hand, saving the Role Document calls UiDocumentServiceImpl.saveRole which has a call to KIMServiceLocator.getResponsibilityInternalService().updateActionRequestsForResponsibilityChange which in turn calls the requeueDocument.


        There are no comments yet on this issue.


          • Assignee:
            Saurabh Ajmera (Inactive)
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel