Next Experience - San Diego instance with Polaris enabled, global search is showing Bad Request 400 errorDescriptionIn San Diego on an instance with Polaris enabled, global search is showing Bad Request 400 errorAfter upgrading to San Diego and activating Polaris a user is trying to do a global search but they are getting a Bad Request 400 error. Console errors are seen in the console. Images attached. The user is able to search for a record and it will show the record. But when they search a term they get the error. The expectation is to see a search result page like in Legacy search.From this apge it works fine even in Polaris./nav_to.do?uri=%2F$sn_global_search_results.doIf the user is given the agent_workspace_user role the issue is resolved. But this means all users must have this role to get the search result page in Polaris. The legacy search result page works fine.Steps to Reproduce Login to any San Diego instance and enable Polaris experience by setting property glide.ui.polaris.experience = truecreate a new role and add role to global search propertyglide.ui.can_searchGive this new role to Abraham lincoln.Do search from global search- notice bad request 400 error Expected - Search should give you results. Actual - It gives bad request 400 error.WorkaroundThis issue is under review. If you are experiencing this problem, contact ServiceNow Customer Support.Related Problem: PRB1563403