---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# ServiceNow Studio supported file types using code search

# ServiceNow Studio supported file types using code search {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

ServiceNow Studio supports the following file types when using code search.
When using code search in ServiceNow Studio, the application uses the default code search group. The following table outlines the file types that are supported when using the default ServiceNow Studio code search.  
Tip:  
If your company wants to expand the list of supported file types used in code search, an administrator can create a new code search group that includes additional file types. For more information about expanding code search, see [Expand code search tables](https://developer.servicenow.com/connect.do#!/share/contents/3024956_expand_code_search_tables?v=1&t=PRODUCT_DETAILS). {#sn-studio-file-types__table_lcj_1bh_qcc__entry__3}

| File type | Code search table name | Description |
|-|-|-|
| [Access control](https://www.servicenow.com/docs/access?context=sc-access-control&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) | 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 {#sn-studio-file-types__ul_qhg_mtr_sq} |
| [Business rules](https://www.servicenow.com/docs/access?context=c_BusinessRules&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_script | Customize system behavior. * [Business Rules](https://www.servicenow.com/docs/access?context=c_BusinessRules&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) 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). {#sn-studio-file-types__ul_wwy_y5r_sq} {#sn-studio-file-types__ul_lvx_x5r_sq} |
| [Client scripts](https://www.servicenow.com/docs/access?context=client-scripts&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_script_client | Used for changing the appearance of forms, displaying different fields based on values that are entered or other custom display options. * onLoad means that the Client Script runs when the form or page is loaded * onChange means that the Client Script runs when something specific gets changed AND also when the form or page loads * onSubmit means that the Client Script runs when the form is submitted {#sn-studio-file-types__ul_qv4_mvr_sq} Client Scripts can also be called by other scripts or modules, including UI policies. |
| [Email templates](https://www.servicenow.com/docs/access?context=c_EmailTemplates&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sysevent_email_template | Enable administrators to create reusable content for the subject line and message body of email notifications. |
| [Inbound email actions](https://www.servicenow.com/docs/access?context=actions-inbound-email&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sysevent_in_email_action | Script how the system responds to inbound emails. |
| [Map pages](https://www.servicenow.com/docs/access?context=c_MapPages&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) | cmn_map_page | Display ServiceNow data graphically on a Google map page based on location data that you provide. |
| [Map transforms](https://www.servicenow.com/docs/access?context=c_CreatingNewTransformMaps&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) | sys_transform_map | Used for importing data. Transform maps: * Define mapping relationships between tables. * Can use business rules, other scripts, or other options to import data. {#sn-studio-file-types__ul_i4r_xkb_1dc} |
| [Notifications](https://www.servicenow.com/docs/access?context=t_CreateANotification&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sysevent_email_action | Determine how an application communicates with users and alerts them about important application-related events. |
| [Processors](https://www.servicenow.com/docs/access?context=c_Processors&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_processor | Provide customizable URL endpoints that can execute arbitrary server-side JavaScript code and produce output such as TEXT or JSON. |
| [Relationships](https://www.servicenow.com/docs/access?context=table-relationships&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sys_relationship | Used to extend tables, reference records in another table, create many-to-many relationships, and join tables in a database view. |
| [Scheduled script executions](https://www.servicenow.com/docs/access?context=c_ScheduledJobs&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | 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](https://www.servicenow.com/docs/access?context=r_ScriptActions&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US) | sysevent_script_action | Contain scripts that run when an event occurs, for example: * Approval is canceled * Change is approved * Problem is assigned {#sn-studio-file-types__ul_dp1_zvr_sq} |
| [Script includes](https://www.servicenow.com/docs/access?context=c_ScriptIncludes&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_script_include | Contain scripts that can be functions or classes. These scripts 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](https://www.servicenow.com/docs/access?context=t_ViewAScheduleItem&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sys_trigger | Contain the back-end data for the [System scheduler](https://www.servicenow.com/docs/access?context=c_SystemScheduler&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US), 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. You can access schedule item records to troubleshoot scheduling. |
| [Defining UI actions](https://www.servicenow.com/docs/access?context=c_UIActions&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | 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](https://www.servicenow.com/docs/access?context=c_UIMacros&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | 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 that is not provided by existing field types. By default, the system provides UI macros for a variety of user interface elements. |
| [UI pages](https://www.servicenow.com/docs/access?context=r_UIPages&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_ui_page | Used to create and display forms, dialogs, lists, and other UI components. |
| [Using UI policies](https://www.servicenow.com/docs/access?context=t_CreateAUIPolicy&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sys_ui_policy | Define the behavior and visibility of fields on a form. Fields can be one of the following: * Mandatory * Visible * Read only {#sn-studio-file-types__ul_lh4_h1s_sq} 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. {#sn-studio-file-types__ul_xzb_k1s_sq} |
| [UI scripts](https://www.servicenow.com/docs/access?context=c_UIScripts&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | sys_ui_script | Contains client scripts stored for reuse. Only used when called from other scripts. |
| [UI style](https://www.servicenow.com/docs/access?context=t_DefineFieldStyles&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) | sys_ui_style | Enables you to declare individual CSS styles for a field in a list or form. |
| [Widgets](https://www.servicenow.com/docs/access?context=c_NestedWidgets&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) | sp_widget | Describe objects that contain content and can be added to or embedded in portal pages. You can use the base system widgets provided with the Service Portal, clone and modify widgets, or develop custom widgets to fit your own needs. |
[Table 1. Supported file types for code search]

{#sn-studio-file-types__table_lcj_1bh_qcc}