- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2023 12:28 PM
Hello Everyone,
I'm attempting to test something in my developer instance before I make any changes in any of our instances. The problem is I don't see the option to modify the "Service Operations Workspace" in my developer instance or in our companies dev instance. Both instances are on Vancouver Patch 2 Hotfix 1. I noticed that they are showing security constraints when I go into UI builder, and I assume this is why I'm not seeing it.
However, I've quite literally given myself every available role in the instance so to get around the problem, but this was unsuccessful.
In a completely different company instance, I can see "Service Operations Workspace" in UI builder. This instance is still in Tokyo but has the Next Experience UI enabled. Any thoughts on what might be going on here?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2023 09:27 PM
Can you just click on the Display Name header and sort it. Check if that shows your workspace. check the image.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2023 09:27 PM
Can you just click on the Display Name header and sort it. Check if that shows your workspace. check the image.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2023 11:08 AM
I've seen a lot of dumb things working in IT, but this might take the cake. lol - Thank you for the help on this one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2023 08:14 AM
I was having the same problem as you and @Dibyaratnam's solution worked for me. Still super surprised that did the trick...seems like a bug in ServiceNow. If you toggle any of the headers it loads the hidden workspaces. Might be worth submitting an issue for that, but for now, props to @Dibyaratnam for the workaround!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2023 10:49 AM
Glad it worked!😀