Allow to test smart label on edit, and to add more criteria fields from the GUI. (as opp. to mySQL)
When creating smart labels, you can only preview the smart label when creating it. After it's been created, modification is only possible by modifying the actual SQL query. (hardly user friendly).
Also, in addition to editing a smart label, allowing additional criteria fields to be added within the GUI would help, otherwise, the user would really know how to write either MySQL RegEx or MySql queries (both of which aren't that easy for the casual user)
Thanks Pam. The new features in 6.0 have been great. I believe they addressed all but one item on this list:
the issue of previewing the results of the smart label. Currently, testing the smart label shows all the machines that would be targeted by that smart label. However, as soon as you save that smart label, it contains nothing, until the target machines perform an inventory. That doesn't really make sense, because if the KBOX can already show you a preview of the machines, that tells me that they're already in the database, so why not immediately include them in the results, and UPDATE the smart label as machines check-in.
Pam Kelly commented
I know that v6.0 does allow you to change the smart labels after they are created. The smart labels created before the update need to be recreated to use this feature.
Markus Novotny commented
Count me in; having the ability to at least confirm criteria fields, within the GUI, would be great. The ability to delete existing criteria fields and add new ones would be even better.
I agree most heartily with the comments here. The ability to add additional fields and to edit within the GUI seem to be "common sense" user friendliness!
Yes would be excellent to have more than 4 criteria fileds to base smart label on and the ability to edit in GUI would be awesome
Tom S commented
Current system makes it *very* hard for multiple admins to share smart labels, or to have persistent ones. I don't remember what I did yesterday, and using the label name still leaves lots of room for different search criteria.
A simple smart label like "Windows 7 all active" yields different results from an old label compared to what I just typed in today. Heck, the old SQL doesn't even contain the string "windows 7", so I have no idea what it's looking for.
Interesting that I landed on this page trying to find out how to edit Smart Labels. We just got our license 2 days ago and I wanted to view a label I setup in my test environment a month ago since I couldn't remember exactly how I did it. After much searching and gnashing of teeth, I gave up. And here I thought I was just too dense to figure it out...
Travis O'Neill commented
Thank god I'm not the only one wanting this. As soon as I create a smart label it becomes gibberish to me. No editing from that point on, I'm better off just creating a new one, and if its a label I created some time ago, I have no idea what I chose and am forced to start from scratch.
Brian, I completely agree with you. and I'd like to add to your comment (which is quite related), and that is, the selections of fields are limited to certain sections of the KBOX. For instance, if you create an Machine Smart Label, even if you choose the "Operating System" as criteria, you wouldn't get the same list that you would within the patching.
Ideally, it would be nice that anything that is chosen in the criteria, would get populated from the KBOX database, and available to filter through (just like you filter through asset items, inventory, users, etc ...)
One great example of this, is especially if you're trying to create a smart label for some piece of software. You sort of know what the software name is/contains, but since you're building the smart label, you want to be sure, and unless you exit out of building that smart label into a new window to double check, there is no way to filter out existing software that the KBOX is aware of.
Bottom line: Make any criteria values in the smart label to be available searching from existing values in the database.
Would perhaps make the population of new fields slightly slower, but I bet it's not as slow as having to go around to figure out the value that's supposed to be there.
Not only have the option to add more search fields but also have the option to choose more than one choice for a search criteria when specifying a type of search. For example: Operating systems. If an environment has 12 different Operating Systems in the environment and the patch label is for 2 or more but less than the whole, then from the drop down of operating systems should allow multiple selections to be chosen instead of having to edit the SQL statement or include it on another line.
One additional piece I would add, is to allow grouping of the "WHERE" section of the SQL. For instance, I would want to have a smart label that can have :
(OS = "Windows XP" AND OR OS = "Windows 7") AND Impact = "Critical"
This is only currently possible if modified within the SQL statement.
allowing additional criteria fields to be added within the GUI would help
also edit with GUI after creation as you said
I agree completely. You should be able to add fields with an "add field" button or something user-friendly. Not being able to edit the label unless you dive into the SQL is definitely not convenient. I want to get more detailed on the patch filters, but don't have time to mess with all the SQL and it's extremely frustrating. It seems like a natural feature to have included with smart labels. Please fix this.