Enable/Disable Next Experience UI (Tokyo) oddness

[ericgilmore]

Here's a wrinkle for you.

I implemented this in my Dev & Test instances;

• System Property: glide.ui.polaris.experience | true
• User Preference: glide.ui.polaris.use (System checked, No user specified) | false

I then copied glide.ui.polaris.use, unchecked System, and added my account to the User field.

What I wanted was to enable NextExpUI for myself and leave it disabled for everyone else. I did this in my Dev & Test instances.

The results?

- Dev works as expected. If I impersonate anyone else, their environment looks like UI16, cool.

- Test no sir, not working. If I impersonate anyone else, their environment looks like the Next Experience.

What gives? Has anyone else run into this?

[AnveshKumar M · Accepted solution]

Hi @ericgilmore ,

Check these two articles, which I followed some time back. They worked for me.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117832 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1113554 

[ericgilmore]

Well, this seems to have cleared itself up. I went back and tried the same setup today and voila! Shes working captain.

There was one more thing I did. I added a toggle under Preferences (gear icon in UI16, avatar - Preferences in Next Exp UI) that allows one to toggle between UI16 and the Next Experience UI.

ref: ServiceNow SANDIEGO POLARIS View || Enable Disable for Instance and user level || shift b/w UI's