ITIL User Sees Blank Page in Service Operations Workspace

Nofarec
Tera Contributor

‎08-07-2025 12:28 AM

Hi everyone,

I have a user with the ITIL role who up until a few days ago, was able to access and view incidents, requests, and catalog tasks in the Service Operations Workspace. However, recently the workspace appears completely blank to him with blank content of the records. There were no changes to the user’s roles before this issue began.

Nofarec_0-1754551672555.png

 

Has anyone encountered this issue or have suggestions on how to resolve it?

Thanks in advance!

0 Helpfuls
  • 291 Views
3 REPLIES 3

Dr Atul G- LNG
Tera Patron
Tera Patron

‎08-07-2025 06:56 AM

It looks like a cache or role issue.
Try the following steps:

  • Assign the ITIL role.

  • Apply the SOW-specific role to ITIL user as well.

  • Also, repair the SOW plugin.

  • Then, log out and log back in.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Nofarec
Tera Contributor
In response to Dr Atul G- LNG

‎08-10-2025 06:20 AM

Hi, thank you very much for your answer.
The user tried everything you mentioned, but it seems that the only thing that actually solved the problem was resetting the browser. I’m adding this comment to highlight that clearing the cache probably isn’t enough.
Thanks again for your help!

0 Helpfuls

Nofarec
Tera Contributor

‎08-10-2025 06:21 AM

Hi, thank you very much for your answer.
The user tried everything you mentioned, but it seems that the only thing that actually solved the problem was resetting the browser. I’m adding this comment to highlight that clearing the cache probably isn’t enough.

0 Helpfuls