ServiceNow Studio supported file types using code search

Reference the file types that ServiceNow Studio supports when using code search to locate scripts and metadata across an instance.

Code search in ServiceNow Studio uses the default code search group. The following table lists the file types supported by the default ServiceNow Studio code search.

Tip:

To expand the list of supported file types, an administrator can create a new code search group that includes additional file types. For more information, see Expand code search tables.

Note:

File types must extend the sys_metadata table to be searchable in code search. Other file types, such as scheduled items (sys_trigger records), are not searchable in ServiceNow Studio.

Table 1. Supported file types for code search

File type	Code search table name	Description
Access control	sys_security_acl	Determines whether access is granted for a specified operation to a specific entity, such as: Type of entity being secured Operation being secured Unique identifier describing the object
Business rules	sys_script	Customize system behavior. Business Rules run when a database action occurs (query, insert, update, or delete). The script can run: before or after the database action is performed (runs as part of the database operation). asynchronously (at some point after the database operation). on display (when displaying the data in a form).
Client scripts	sys_script_client	Change the appearance of forms and display fields based on entered values or other custom display options. onLoad: The client script runs when the form or page loads. onChange: The client script runs when a specific field changes and also when the form or page loads. onSubmit: The client script runs when the form is submitted. Client scripts can also be called by other scripts or modules, including UI policies.
Email templates	sysevent_email_template	Create reusable content for the subject line and message body of email notifications.
Inbound email actions	sysevent_in_email_action	Script how the system responds to inbound emails.
Map pages	cmn_map_page	Display ServiceNow data graphically on a Google map page based on location data that you provide.
Map transforms	sys_transform_map	Import data by defining mapping relationships between tables. Transform maps: Define mapping relationships between tables. Can use business rules, other scripts, or other options to import data.
Notifications	sysevent_email_action	Determine how an application communicates with users and alerts them about important application-related events.
Processors	sys_processor	Provide customizable URL endpoints that execute server-side JavaScript code and produce output such as TEXT or JSON.
Relationships	sys_relationship	Extend tables, reference records in another table, create many-to-many relationships, and join tables in a database view.
Scheduled script executions	sysauto_script	Define automated, server-side script logic that executes at a specific time or on a recurring basis. Scheduled script executions are also referred to as scheduled jobs.
Script actions	sysevent_script_action	Contain scripts that run when an event occurs, for example: Approval is canceled Change is approved Problem is assigned
Script includes	sys_script_include	Contain reusable functions or classes that run only when called by other scripts, often business rules. Any server script that is complicated or reusable should be a Script Include, especially complicated business rules.
Schedule items	sys_trigger	Contain the back-end data for the System scheduler, where scheduled jobs are created, queued up, and executed. Schedule items can execute scheduled jobs, business rules, inactivity monitors, service level agreement (SLA) calculations, metric events, upgrades, and more. Access schedule item records to troubleshoot scheduling.
Defining UI actions	sys_ui_action	Include the buttons, links, and context menu items on forms and lists. Configure UI actions to make the UI more interactive, customized, and specific to user activities.
UI macros	sys_ui_macro	Contain discrete scripted components that administrators can add to the user interface. UI macros are typically controls that provide inputs or information not provided by existing field types. By default, the system provides UI macros for a variety of user interface elements.
UI pages	sys_ui_page	Create and display forms, dialogs, lists, and other UI components.
Using UI policies	sys_ui_policy	Define the behavior and visibility of fields on a form. Fields can be one of the following: Mandatory Visible Read only The following apply to usage: UI policies are always attached to one table. UI policies often have a condition that must be true for them to run.
UI scripts	sys_ui_script	Store client scripts for reuse. Run only when called from other scripts.
UI style	sys_ui_style	Declare individual CSS styles for a field in a list or form.
Widgets	sp_widget	Describe objects that contain content and can be added to or embedded in portal pages. Use the base system widgets provided with the Service Portal, clone and modify widgets, or develop custom widgets to fit your own needs.