Skip to main content

ServiceNow Next UI: theme your instance - QUICK HACKS

note: Utah release brings in Theme builder changes which may make below steps unnecessary

ServiceNow Next UI: theme your instance - QUICK HACKS

to change the header colour:


apply it across the board:



  • go to sys_ux_style and create an entry as follows (give it whatever name you prefer, e.g. 'header UAT':


grab your own variant color code from https://htmlcolorcodes.com/

see below to copy paste code
  • go to now experience framework> themes, create a new theme, and reference the above newly created from UX Theme Styles tab

  • create new system property glide.ui.polaris.theme.custom and copy-paste the sys_id of the above new theme

apply it as a user preference:

similar steps to above, but set the sys_ux_style type to 'variant' (use insert and stay) then add it to the same theme as the core one. Log out and back in and go to user preferences> themes




other options

see the ux style 'colors' for list of options/ideas
(https://<YOUR_INSTANCE>.service-now.com/nav_to.do?uri=sys_ux_style.do?sys_id=a197a38107b03010e03948f78ad30059 )

menu color




{
    "base": { },
    "properties": {
        "--now-unified-nav_header--background-color":"51,172,255",
        "--now-menu--background-color": "51,172,255"
    }
}

sidebar color




{
    "base": { 
       
    },
    "properties": {
        "--now-unified-nav_header--background-color":"51,172,255",
        "--now-menu--background-color": "51,172,255",
        "--now-unified-nav_menu--background-color": "51,172,255"
    }
}

revert back to default

just blank the glide.ui.polaris.theme.custom sys property


revert back to default - with variants

the following theme achieves this, reference its sys id in the above property









(it should remember the variant selection next time you log in)



(ServiceNow )






Comments

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...