Changing the theme removed the borders layout on classic view

RaghuMani
Tera Contributor

I changed the value on the property 'Glide.ui.polaris.theme.custom' with the sys ID of the theme 'coral' - 'fad87d2ca304121029a4d1aed31e610f'. Everything appears fine since then whenever I open the classic view, I am not seeing the border layout wherever it used to be. Example screenshots attached.

RaghuMani_0-1769691303861.png

Image with border around each widget

RaghuMani_1-1769691382108.png

Image with the border on the activity section on an RITM in classic view.

RaghuMani_2-1769691958909.png

 

Image without the border on the activity section on an RITM in classic view after applying coral theme

 

RaghuMani_3-1769691991898.png

 

Image without border around each widget after applying coral theme

Any suggestions would be much appreciated
 

1 REPLY 1

Matthew_13
Mega Sage

Hi Buddy,

When you set glide.ui.polaris.theme.custom to the Coral theme, you told ServiceNow to use Polaris styling everywhere. Polaris does not use borders the way Classic UI does. Classic pages (dashboards, RITMs, activity streams) were built assuming those borders exist, so when Polaris takes over, they just disappear.

That’s why:

  • Dashboard widgets lose their boxes

  • The activity section on RITMs goes flat

  • Nothing is broken, it just looks wrong

ServiceNow doesn’t officially support making Classic UI look “right” with a Polaris theme. It’s basically a mismatch between old UI and new design rules.

Your options are:

  • Leave it as-is and accept the borderless look (this is what ServiceNow expects)

  • Add custom CSS to force borders back (works, but not upgrade-safe)

  • Use Polaris only for Next Experience and keep Classic on the old theme (safest if users still live in Classic)

If your users still rely heavily on Classic, the cleanest move is honestly the last one. Polaris really shines in Next Experience — Classic just isn’t built for it.

 

@RaghuMani - Mark Accepted Solution and Thumbs Up if you found Helpful