I don't know about you guys, but having worked with ServiceNow since the pre-Fuji days, I can hardly believe how far the platform has come in just a few short years. 

If you've been following SN Pro Tips for a while, you may have seen our articles on Geneva and Helsinki. In that same spirit, today we're bringing you a break-down of what's new in ServiceNow's Jakarta release, and all the main points you'll need to know and keep an eye out for, as an Admin or developer. 
This has been another really significant update to ServiceNow, so we can't cover every little detail, but if we missed something that you think is important, please leave a comment and let us know your favorite new feature! 

Click below to read on, and learn what's new in ServiceNow Jakarta! 

If you've ever searched from the list view of a given table, you may have seen the "for text" option next to the search box in the list header.

This search box can be configured to directly search in any field which is displayed in the list view, but you can accomplish that just by clicking the "magnifying glass" icon to the left of the column headers. 

You might notice though, that this text search isn't.... very... good. For example, if you search for multiple words like "blackberry configuration", the search assumes that you want all of the words in the search to be included in any of the results returned, so results like "blackberry setup" would not be shown. 

Let's explore why, and see if there might be a better way to do this kind of text search in our scripts. 

In this article, we're going to learn about the differences between 123TEXTQUERY321, IR_AND_QUERY, IR_OR_QUERY, and - IR_AND_OR_QUERY, as well as how to use them in scripts!