How to clean browser cache every time when we are impersonating with another user?

[JayD1]

Hi Experts,

As i am working in service portal and there is an intermittent issue occurring, explained below:

when I am testing widgets in portal some of the widgets is not visible to the intended users(we have used user criteria to restrict access)

once I am cleaning the browser cache I am able to see the widgets which I am supposed to see.

why this issue is happening and do we have any way to clean the browser cache every time when we are impersonating with another user. 

any help would be appreciated.

Thanks,

joe

[Alberto Consonn]

Hi Joe,

it might be useful the following blog article which explain how and when it is needed to clear the cache:

https://community.servicenow.com/community?id=community_blog&sys_id=81ada2a9dbd0dbc01dcaf3231f961913

If I have answered your question, please mark my response as correct and/or helpful.

Thank you very much

Cheers
Alberto

[JayD1]

Hi Alberto,

Thanks for your quick response, I was referring to the post and that is more about the server cache clean up, but the thing is we need to clean up the browser cache.

for instance :

when I impersonate as X user I should be able to see a,b,c widgets but i can't,now as I clean my browser cache and I impersonate as X i can able to see the widgets.

do we have any option to clean the browser cache from ServiceNow or we have to do it manually?

 why this issue is happening? will it impact the prod instance.

Thanks,

Joe

[Alberto Consonn]

Hi Joe,

as far as I understood, you're doing some testing using the impersonation feature, which is good. However, it's always best practice to try testing also using an incognito browser window and do the login with the end-user credentials instead of use the impersonation, it's more safe cause you can avoid any possible cache issue. 

By the way, in production there shouldn't be any issue, however before migrate to production ensure to test it in another instance (i.e test or preprod) using the login flow.

Hope this can help you.

Cheers

Alberto

[JayD1]

Just out of my curiosity I want to go little deep and trying to understand how can I be so sure that this issue will not happen in production?

suppose in production we have small issue occurs for any specific user and to check that issue we have to  check by impersonation.what we can do , please advise.