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

Issue when two quickfinders on same view have different lookup configuration


    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m4, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-10397Allow for callback methods for quickfinder (lookup) returns
      KULRICE-8651There are two services that serialize BOs to XML and they have different configurations
      KULRICE-12021Kim Attribute problem when multiple attributes have the same name
      KULRICE-12435Some quickfinder lookups are broken
      KULRICE-12995Rice Spring Configuration issues
      KULRICE-5324When multiple components have same bean definition in dictionary they get the same id assigned
      KULRICE-1799Figure out how to handle the potential conflict of having two different documents saving to the same join (i.e. group membership)
      KULRICE-7067Inquiry widget does not have properties for viewName and viewId like quickfinder
      KULRICE-4364Person Lookup when seeded with Last Name shows duplicate entries (same person two times with same info on both lines).
      KULRICE-5686Need the ability to configure results limits differently for different lookups
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      When you have two quickfinders on the same view, and one has different configuration than the other (for example, assume the second one sends in readOnlyfields), the settings are not cleared after each one is invoked.

      If you click the first quickfinder which has readOnlyFields set, then close and click the second one which does not, the readOnlyFields are still sent. I thought this might be because the action parameters are not getting cleared out between the lightbox invocations. However I tried clearing them (by clearing the formcomplete div) and that didn't fix the problem.



          • Assignee:
            Matthew Wuertz (Inactive)
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel