Red Hat Bugzilla – Bug 536437
Improvements to the DynaGroups Wizard
Last modified: 2009-11-10 16:22:54 EST
This is an additional set of improvements that didn't make it into the first version of the wizard.
4) "expression type" drop-down always makes the first expression "resource.type.name = Apache HTTP Server", it should either be null until one is selected or it should default to the first item in the "resource type" drop-down that gets generated after selecting the appropriate plugin
5) enablement / disablement options
5a) when "resource type" drop-down is an empty list, replace it with the printed message "there are no types defined by the selected plugin"
5b) when "property names" drop-down is an empty list, replace it with the printed message "there are no properties defined by the selected type"
6) user intuitiveness - similar to, but more direct than enablement / disablement options
6a) maybe only populate the "defining plugin" / "resource type" drop-downs with elements that are known to have resource types that have properties - this would be a complete replacement for options 5a & 5b
rev2545 - dynagroup expression builder improvements for items 5a & 5b
example for 5a) Resource > Resource Type > Database > "None defined for selected plugin" > "No type selected"
example for 5b) Resource > Resource Type > Apache > Apache HTTP Server > "None defined for selected type"
#4 does not seem to be an issue anymore. although Apache/Apache HTTP Server combo is the default value (but is readonly), the definition plugin and resource type drop-downs seems to properly "stick" to their previously selected values as various other combinations of elements are selected around them.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-787