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

Using Person Lookup with First Name or Last name only looks at the "Preffered" name instead of the default

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-3814Person Lookup ignores names' default field
      KULRICE-7643DTOConverter#convertWorkflowAttributeDefinition only looks for a definition by name now
      KULRICE-4561Indicate First Name and Last Name are required on Person document
      KULRICE-4603Person: Cannot use hyphenated last name on the Person doc - receive error that only letters or digits may be used. Also prevents the addition of roles if a person comes into KIM via LDAP with a hyphen.
      KULRICE-4364Person Lookup when seeded with Last Name shows duplicate entries (same person two times with same info on both lines).
      KULRICE-4213Allow principal names in Kim screens instead of only principal Ids
      KULRICE-1478Research JPA Naming Defaults
      KULRICE-4019allow header block to show initiator person name instead of principal name
      KULRICE-12360Display name formatting issue when middle or first name missing
      KULRICE-4132remove default admin name from dummy_login.jsp
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently, the Person Lookup will only look at a person's name for the lookup if the name is marked as default and has a nameType of Preferred. Judging by the way the rest of the lookups work, it should only be looking at the default name, even if this has a different nameType.

      The problem with this is that this "preferred" criteria was put into place due to a problem where the same entity was being returned multiple times if the person had two names that matched the name search. The reason for this is that there is a mismatch in the getter and setter names in the KimDefaultableEntityDataBase class. The variable in this class is 'dflt', but the getters and setters are isDefault(), and setDefault, so when reflection is used, to set the criteria, it says the variable isn't writable, and drops that criteria. This looks like it is already fixed for rice 1.1, but I'm thinking we might need to fix this in 1.0.3 or one of its derivatives.

        Activity

        Hide
        Eric Westfall added a comment -

        Jeremy will put in the fix so that the person lookup uses default name instead of preferred name, and then he will ask William to re-test.

        Show
        Eric Westfall added a comment - Jeremy will put in the fix so that the person lookup uses default name instead of preferred name, and then he will ask William to re-test.
        Hide
        Jeremy Hanson added a comment -

        Changed this to have isDflt() and setDflt() methods. removed the criteria for "Preferred"

        Show
        Jeremy Hanson added a comment - Changed this to have isDflt() and setDflt() methods. removed the criteria for "Preferred"

          People

          • Assignee:
            Jeremy Hanson
            Reporter:
            Jeremy Hanson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel