- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 08:44 AM
All,
Good afternoon. Our client has requested that we change the default asterisk color from red to blue. This red to blue asterisk color change must apply to all forms that have required fields.
I navigated to System Properties >> CSS and updated the value of the "Mandatory field status indicator color (unpopulated):" from #cc0000 (red) to #0000ff (blue).
After saving my changes, the asterisk still appears red and not blue.
To ensure my changes were made, I navigated to sys_properties.list and found the "css.label.mandatory.background.color", and verified that the value was indeed changed to #0000ff.
We are on the Helsinki release. Is there another place where the value need to be updated to make the red asterisk for required fields turn blue?
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 12:22 PM
ANSWER TIME!
Right now I'm just shaking my head at the answer provided by the ServiceNow support. Here's a copy of what they provided my coworker:
Worked with ServiceNow support on that one. What I was told is that the CSS module settings no longer are used on the latest versions of the UI. Initially I was told the UI no longer supports that change (was given a potential way to script it but also told upgrades could be an issue if I did it), but when I pressed them they came up with a solution to add an entry to the system properties (sys_properties) table. The steps were:
1) Navigate to system_properties.list in the filter navigator.
2) Search for entry css.$color-negative. It's probably not there, if so create a new one with this name. Type is String and value is the hex code of the color you want, I used #0000ff.
3) Save and it takes effect immediately.
Not too obvious and the support person didn't know about it at first...so far as I can tell that isn't documented anywhere. Who knows what other css variables are out there. But, it's probably reasonably safe from upgrade issues since it is not defined explicitly by default.
Fun times...as an FYI, here's what was created to make the asterisk appear blue:
davidd., tagging you on this answer. Cheers and thanks again for your help sir.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 11:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 11:45 AM
Yeah, I'm shrugging with you too davidd.
Shouldn't be this hard to make a simple color change. Right? 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 12:22 PM
ANSWER TIME!
Right now I'm just shaking my head at the answer provided by the ServiceNow support. Here's a copy of what they provided my coworker:
Worked with ServiceNow support on that one. What I was told is that the CSS module settings no longer are used on the latest versions of the UI. Initially I was told the UI no longer supports that change (was given a potential way to script it but also told upgrades could be an issue if I did it), but when I pressed them they came up with a solution to add an entry to the system properties (sys_properties) table. The steps were:
1) Navigate to system_properties.list in the filter navigator.
2) Search for entry css.$color-negative. It's probably not there, if so create a new one with this name. Type is String and value is the hex code of the color you want, I used #0000ff.
3) Save and it takes effect immediately.
Not too obvious and the support person didn't know about it at first...so far as I can tell that isn't documented anywhere. Who knows what other css variables are out there. But, it's probably reasonably safe from upgrade issues since it is not defined explicitly by default.
Fun times...as an FYI, here's what was created to make the asterisk appear blue:
davidd., tagging you on this answer. Cheers and thanks again for your help sir.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2017 01:05 PM
"Font size for the header" (css.nav_header.font-size) doesn't work either, no matter what you changed it to (percent/pixels, etc) since UI16. I have a post about it somewhere. Your answer is interesting. What I didn't realize is I can right click on the property title and "edit property", not that it helps, but hey, I can get to the system property - I wonder what the new system property is that I should create that will allow me to change the header font size. We don't even care anymore at this point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 06:20 AM
Wow... I too am shaking my head at the ServiceNow response, "the CSS module settings no longer are used on the latest versions of the UI". My question to them... Why the deception in having the settings if they are invalid!
Anyway... (takes a few deep breaths), thank you for posting the answer. Hopefully we don't run into many more of these types of cases.
