The most exciting change in the latest Tokyo version is the adjustment of the JavaScript engine from ECMAScript5 to ECMAScript 2021 (ES12) JavaScript.<\/strong> Until now, ECMAScript 2021 (ES12) could be used in scoped applications and scripts, while the new standard enables the following features on the platform:<\/p>\n\n\n\n The second new feature in the Tokyo version is supporting the migration of IP addresses, which are stored as strings, to the new <\/strong>IP Address (Validated IPV4, IPV6)<\/strong> type<\/strong>. The new IP type will store valid IPv4 and IPv6 addresses.<\/p>\n\n\n\n The data is formatted according to the dictionary attribute ip_data_control and can be set to one of the four values:<\/p>\n\n\n\n Another new feature is a fallback language, which will help in situations where the UI is not translated into the language needed by the user<\/strong>. You need the administrator role to set the language. There is no need to add custom translations in user interface strings. Users will get the most suitable translations and if any of the translations is unavailable, then the instance session will use English.<\/p>\n\n\n\n Admins can set fallback languages on the Languages (sys_language<\/em>) table, but English cannot be chosen there as it is the default language. If fallback language is not preferred, it is possible to set glide_i18n.language_fallback_enabled<\/em> as false and then the language is always set to English.<\/p>\n\n\n\n The new Tokyo release also gives the possibility to<\/strong> configure system rules to prevent sys log tampering<\/strong>. From the current version, all manipulation over sys logs tables will be visible. To start the protection, you need to activate com.glide.protected_tables<\/em> plugin. For now, protection rules are available for the following tables and their children: syslog, syslog_transaction, sys_outbound_http_log, sysevent, sys_audit, sys_push_notification, protected_table_configuration<\/em>.<\/p>\n\n\n\n After plugin activation, any attempt of deleting or changing logs from those tables will be visible as log records on protected_table_log table. It is possible to choose if we want to block modifications and log attempts, not block modifications but still log the attempts, or block modifications without logged attempts.<\/p>\n\n\n\n Since the Tokyo release, it is possible to safely delete or update records<\/strong>. We need a scheduled job to delete records. After creation, but before execution of the job, you can preview all affected records. Even after the job has ended, we can still use rollback and restore deleted records.<\/p>\n\n\n\n Deleting a bigger number of records is also possible thanks to the table cleaner. Table cleaner is a type of scheduled job that helps remove all old records and maintain a number of records<\/strong> in the table.<\/strong> It runs once per hour and deletes all old, expired, and unneeded records. Table cleaner cannot be used for tables that are configured to use table extension or rotation. Table cleaner deletes records by 20 minutes session, the number of deleted records can be different if queries are slow.<\/p>\n\n\n\n Bulk updates without scripting are also possible. To perform it, we need to create an updated job. To prevent the table from being locked during the job execution we should add some conditions to limit updated records. Also, here it is possible to check records before updating and restore them by rollback if needed. The rollback can be performed by the Admin.<\/p>\n\n\n\n In the Tokyo release, we also get ScopedCacheManager API for faster access to data stored in memory<\/strong>. To retrieve, set or flush cache the com.glide.scopedcache<\/em> plugin need to be activated by the Admin user. To be able to use it, one or more cache or cache pairs need to be chosen. For now, we can use table pair cache, table row pair cache, table column pair cache, or table column and row pair cache.<\/p>\n\n\n\n ScopedCacheManager API gives us a few advantages, like the possibility to use cache data outside the transaction cycle and caching output of valuable operations for quick use in the future.\u00a0 We can also cache strings to have access to it or applications that can be flushed depending on changes in the underlying tables.<\/p>\n\n\n\n The Tokyo release also made changes in core platform ServiceNow, the first of which is the system localization<\/strong>. Localization helps accommodate users from around the world on the same instance. Information like time, date or currencies can be specified and based on a location. ServiceNow supports many languages but it is also possible to provide your own translations, especially for custom-made modifications or applications.<\/p>\n\n\n\n Since the Tokyo version, we can use a side bar in Conversational Interfaces<\/strong>. With the sidebar workspace, agents can open real-time discussions on interaction or task table-based records. For now, it is possible to create one discussion per record.<\/p>\n\n\n\n Sidebar can be used in:<\/p>\n\n\n\n I hope that the numerous changes and improvements introduced on the ServiceNow platform in the Tokyo version will affect the ease and efficiency of using the tool in everyday work. I encourage you to try them.<\/p>\n\n\n\n ***<\/p>\n\n\n\n If you are interested in ServiceNow, we recommend our expert’s article:<\/p>\n\n\n\n\n
![\"Adjustment](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2023\/02\/1-3.png\")
<\/a>New IP address type<\/strong><\/h2>\n\n\n\n
\n
<\/a>System localization fallback language<\/strong><\/h2>\n\n\n\n
<\/a>Sys log tampering prevention<\/strong><\/h2>\n\n\n\n
<\/a><\/a>Safe records deleting and updating<\/strong><\/h2>\n\n\n\n
<\/a>New scoped cache API<\/strong><\/h2>\n\n\n\n
<\/a><\/a>Support for system localization<\/strong><\/h2>\n\n\n\n
<\/a>Sidebar<\/h2>\n\n\n\n
\n
<\/a>Summary<\/strong><\/h2>\n\n\n\n
Sources<\/strong><\/h2>\n\n\n\n
\n