Details
-
Type:
Bug Fix
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-10397Allow for callback methods for quickfinder (lookup) returns KULRICE-8651 There 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-12995 Rice 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-7067 Inquiry 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:KRAD
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
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.
Activity
Eric,
Please create a test case for this in the configuration test view.
Jerry
Test case created in the configuration test view with different configuration options for readOnlySearchFields and it appears to be working ok.
The test page is not quite right; it will succeed, but it doesn't really test the issue.
Another developer corrected this issue. I adjusted the test to properly demonstrate the issue. If one quickfinder had an option that the second did not, the option from the first would persist.
Here is the code I tried to clear the action parameters:
jq("#kualiForm").ajaxSubmit({
success: function(data) {
// Add the returned URL to the FancyBox href setting
options['href'] = data;
// clear out hiddens
jq("#formComplete").html("");
// Open the light box
{ jq.fancybox(options); }if (top == self)
else
{ parent.$.fancybox(options); }}
});