Bug 1298968

Summary: Unable to create service dialog for element type dynamic drop down list
Product: Red Hat CloudForms Management Engine Reporter: John Prause <jprause>
Component: UI - OPSAssignee: eclarizi
Status: CLOSED ERRATA QA Contact: Taras Lehinevych <tlehinev>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5.0CC: adahms, akarol, bilwei, cpelland, dajohnso, eclarizi, fdewaley, hkataria, jhardy, jocarter, mfeifer, mpovolny, obarenbo, simaishi, tlehinev
Target Milestone: GAKeywords: ZStream
Target Release: 5.5.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
 Story Points: ---
Clone Of: 1271104 Environment:
Last Closed: 2016-02-10 15:35:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1271104    
Bug Blocks: 1235259, 1236522, 1240309    
Attachments:
Description Flags
drop_down_list none

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