Skip to content
Release: Australia · Updated: 2026-07-09 · Official documentation · View source

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:

NumberActiveLevel of FindingUnique ServiceNow ProductShort DescriptionBusiness ImpactSteps to ResolveSupporting Documentation
sn\_SE100261Suggest JavaScript popups \(alert, confirm, prompt\) should be limited in useUsers 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\_SE100291Act Modules should not be linked to nonexistent tablesUsers may become frustrated with ServiceNow.Deactivate the module.Documentation
sn\_SE100561Suggest Email Sending enabled on non-production systemUser 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\_SE100581Act g\_form.setVisible should be replaced with g\_form.setDisplayUser 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\_SE101401Suggest First element on a global list shouldn't be a reference fieldUsers may experience frustration.Update the list view to show something other than a reference field as its first element.Documentation
sn\_SE102491Recommend Optional: Hints should be included for all fieldsEnd 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\_SE102641Suggest The meta field should not be empty on catalog itemsUser 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\_SE102671Recommend Dirty form support should not be disabledEnd 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\_SE102691Suggest System property glide.ui.max\_ref\_dropdown should not be greater than 100Too 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\_SE102701Act 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\_SE102711Suggest Maximum attachment size is greater than 5GBUsers 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\_SE102961Suggest Notifications should not have inactive recipientsPotential 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\_SE102971Act Child group does not contain all parent rolesProcess 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\_SE103081Suggest Change Request conflict detection: blackout windowChange 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\_SE103091Suggest Change Request conflict detection: current CIChange 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\_SE103101Suggest Change Request conflict detection should be enabled for maintenance windowsChange 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\_SE103111Suggest Change Request conflict detection: refresh conflictsChange 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\_SE103171Suggest Groups should have a managerGroups 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\_SE104221Act Multiple UI Policies with the same order for a particular field/variableUser 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\_SE104951Recommend Query Business Rules filtering out records without your knowledgeRecords you need access to could be filtered out unknowingly.- Redirect employees to the Portal, you will not need to create query business rule because there is a filter already in place. - If there is a need restrict query on the tables, try using fixed query on filters instead. - If the above two are not an option then ensure the following are considered when creating Query Business Rule. - Index the most common field in the filter. - Avoid negative operator like != or NOT IN.Documentation
sn\_SE105101Recommend Duplicate task numbersDuplicate 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\_SE105141Suggest Avoid creating long module titlesLong module titles affect readability on the navigator.Reduce the length of module titles.Documentation
sn\_SE105151Recommend Catalog Items should have a Name and Short descriptionCatalog Items may be difficult to identify without a Name or Short Description.Add a Name and Short Description when configuring Catalog Items.Documentation
sn\_SE105161Suggest Group exists with no usersAny 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\_SE105181Review Excessive use of fields on a formUser 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\_SE105191Suggest HR Service should have a Fulfillment InstructionWithout 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\_SE105201Review Number of Related Lists on Project FormUser 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\_SE105211Suggest Knowledge articles older than 12 months may be outdatedInformation within the knowledge articles may be outdated and may not contain accurate and up-to-date informationReview the content contained within knowledge articles older than 12 months and determine if it should be edited, retired, or preserved.Documentation
sn\_SE105241Suggest Excessive Client ScriptsUsers 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\_SE105251Recommend List Report without any columns selectedReports 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\_SE105271Suggest Populate Knowledge Base articles fullyUsers 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\_SE105331Recommend Inactive breakdown source associated with active indicators or collection jobsThe 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\_SE105351Suggest Human Resource Catalog Client scripts should have 'All' as UI typeThe 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\_SE105371Suggest Instance URL should not be hard-codedObjects 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\_SE105451Suggest Active session time should be greater than the inactive session time for IntegrationsInefficient session management creates a poor user experience and poor performance with integrationsAdjust the "glide.integrations.active.session.life_span" property to have a greater value than the "glide.integration.session_timeout" property.Documentation
sn\_SE105511Suggest Widgets not used in any dashboardsWithout widgets, dashboards will appear empty and not convey important data.Use the Widget Picker to add widgets to your dashboard.Documentation
sn\_SE105751Review Change the favicon to a more representive picture of your companyThe 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