Bug 1311308 - <Choose> Won't Display on Refresh of Dynamic Dropdown
Summary: <Choose> Won't Display on Refresh of Dynamic Dropdown
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Martin Hradil
QA Contact: Shveta
URL:
Whiteboard: ui:dialog
Depends On:
Blocks: 1312049
TreeView+ depends on / blocked
 
Reported: 2016-02-23 21:42 UTC by Dustin Boyd
Modified: 2016-07-12 18:45 UTC (History)
10 users (show)

Fixed In Version: 5.6.0.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1312049 (view as bug list)
Environment:
Last Closed: 2016-06-29 15:39:14 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Dustin Boyd 2016-02-23 21:42:25 UTC
Description of problem:
I have <Choose> set as a value if the hash is nil. <Choose> shows on initialization, but when it refreshes and redoes the ldapsearch, it goes to a blank value. The value <Choose> is in the hash in the logs when you log the inspect. I change the value to -Choose- and it is shows fine on the refresh without issues. I tried / \ REGEX escape values to no avail. It will escape and show the escape characters with the rest of the value.

Version-Release number of selected component (if applicable):
5.5.2.4.20160127105142_395c086

How reproducible:
Every time it refreshes after initialization.

Steps to Reproduce:
1. Create a dynamic dropdown with automate code that has <Choose> as the nil value of a hash
2. Create a service dialog to use this dynamic dropdown and have it set to auto refresh
3. Try to create a service with this dialog and allow it to auto refresh

Actual results:
Initializes 1x fine, but subsequent auto refreshes change the displayed value to blank.

Expected results:
The dynamic dropdown shows <Choose> as the default value when sorted alphabetically in the hash.

Additional info:
self_service UI shows the value fine, but the old Service Catalog doesn't display correctly.

Comment 3 Dustin Boyd 2016-02-24 19:52:48 UTC
Dan, required is taken away when I select dynamic. I have dialog_field["required"] = "true" in the automate code. Do I have to set it ahead of time before I create the element like I do when it gives me the error of "cannot create without initial values" and then go back and make it dynamic?

Comment 4 Dustin Boyd 2016-02-24 20:02:52 UTC
Dan, I changed it from dynamic to traditional and saved it with the true value. Changed it back to dynamic with the same automate code underneath. No change since I toggle it between dynamic to traditional and it appears false underneath the dynamic every time I toggle it. It seems like more of a < > issue than anything since I can put gnandndindand between < > and it's a blank value.

Comment 5 Harpreet Kataria 2016-02-25 14:52:17 UTC
Martin,

This issue appears to be fixed in commit 30e5964f0f7a461aecee5f7e6a06e07466f5b7f5 on upstream master, i am not sure if all the changes in that commit are safe to be cherry-picked on to 5.5.z so sending this ticket your way to cherry-pick changes appropriately. Let me know if you have questions.

Thanks,
~Harpreet

Comment 7 Shveta 2016-04-19 18:00:49 UTC
Fixed.
Verified in 

5.6.0.1-beta2.20160413141124_e25ac0e

Comment 9 errata-xmlrpc 2016-06-29 15:39:14 UTC
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


Note You need to log in before you can comment on or make changes to this bug.