Bug 1298968 - Unable to create service dialog for element type dynamic drop down list
Summary: Unable to create service dialog for element type dynamic drop down list
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
high
medium
Target Milestone: GA
: 5.5.2
Assignee: eclarizi
QA Contact: Taras Lehinevych
URL:
Whiteboard:
Depends On: 1271104
Blocks: 1235259 1236522 1240309
TreeView+ depends on / blocked
 
Reported: 2016-01-15 14:44 UTC by John Prause
Modified: 2019-10-10 10:54 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
This update resolves an issue that prevented users from creating service dialogs for dynamic drop-down list element types by making it possible to save a DialogFieldDropDownList without values when it is dynamic.
Clone Of: 1271104
Environment:
Last Closed: 2016-02-10 15:35:20 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
drop_down_list (59.65 KB, image/png)
2016-01-25 10:10 UTC, Taras Lehinevych 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0159 0 normal SHIPPED_LIVE CFME 5.5.2 bug fixes and enhancement update 2016-02-10 20:19:02 UTC

Comment 3 Taras Lehinevych 2016-01-25 10:10:38 UTC 
Created attachment 1117897 [details]
drop_down_list
Comment 4 Taras Lehinevych 2016-01-25 10:12:39 UTC 
Failed verification. 

When you adding the drop down list and Dynamic box is unchecked you will get "Dropdown elements require some entries" error flash message. Please check attachment.
Comment 6 eclarizi 2016-01-25 16:31:47 UTC 
Um, isn't that intended behavior? If you do not have the dynamic box checked, you need to give it some values, otherwise the drop down will be blank. The original problem was that when the dynamic box was checked, it was still saying that you needed to provide values which did not make sense since it was assumed the values would be coming from the automate method.
Comment 7 Taras Lehinevych 2016-01-25 16:49:02 UTC 
Thank you for response.
My apologies, you are right. I'll change the status.

Verified fixed in version 5.5.2.2
Comment 8 errata-xmlrpc 2016-02-10 15:35:20 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:0159
Note You need to log in before you can comment on or make changes to this bug.