As an LF and WF administrator I love advanced search syntax when I need to use the NOT operator (-) to exclude entries from my searches but my end users struggle with learning advance search syntax. Also advanced search syntax can require more time to build a search query vs the regular search UI. It would be helpful if the normal search UI could be used to do inclusive and exclusive searches on field values or folder paths for example.

One idea is if there was a way to toggle a search field from being an inclusive search field to an exclusive search field via a button. The drawback to this would be if you wanted to use the same field in both the inclusive and exclusive search criteria. That could be remedied if there was the ability to have the normal inclusive search pane and a button to turn on an additional search pane for exclusive search criteria and the search results would be the combination of the two search panes like you would get in an advance search using {Search Criteria1} - {Search Criteria2} format.