Does anyone else find Service Operations Workspace slow?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2023 01:11 AM
Hi All
We have recently moved to Utah switching on the new UI and also moving to the new Chat tool.
Our main Service Desk is outsourced supporting over 45,000 customers around the world and in all of their 5 locations they complain that compared to call module the system is intermittently very slow and hampering their ability to support our customers.
ServiceNow have been supporting us but so far nothing has made a major difference and we are a month in...
I just wondered if anyone has or is experiencing the same before we start engaging network teams etc.
Sally
- 5,884 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 10:58 AM
To those of you who have upgraded to Vancouver, is the performance of SOW improved? Anything new to report?
We'll be upgrading to Vancouver next week and will implement SOW and the new UI (Next Experience) later this year. Appreciate any input you can provide. Thanks.
Susan Williams, Lexmark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 01:57 PM
We have noticed improvements moving to Vancouver. It is important to stay as up do date as possible, lagging behind too much will have a negative effect on performance from what we experienced. By going into the latest version which was Vancouver we were able to improve page load delays (Details tab, User record), forms not loading (Interaction coming by way of chat), tabs out of place, Home page loading slow, etc..
We also found a few other things you can look into to improve speed and performance. Give some of these a try.
1. Improve list and record page loads check and disable any unused sys_ui_scripts - we had some that were not used in workspaces/sow and were slowing things down
2. improve sow home page load - deactivate the recently viewed SNC feature within the sys_ux_screen table
3. Improve list loads - disable the list count for large tables like cmdb, task, etc. (glide.ui.list.seismic.omit.count)
4. improve CI field search within incident and request forms - check n improve your queries
5. Land on another page other than Home page (its the slowest page due to the widgets) - you can load to the List for example [ we didnt do this but somethign to think about ]
6. remove some of the widgets from the home page - if your not using them why load them
7. If the catalog page loads slow when trying to create a new request - lower the amount of categories and/or popular items shown
Last but not least understand that SOW is its own space, many of the things you customized or even just configured within the classic space will not just place nice in the SOW space. We had to go back and completely survey our configurations and customizations and tweak them to some degree to improve performance. ServiceNow did help us but most was on us. We now are in a better place and our stakeholders are happier. But, we had to dig in and learn how to maintain and configure workspaces. Its a skill set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 12:55 PM
We are on Utah still and i have found that while there is no specific answer, these problems largely seem to have gone away. Presumably due to patches done on SN side

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2024 03:13 AM