Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Steps : create a dialog with two dynamic drop down and auto-refresh checked for both. Create a service that uses this dialog Order service , dropdown shows "None" in values. Press "refresh" and values are loaded and displayed . Build : 5.5.3.2.20160318152106_92d2d67
Created attachment 1141930 [details] No values Also, selecting value in first drop down does not auto-refresh values in second drop down .On hitting "refresh " again corresponding to first dropdown are displayed.
Created attachment 1141931 [details] one
Created attachment 1141932 [details] two
This issue seems very similar to a combination of both of these: https://bugzilla.redhat.com/show_bug.cgi?id=1321352 https://bugzilla.redhat.com/show_bug.cgi?id=1311306 Are we sure that this is a separate issue?
Nevermind, I just realized that the above two BZs are related to the SSUI and this is not. Shveta: Is the "load values on init" checkbox checked for both of these dialogs?
No , "load values on Init" was not checked . so one issue is resolved . It does load value when that checkbox is checked. But the values are not auto-refreshed in second dropdown when some value is selected in first dropdown.
Ok, I think that second issue I reproduced the other day and wasn't related to any BZ before. I think this PR should fix it: https://github.com/ManageIQ/manageiq/pull/7696
I think I was incorrect again on that previous PR. *This* one should've be the fix: https://github.com/ManageIQ/manageiq/pull/7661. I think what was happening for you was that the first drop down was triggering the auto-refresh but it was happening simultaneously with the actual server update of that drop down. Going to mark this as POST for now since I can't reproduce on the latest.
Fixed. verified in 5.6.0.4-beta2.3.20160421172650_719e256
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348