Is there a way to hide the HTML field editor toolbar on just one form?

bnine · ‎02-17-2016

I know that you can go into System Properties > UI Properties and edit the 'Configures the editing toolbar' sections to choose what show up, but it looks like this will affect other parts of the system instead of just the app I am working in.

We only want to remove it on one form for now. Right now I have this HTML field being populated with the contents of the KB article being attached to the ticket, and we are going to be sending the contents of the field to the caller in an email, and we want the user to be able to see what it will look like. (I had used the regex .replace() scripts floating around here remove the HTML tags that came up when the KB contents were copied into a regular string field in plain text, but that was inadequate). I think this is the

Is there a way to do this, maybe with a client script?

P.S. I have just over a month's worth of experience with ServiceNow, so let me know if I am posting this in the wrong place or something

ahaz86 · ‎02-17-2016

First thing that comes to mind is an on load client script.

function onLoad() {

   var sheet = window.document.styleSheets[0];

   sheet.insertRule('.mce-toolbar-grp { display: none !important; }', sheet.cssRules.length);

   sheet.addRule('.mce-toolbar-grp ', 'display: none !important;', -1); // IE likes to be different

}

Give that a shot

View solution in original post

geoffcox · ‎02-24-2016

Whenever we have an html field that is calculated, I set it to "read only" in the dictionary so that the user cannot interfere with its contents. This also effectively hides all the html editor widgets too.

dmfranko · ‎03-15-2016

Doesn't appear to work this way in Geneva anymore .

geoffcox · ‎03-16-2016

Works fine in my dev instance, which is on Geneva.

dmfranko · ‎03-16-2016

How about for a catalog item? Looks like you might be in an incident or something.

geoffcox · ‎03-18-2016

Ah, if you want to put some read only html into the catalog item (such as with a record producer), you can choose "ui page" as the variable type.

I tried this on the dev instance.