"GO TO" list search properties and what to expectIssue This article explains the behavior of the list "Go To" search box in ServiceNow and how two system properties—glide.ui.goto_use_starts_with and glide.ui.goto_use_contains—influence search results. The Properties glide.ui.goto_use_starts_with [ true / false ]glide.ui.goto_use_contains [ true / false ] Note: These properties are not created by default. You must define them manually in System Properties (sys_properties).ReleasePre-New York Releases: Affects the "Go To" search box at the top of list views.New York and Later: Applies to the updated search field shown in modern list views.ResolutionWhat they do To test, searched the word "node" in the "Name" field on the Business Rules (sys_script) table: Greater than or equal to (>=) search: glide.ui.goto_use_contains = falseglide.ui.goto_use_starts_with = false Servicenow Encoded Query: GOTOname>=nodeSQL: SELECT ... FROM sys_script WHERE `name` >= 'node' Contains (*) search: glide.ui.goto_use_contains = trueglide.ui.goto_use_starts_with = false Servicenow Encoded Query: GOTOnameLIKEnode SQL: SELECT ... FROM sys_script WHERE `name` LIKE '%node%' Starts with (^) search: glide.ui.goto_use_contains = falseglide.ui.goto_use_starts_with = true Servicenow Encoded Query: GOTOnameSTARTSWITHnode SQL: SELECT ... FROM sys_script WHERE `name` LIKE 'node%' Mystery all true search: glide.ui.goto_use_contains = trueglide.ui.goto_use_starts_with = true It just uses the contains search. Edge cases: true/false field:enter "TRUE" or "FALSE" Converted to 0 or 1 respectively but uses the same operators documented above. (This can result in true returned for false in the greater than default search) Define only one of the two properties (contains or starts_with) to avoid ambiguity.Test search behavior in a sub-production environment before deploying changes.Document custom search behavior in your internal KBs for consistency across teams.Related LinksReference Documentation: Configure Default Search Behavior in a List Simplify Queries with Encoded Queries