ServiceNow

This is a quick and dirty way to pass data from a UI action to a Business rule. Use at your own risk!

There are several ways to filter a List collector dynamically. This is the simplest one I found so far. It will work in both the Service portal and the default interface. It will only require a one-line onChange client script for it to work on the default interface. Let’s see it with one simple example.

If you try to populate a GlideList field using a script, you can end up with different values in your table, depending on the way you do it. GlideList fields such as the Watch list and Work notes list can store 2 types of values: Usually, you will want to save references(sys_ids) for users in

Why don’t we use Field styles for X?Unluckily, this is probably the most inconsistent piece of functionality in the Servicenow platform.

ServiceNow provides a good documentation page about User Notification Preferences. Have you ever wondered where these settings are stored in the backend? Let’s have a look at the main tables and fields where ServiceNow stores this data. Notification Preferences Notification Preferences Popup Backend Table / Field Allow Notifications User -> Notification [sys_user.notification] Notification Channel Notification