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

Person document incorrectly validating "unique" attributes on role memberships

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7930Person document is allowing add of role memberships with bad information
      KULRICE-5045Change to Role membership from the Role document causes the affected enroute document to re-queue, while role membership changes from person doc does not
      KULRICE-7749Unable to inactivate Role Assignment from a Person record when the qualifier data does not validate
      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-7608Dynamic role membership being cached incorrectly
      KULRICE-11043Person document goes into exception when attempting to deactivate a Person with a single group membership
      KULRICE-4368On the Group Document, if you forget to enter description, when you submit and get the validation errors it messes up the membership list
      KULRICE-9165Person document not displaying role qualifiers
      KULRICE-4178Some role qualifiers displaying incorrectly
    • Rice Module:
      KIM
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Unable to inactivate a single role member when more than one membership for the same role exists using the Person document.

      Edit Person (in KFS-INT) using 'Name = asneed'. Inactivate one of the Role memberships by going to Role 7 and changing the 'Active To Date' field to today on only one; click Submit. Receive the following error message:

      "Errors found in this Section:
      Member documentTypeName ORG qualifier value is not unique:

      {2}
      Member chartOfAccountsCode BL qualifier value is not unique: {2}

      Member organizationCode ACAD qualifier value is not unique:

      {2}

      "

        Issue Links

          Activity

          Hide
          Shannon Hess added a comment -

          Jonathan,

          This has been fixed. Can you please bring in the latest code and verify that it now works as expected?

          Thanks,
          Shannon

          Show
          Shannon Hess added a comment - Jonathan, This has been fixed. Can you please bring in the latest code and verify that it now works as expected? Thanks, Shannon
          Hide
          Bryan Hutchinson added a comment -

          Shannon,

          I pulled in the latest Rice code into my local environment, and was able to confirm this has been fixed.

          Thanks,
          Bryan

          Show
          Bryan Hutchinson added a comment - Shannon, I pulled in the latest Rice code into my local environment, and was able to confirm this has been fixed. Thanks, Bryan
          Hide
          Jessica Coltrin (Inactive) added a comment -

          closing all 2.1.2 Jiras

          Show
          Jessica Coltrin (Inactive) added a comment - closing all 2.1.2 Jiras

            People

            • Assignee:
              Shannon Hess
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel