- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2023 10:49 AM
We recently upgraded to Tokyo and are in the middle of configuring the Service Operations Workspace, but there is differing behavior with the Global Search feature between our TEST and DEV instances.
In DEV you can search globally.
In TEST you can only search the workspace.
We've looked at any and all configuration differences but cannot find one.
Not sure if this is possible due to a skipped script or corrupt upgrade. Need some assistance to point us in the right direction. Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 12:09 PM
I was able to resolve my issue using the following link: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1537094
You have to enable 'Multiple Experiences' for the UX Parent Application 'Unified Navigation app shell'.
This allows the drop-down to choose from, but you can also use TonO's suggestion above. This allows you to default to only Global.
Thank you all!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 09:25 AM
You should have an option to change where you search. You just need to click the triangle at the end of the search field:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 09:32 AM
Hey Michael,
Unfortunately I do not have that option there, in either instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 10:31 AM
This page explains how to configure the workspaces to allow them to be searchable https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/search-administratio...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2023 08:52 AM
Hi Jeffrey,
Did you ever get this issue resolved? We are experiencing the same exact issue after receiving Utah Patch 4 Hotfix 2b.
Thanks,
Greg