Does anyone else find Service Operations Workspace slow?

sallyf-zurich
Tera Contributor

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

58 REPLIES 58

Not 100% sure what you mean by new UI or Classic. We were using the Service operation workspace both before (Sandiego) and after. I think it was slow and laggy before, but gotten much worse.

I do not see the issue in the platform view (Classic?)

Sorry what I meant by this was with Utah we rolled out a new User Interface so SNOW looks a little different - we call that the new UI and the old view we have always had the classic UI. We where led to believe you needed the new UI to take advantage of some pro features but I'm yet to find out exactly what. Regardless SOW is the issue here I believe not the ServiceNow UI.

pickonet
Tera Contributor

We recently implemented SOW and it is intermittently hanging, freezing. Staff have lost complete interactions. I heard that a standalone installer is available for SOW, is this true? would it be worth using the application instead of the web version? 

How interesting, it has been causing us intermittent pain for close to 3 months now and while we have seen slight improvement in recent weeks due to a number of changes and patches it can still freeze randomly which for the Service Desk agents is far from ideal. I'll ask about the standalone installer at my side and see what my ServiceNow team can find out.

To me a standalone application does seem a backwards step, as most aplications are moving to HTML5 these days to allow for flexibility.

My gut feeling is there is some client side JS that is causing issues, but no idea how to find or troubleshoot that.