Skip to main content

ServiceNow Field Watcher on Tokyo

 ServiceNow Field Watcher on Tokyo

The ‘field watcher’ feature seems to be disabled in Tokyo

Field watcher is not supported with Next Experience in Tokyo. Details of the same can be found here - Field watcher 

However if you still need to use the Field watcher , then you have to switch back to UI16. 
You can switch back to UI16 through toggle button "Disable Unified Navigation". You can enable this by enabling the system property - glide.ui.polaris.on_off_user_pref_enabled 
Once done you should be able to use Field watcher. 

Note - Please use the above workaround in the sub-prod instance first to test and validate. 


Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue'" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object