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

Results from person lookup should be bounded by default like it is in Rice 1.x


    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.1.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-7483make doc search work like other lookups in terms of result limits
      KULRICE-5727Create a Rice 1.x environment for validation, etc.
      KULRICE-4750Using Person Lookup with First Name or Last name only looks at the "Preffered" name instead of the default
      KULRICE-2717can't edit person from "edit" link in lookup result list
      KULRICE-7780Doc Search: Results set initiator column no longer an active link to inquiry
      KULRICE-3814Person Lookup ignores names' default field
      KULRICE-7223Multivalue lookup not returning results
      KULRICE-5341UserSession gets bound to a thread, and eDocLite documents are not establishing user session properly
      KULRICE-6620Role Inquiry does not contain the information present in Rice 1.x
      KULRICE-3662Message Properties aren't getting loaded from KEW ApplicationResources.properties for KEW lookup screens (like doc search)
    • Rice Module:
    • Application Requirement:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      Currently in KR 2.0, the person lookup is not bounded and doing a lookup with no criteria results in the memory on the server being maxed and eventually crashing the server (At IU due to the amount of data in the KRIM tables)


        There are no comments yet on this issue.


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


            • Created:

              Structure Helper Panel