Scan Engine definitions: User Experience
Scan Engine user experience definitions evaluate the quality of user interactions with applications. Considers the ease of use, efficiency, design, responsiveness, accessibility, and its emotional and functional impact.
Australia definitions
The following user experience definitions have been added for the Australia 2026 release:
| Number | Active | Level of Finding | Unique ServiceNow Product | Short Description | Business Impact | Steps to Resolve | Supporting Documentation |
|---|---|---|---|---|---|---|---|
| sn_SE10026 | 1 | Suggest | JavaScript popups (alert, confirm, prompt) should be limited in use | Users may become frustrated with the tool with all the popups. | Use OOB methods such as g_form.addInfoMessage() and g_form.showFieldMsg() to display information to the user without popups. GlideDialogWindow is another method that can be utilized if we need to gather data from the user which doesn't reside on the form. | Documentation | |
| sn_SE10029 | 1 | Act | Modules should not be linked to nonexistent tables | Users may become frustrated with ServiceNow. | Deactivate the module. | Documentation | |
| sn_SE10056 | 1 | Suggest | Email Sending enabled on non-production system | User could become frustrated with the platform as well as time could be spent on a fictitious task. | Either disable email sending or provide a test user that will receive all emails. | Documentation | |
| sn_SE10058 | 1 | Act | g_form.setVisible should be replaced with g_form.setDisplay | User may see blank areas on the form. | Use either a UI Policy or g_form.setDisplay function in place of g_form.setVisible function. | Documentation | |
| sn_SE10140 | 1 | Suggest | First element on a global list shouldn't be a reference field | Users may experience frustration. | Update the list view to show something other than a reference field as its first element. | Documentation | |
| sn_SE10249 | 1 | Recommend | Optional: Hints should be included for all fields | End users may become frustrated with the lack of how to use the system. | Add a hint describing any pertinent information about the field to help the end user better understand the field's purpose. | Documentation | |
| sn_SE10264 | 1 | Suggest | The meta field should not be empty on catalog items | User experience should improve. | Review the catalog item to determine the appropriate keywords for the catalog item and add those to the Meta field. | Documentation | |
| sn_SE10267 | 1 | Recommend | Dirty form support should not be disabled | End users may become frustrated with the platform as a result of their modifications not being saved. | Enable dirty form support by setting the property glide.ui.dirty_form_support to true. | Documentation | |
| sn_SE10269 | 1 | Suggest | System property glide.ui.max_ref_dropdown should not be greater than 100 | Too many choices on a screen resulting a poor user experience. | Update the value on the glide.ui.max_ref_dropdown system property to be less than 100 (preferably a value of 25). | Documentation | |
| sn_SE10270 | 1 | Act | HTML Field Editor should be set to "tinymce" | Unexpected functionality may result in a poor user experience. | The value of "glide.ui.html.editor" should be set to "tinymce". | Documentation | |
| sn_SE10271 | 1 | Suggest | Maximum attachment size is greater than 5GB | Users may experience issues on the platform after loading a large attachment. | Review the attachment size and determine if allowing more than a 5GB attachment is necessary. | Documentation | |
| sn_SE10296 | 1 | Suggest | Notifications should not have inactive recipients | Potential process delays due to notifications that are never received. | Replace inactive recipients or set notifications to be sent to groups that are maintained with only active users. | Documentation | |
| sn_SE10297 | 1 | Act | Child group does not contain all parent roles | Process delays due to insufficient access. | Review this group to understand why the roles have not been inherited from the parent group. Potential causes to this issue include business rules that did not execute, a clone that excludes the Group Role [sys_group_has_role] table, or if roles have been deleted directly from the Group Role [sys_group_has_role] table. Removing the parent from this group, saving, and then adding the parent back should resolve this issue. | Documentation | |
| sn_SE10308 | 1 | Suggest | Change Request conflict detection: blackout window | Change Requests will be unable to check against blackout windows which could jeopardize the success of the change. | The following Conflict Detection property should be set to true: change.conflict.blackout. | Documentation | |
| sn_SE10309 | 1 | Suggest | Change Request conflict detection: current CI | Change Requests will be unable to check against CI conflicts which could jeopardize the success of the change. | The following Conflict Detection property should be set to true: change.conflict.currentci. | Documentation | |
| sn_SE10310 | 1 | Suggest | Change Request conflict detection should be enabled for maintenance windows | Change Requests will be unable to check against the CI's maintenance window which could jeopardize the success of the change. | The following Conflict Detection system property should be set to true: change.conflict.currentwindow. | Documentation | |
| sn_SE10311 | 1 | Suggest | Change Request conflict detection: refresh conflicts | Change Requests that do not automatically run conflict detection when significant fields are updated risk missing a conflict which could jeopardize the success of the change. | The following Conflict Detection property should be set to true: change.conflict.refresh.conflicts. | Documentation | |
| sn_SE10317 | 1 | Suggest | Groups should have a manager | Groups with no manager's assigned can lead to difficulty with escalations, failure to meet SLAs, and poor data management. | Assign a manager to the group. | Documentation | |
| sn_SE10422 | 1 | Act | Multiple UI Policies with the same order for a particular field/variable | User could become frustrated with the platform and consider the inconsistent behavior a bug. | Differentiate the order on the UI Policies to ensure UI Policies are always fired in the same sequence which will keep the user experience consistent. | Documentation | |
| sn_SE10495 | 1 | Recommend | Query Business Rules filtering out records without your knowledge | Records you need access to could be filtered out unknowingly. |
|
Documentation | |
| sn_SE10510 | 1 | Recommend | Duplicate task numbers | Duplicate task numbers may confuse users and create unnecessary effort. | Although duplicate numbers are rare, numbering does not enforce uniqueness, by default. Fix the number maintenance and re-number those who are duplicates. Enable unique number indexing on the table to ensure duplicate numbers are not created. | Documentation | |
| sn_SE10514 | 1 | Suggest | Avoid creating long module titles | Long module titles affect readability on the navigator. | Reduce the length of module titles. | Documentation | |
| sn_SE10515 | 1 | Recommend | Catalog Items should have a Name and Short description | Catalog Items may be difficult to identify without a Name or Short Description. | Add a Name and Short Description when configuring Catalog Items. | Documentation | |
| sn_SE10516 | 1 | Suggest | Group exists with no users | Any objects referencing an empty group, such as reports, will not reach it's intended audience. | Add users to the group or set the group to inactive. | Documentation | |
| sn_SE10518 | 1 | Review | Excessive use of fields on a form | User could become frustrated with the platform and consider the inconsistent behavior a bug. | Review the purpose of each field configured on a form and decide whether or not it is truly needed. | Documentation | |
| sn_SE10519 | 1 | Suggest | HR Service should have a Fulfillment Instruction | Without fulfillment instructions, HR agents may have difficulty completing cases. | Use the condition builder to dynamically change what fulfillment instructions appear for an HR case when it is transferred from one HR service to another. | Documentation | |
| sn_SE10520 | 1 | Review | Number of Related Lists on Project Form | User could become frustrated with the platform and consider the inconsistent behavior a bug. | Review number of related lists and determine which lists are required. | Documentation | |
| sn_SE10521 | 1 | Suggest | Knowledge articles older than 12 months may be outdated | Information within the knowledge articles may be outdated and may not contain accurate and up-to-date information | Review the content contained within knowledge articles older than 12 months and determine if it should be edited, retired, or preserved. | Documentation | |
| sn_SE10524 | 1 | Suggest | Excessive Client Scripts | Users may experience reduced performance while loading or updating records. | Reduce and optimize the number of client scripts per table. Deactivate any unnecessary client scripts. | Documentation | |
| sn_SE10525 | 1 | Recommend | List Report without any columns selected | Reports could be unreadable and confusing without defined columns. | In the Columns window that opens after you select Choose columns, select fields in the Available list that you want to appear in your report and move them to the Selected list. | Documentation | |
| sn_SE10527 | 1 | Suggest | Populate Knowledge Base articles fully | Users may have difficulty finding relevant knowledge articles. | Update the KB article to populate relevant fields (Short Description, Category, KB Article Body, Valid To and Author). | Documentation | |
| sn_SE10533 | 1 | Recommend | Inactive breakdown source associated with active indicators or collection jobs | The breakdown defined in the indicator or collection job may return incomplete or no data. | Set the breakdown source to active so the breakdown it is defined in can properly capture the elements needed for the collection job. | Documentation | |
| sn_SE10535 | 1 | Suggest | Human Resource Catalog Client scripts should have 'All' as UI type | The HR application experience between desktop and mobile may differ for users if catalog client scripts are not defined for both. | Set the UI type field to "All". | Documentation | |
| sn_SE10537 | 1 | Suggest | Instance URL should not be hard-coded | Objects referring to the hard-coded URL will not be dynamic and will only be useful for the hard-coded instance. | Use the method gs.getProperty(instance_name); to dynamically retrieve the instance name, or gs.getProperty(glide.servlet.uri); to get the full URL. | Documentation | |
| sn_SE10545 | 1 | Suggest | Active session time should be greater than the inactive session time for Integrations | Inefficient session management creates a poor user experience and poor performance with integrations | Adjust the "glide.integrations.active.session.life_span" property to have a greater value than the "glide.integration.session_timeout" property. | Documentation | |
| sn_SE10551 | 1 | Suggest | Widgets not used in any dashboards | Without widgets, dashboards will appear empty and not convey important data. | Use the Widget Picker to add widgets to your dashboard. | Documentation | |
| sn_SE10575 | 1 | Review | Change the favicon to a more representive picture of your company | The favicon is a visible representation of our IT department's attention to detail and commitment to providing a modern, user-friendly experience. An outdated favicon can lead to a perception that our IT services are outdated, slow to adapt, or unresponsive to user needs. | First, upload an image by navigating to System UI > Images > New. Once uploaded, navigate to System Properties > System > then in the Icon image displayed in the bookmarks and browser address bar, enter the file name of your uploaded image.The feature is controlled by a system property glide.product.icon, it should exist with a value set by admin. | Documentation |