Description of problem:
From bz 1540273:
Brant Evans 2018-02-05 17:20:04 EST
I think that is related to how the tag category is defined. A tag category has "Single Value" property. If set to true then only one value from that tag category can be assigned. If it is false then any number are able to be set.
The dialog element for a tag control sounds like it is working as I'd expect. If the category has "Single Value" set to true then a drop-down is displayed that only allows selecting one value. If set to false then the dialog element allows selecting multiple values.
"department" category has "Single Value" set to false. "environment" has "Single Value" set to true.
If there is a property that the user cannot change, don't display a switch that seems to be able to do so.
Right now, when the user sets the Single value switch to false (where not appropriate), it works without warning and the element and dialog can be saved. The switch is however ignored and single value dropdown is present in the dialog.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Navigate to Automation -> Automate -> Customization; Service Dialogs; Configuration -> Add a new Dialog
2. Add the Tag Control item to the new Dialog
3. Edit the Tag Control item; in tab Options:
- for Category select Environment
- set the Single value switch to No
5. Save the dialog
6. Observe single value dropdown
Single value dropdown displayed when Single value set to No
Don't display the Single value switch when it doesn't do anything
New commit detected on ManageIQ/ui-components/master:
Author: Roman Blanco <firstname.lastname@example.org>
AuthorDate: Wed Aug 22 09:56:06 2018 -0400
Commit: Roman Blanco <email@example.com>
CommitDate: Wed Aug 22 09:56:06 2018 -0400
Hide 'Single Value' checkbox if it is not applicable
src/dialog-editor/components/modal-field-template/tag-control.html | 3 +-
src/dialog-editor/components/modal/modalComponent.ts | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
Verified in Version 188.8.131.52.20181023151612_4c11b0d
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.