Skip to main content

ServiceNow New in Tokyo

Tokyo user interface:

 Tokyo top features

Translated notifications

o Static translation

o Dynamic translation

App engine

o New tab for managing flows in table & form builder

o Formula builder: use predefined formulas to calculate the value of the column without having to write a script

o Template auditing: share templates with user/group

o Under logic and automation, new email notification builder: create event-based emails that can be also triggered from flows

o Brand new app engine management center (ServiceNow Store): to provide admins with central hub to see all their deployed apps, their usage, request for dev access, where the apps are in their pipeline between environments

UI Builder enhancements

o New condition builder with many configuration options: predefine a query, exclude fields you prefer not to show. Condition builder now added to list component

o New form component which adds user presence so we can know if anyone else looking at/editing same record

o Update to tabs component: conditionally display tabs and adjust orientation of tabs

New service portal features

o Can now display the language picker for unauthenticated guest users

o Can also pass language to the url via the lang parameter

o New sitemap generator plugin (ServiceNow Store): available to help with SCO and getting all your portal pages indexed by search engines

o Smaller updates

Tiny MCE wysiwig editor upgraded to latest version

Service portal dashboard deprecated & replaced by user experience analytics

Employee center now default portal for new instances

Servicenow server side javascript engine upgrade (ECMAScript 2021, feature rollup of ES6 through ES12)

o Currently only available for scoped apps

o Extra features such as let, const

o Template strings/literals

o Support for arrow functions

o Destructuring

o Map objects


(Courtesy of NewRocket   )


(ServiceNow )


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