ServiceNow Blog

ServiceNow Robust Transformer Engine (RTE) changes - Tokyo  see: https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/import-sets/concept/etl-definition-overview.html note that you now have to dotWalk for reference fields, which is a change from San Diego: note also the following: There is a new UI policy introduced "require path when table is defined" in Tokyo version , which Path will be mandatory when table name is not empty. On San Diego: Specify the table name for an import entity because there is no UI policy to make Path field as mandatory. On Tokyo: Don't need to specify both the table name and Path name for an import entity because that UI policy is introduced, system will automatically create the import set table for import entity. you can clear the table's cache by running the below script from Scripts -Background. GlideTableManager.invalidateTable("x_cls_clear_skye_i_account"); From ServiceNow: - under "Target ent

 ServiceNow Clear a Table Cache see  https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1124100 background script: GlideTableManager . invalidateTable ( "x_cls_clear_skye_i_account" ); GlideCacheManager . flushTable ( "x_cls_clear_skye_i_account" );

 ServiceNow Track Changes to a Field If the field is audited , you can get information from the sys_audit , when the value is changed and by whom.    Note that ServiceNow also have access to db_log but the local admin typically won't have access

 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.  

  ServiceNow get the application scope name in script gs . info ( gs . getCurrentScopeName ()); see also: https://developer.servicenow.com/dev.do#!/reference/api/tokyo/server_legacy/c_GlideSystemAPI#r_GS-getCurrentScopeName

 ServiceNow How to Upgrade your PDi https://www.youtube.com/watch?v=rRSoGDXSThY&t=8s

 ServiceNow UTAH release highlights catalog builder with next experience UI look and feel item designer to be deprecated next experience / UI builder accessibility (1000 fixes) dark theme lists forms dashboards/widgets knowledge service catalog virtual agent client VTB landing page Theme builder build next experience themes match your .org brand favourites grouping enables users to group their favourites together create new custom groups multi-menu filtering click=auto focus on the filter find options from other menus (under ALL RESULTS) History detail show workspaces and custom UI pages in the history ex: VTB upgraded instances, set system property glide.ui.polaris.history.recording=ALL (for instances upgraded to UTAH - this is set by default on new instances) Duplicate content and right-click menu save time hot keys includes properties, styles and events Experience view overlay to UI builder and visual editor center of configuration map of the universe customisable product notificati

ServiceNow Setting the Timezone in the Instance  Log in to the instance using an admin account Navigate to:  System Properties > Basic Configuration Scroll to the  System timezone for all users unless overridden in the user's record  heading From the pull-down menu, select the appropriate timezone value you would like to set as the default for the instance (i.e. US/Pacific). If you notice that the current value is "System", this indicates that the time zone is the default time zone from the server. Save as per link

ServiceNow Calling Workflow from Flow see this link by  servicenowgyan

S erviceNow get record last updated fields - scoped application   (note I have dropped this in here today without having fully tested it yet 😛 ) scoped application version: see http://snamigos.blogspot.com/2017/11/how-to-get-changed-or-modified-fields.html where the blogger is recommending this approach: //this will give you array of changed field names var changed _fields = getChangedFieldNames(current); function getChangedFieldNames(gr) { var result = []; var elements = gr.getElements(); var size = elements.length; for ( var i = 0 ; i < size; i ++ ) { var ge = elements[i]; if (ge.changes()) { result.push(ge.getName()); } } return result; }

 Old ASYNCH business rules are being deprecated in ServiceNow - and you may see them tagged as such following upgrades See this KB https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951770 (ServiceNow )