---
sourceDocument: Zurich Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Navigator panel taxonomy

# ServiceNow Studio Navigator panel taxonomy {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 31 minutes to read

Learn more about each metadata file type and its corresponding primary table in the File categories tab of the ServiceNow Studio Navigator panel.
Note:  
Any additional extensions of the sys_metadata table are automatically included in the Navigator panel in the appropriate section.

For each file category, see the file types that you can create and their corresponding primary table. For more information about navigating to a file's primary table, see [Navigate directly to a table in ServiceNow Studio](https://www.servicenow.com/docs/3AZn6tSyjFqMs74Hj34YBQ "Navigate directly to the list view of a table in ServiceNow Studio by using the Open list feature in the Navigator panel or search shortcuts in the main search.").

Metadata-specific admin roles are existing roles on the ServiceNow AI Platform that provide developers with admin access to a specific metadata type. For example, a script include admin allows a developer to create, read, update, or delete any script include on the ServiceNow AI Platform and perform development on script includes in ServiceNow Studio. For more information, see [ServiceNow Studio personas and roles](https://www.servicenow.com/docs/7j4~8_70Z7uu_drHQVSneQ "Admins, delegated developers, and users with Guided Application Creator roles have access to work in ServiceNow Studio.").

## AI files {#servicenow-studio-file-navigator-taxonomy__section_nkn_lxn_gfc}

AI files provide ways to use generative AI to enhance user productivity and efficiency through conversation and proactive experiences.  
Important:  
AI options in the ServiceNow Studio file taxonomy are only available if the AI components have been installed and configured.
{#servicenow-studio-file-navigator-taxonomy__table_jsx_hzn_gfc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Agentic Workflow | An agentic workflow is a business problem that you want to solve. In AI Agent Studio, you must define an agentic workflow and connect it with an AI agent to get a resolution plan. For more information, see [Create an agentic workflow](https://www.servicenow.com/docs/access?context=configure-use-case-ai-agents&version=zurich&pubname=zurich-intelligent-experiences&ft:locale=en-US). | sn_aia_usecase | AI Agent Studio |
| AI Agent | AI Agents are entities that mimic human-like intelligence by using large language models (LLMs). AI agents can perform tasks that range from simple automated responses to complex problem solving. By using AI agents, you can reduce the workloads of your live agents and help increase their productivity. For more information, see [Create an AI agent](https://www.servicenow.com/docs/access?context=configure-next-best-action-agent&version=zurich&pubname=zurich-intelligent-experiences&ft:locale=en-US). | sn_aia_agent | AI Agent Studio |
| Skill | Skills are user-defined AI capabilities tailored to meet specific business needs. Custom skills are created using Now Assist Skill Kit, which allows for a user to define input data, prompts, LLM providers and deployment areas for custom skills. For more information, see [Create a skill](https://www.servicenow.com/docs/access?context=create-new-skill&version=zurich&pubname=zurich-intelligent-experiences&ft:locale=en-US). | sn_nowassist_skill_config | UI16 |
[Table 1. AI file types]

{#servicenow-studio-file-navigator-taxonomy__table_jsx_hzn_gfc}

## Automation files {#servicenow-studio-file-navigator-taxonomy__section_pcg_352_ddc}

Automations provide ways to manage recurring tasks efficiently, with fewer steps, reducing human input and effort. For example, you can configure an email notification to be sent automatically when a record is approved. Create
automations to streamline and simplify how you work by adding automations to an app, such as actions, flows, and other automatic tasks.
{#servicenow-studio-file-navigator-taxonomy__table_zws_dv2_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Action | Actions automate a repeatable task or operation within a flow as a sequence of related steps. Actions run a sequence of steps to complete the task, and pass data to the flow as outputs. For more information, see [Exploring actions](https://www.servicenow.com/docs/access?context=exploring-actions&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_hub_action_type_definition | Workflow Studio |
| Activity definition | Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs. Each activity definition contains some basic configuration details, as well as an automation plan and activity experience. For more information, see [Activity definitions](https://www.servicenow.com/docs/access?context=activity-definitions&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_pd_activity_definition | UI16 |
| Connection \& Credential Aliases | A Connection and Credential alias defines an alias that labels a credential or connection record, enabling an app to connect to another system or component. For more information, see [Connections and Credentials](https://www.servicenow.com/docs/access?context=r-credentials&version=zurich&pubname=zurich-platform-security&ft:locale=en-US). | sys_alias | UI16 |
| Datastream | A datastream is a reusable action that processes a stream of response data within a flow. For example, you can create a data stream action to import a large quantity of employee data from a third-party HR site. For more information, see [Data Stream actions and pagination](https://www.servicenow.com/docs/access?context=data-stream-actions&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_hub_action_type_definition | Workflow Studio |
| Decision table | Decision tables decouple decision logic from your code by creating and maintaining decision rules. Decision tables provide a single point where you can create, view, and modify decisions. For more information, see [Exploring Decision Tables](https://www.servicenow.com/docs/access?context=decision-designer-overview&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_decision | Workflow Studio |
| Email Template | Email templates enable administrators to create reusable content for the subject line and message body of email notifications. Admins can add rich text and other items, such as images, to email templates. For more information, see [Email templates](https://www.servicenow.com/docs/access?context=c_EmailTemplates&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sysevent_email_template | UI16 |
| Flow | Flows are automated processes that consist of a trigger and a sequence of reusable actions and flow logic. The trigger specifies when to run the flow. The actions perform a sequence of operations on your data. For example, the Visual Task Boards (VTB) Sample Flow creates and assigns a VTB card whenever a priority 1 incident is created. For more information, see [Exploring flows](https://www.servicenow.com/docs/access?context=exploring-flows&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_hub_flow | Workflow Studio |
| Notification | Notifications alert users when a record changes. For example, you could get a push notification when a request is rejected. For more information, see [System notifications](https://www.servicenow.com/docs/access?context=system-notifications-landing&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sysevent_email_action | UI16 |
| Playbook | Playbooks are sets of automated activities that occur based on a trigger. For example, you can create a playbook for your app to send an email when a request is approved. For more information, see [Getting started with Playbooks](https://www.servicenow.com/docs/access?context=getting-started-processes&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_pd_process_definition | Workflow Studio |
| Subflow | Subflows are processes that consist of a sequence of reusable actions and flow logic, data inputs, and outputs. In contrast to flows, subflows don't have a trigger but instead run when called from a playbook, flow, another subflow, or a script. For more information, see [Exploring subflows](https://www.servicenow.com/docs/access?context=exploring-subflows&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sys_hub_flow | Workflow Studio |
[Table 2. Automation file types]

{#servicenow-studio-file-navigator-taxonomy__table_zws_dv2_ddc}

## Client development files {#servicenow-studio-file-navigator-taxonomy__section_nk1_gw2_ddc}

Client development files define operations that occur based on actions you can take when working with an app built in ServiceNow Studio.
{#servicenow-studio-file-navigator-taxonomy__table_it4_jw2_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Assignment Data Lookup | Use assignment data lookups to assign a record automatically using Data Lookup and Record Matching. For example, you can automatically set a value in the assigned_to and assignment_group fields for a record when a set of conditions occurs, such as assigning approvals to a group of managers for users below a certain level. For more information, see [Defining assignment rules](https://www.servicenow.com/docs/access?context=c_DefineAssignmentRules&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | dl_u_assignment | UI16 |
| Client Extension Instance | Use a client extension integration to a registered instance of a client extension point that links a UI script with a client extension point. The UI script is included on pages that invoke the client extension point. For more information, see [Using extension points to extend application functionality](https://www.servicenow.com/docs/access?context=extension-points&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_client_extension_instance | UI16 |
| Client Extension Point | Client extension points extend the functionality of an application without altering the original application code. Extension points can help prevent your custom code interactions from breaking, which often occurs after an upgrade if you directly embed the custom code into the application code. For more information, see [Using extension points to extend application functionality](https://www.servicenow.com/docs/access?context=extension-points&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_client_extension_point | UI16 |
| Client Script | Client scripts enable apps on the ServiceNow AI Platform to run JavaScript on the client (web browser) when client-based events occur. For example, it could run when a form loads, after form submission, or when a field changes value. For more information, see [Client scripts](https://www.servicenow.com/docs/access?context=client-scripts&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_script_client | UI16 |
| Data Lookup Definitions | Data lookup definitions are no-code solutions that enable you get attributes from a record on the same table. For example, you can create a data lookup definition to populate an email field automatically when you enter your name. For more information, see [Create a catalog lookup definition](https://www.servicenow.com/docs/access?context=t_CreatACatDataLookupDefRec&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | dl_definition | UI16 |
| Priority Data Lookup | Priority data lookups enable you to define the impact and urgency of an incident to calculate how it should be prioritized. For more information, see [Define priority lookup rules](https://www.servicenow.com/docs/access?context=def-prio-lookup-rules&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). | dl_u_priority | UI16 |
| UI Extension Instance | Use a UI extension instance to create a registered instance of a UI extension point that links a UI macro with a UI extension point. The macro can be called whenever the UI extension point is invoked. For more information, see [Creating and adding a UI extension point](https://www.servicenow.com/docs/access?context=impl-ui-ext-pts-base-code&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_ui_extension_instance | UI16 |
| UI Extension Point | UI extension points enable you to add custom content to a UI page without having to modify the page directly. You must first create the UI extension points, and then add them to the UI macros in the base application code. For more information, see [Using UI extension points in server-side UI macros](https://www.servicenow.com/docs/access?context=ui-extension-points&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_ui_extension_point | UI16 |
| UI Policy | UI policies dynamically change the behavior of information on a form and control custom process flows for tasks. For example, you can use UI policies to make the number field on a form read only, make the short description field required, and hide other fields. For more information, see [Using UI policies](https://www.servicenow.com/docs/access?context=t_CreateAUIPolicy&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_ui_policy | UI16 |
| UI Script | UI scripts provide a way to package client-side JavaScript into a reusable form, similar to how script includes store server-side JavaScript. For more information, see [UI scripts](https://www.servicenow.com/docs/access?context=c_UIScripts&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_ui_script | UI16 |
[Table 3. Client development file types]

{#servicenow-studio-file-navigator-taxonomy__table_it4_jw2_ddc}

## Content files {#servicenow-studio-file-navigator-taxonomy__section_krd_lx2_ddc}

Content files define ways to provide users and systems with information by referring to knowledge articles and other forms of communication. For example, content files can reference knowledge articles, static blocks of text, or
external web-based content. Use content files to provide information to apps you're building in ServiceNow Studio.
{#servicenow-studio-file-navigator-taxonomy__table_qkg_rx2_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Audio | Use audio files to upload sounds and recordings that your app can use on the ServiceNow AI Platform. For more information, see [Manage audio files](https://www.servicenow.com/docs/access?context=t_UploadAnAudioFile&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | db_audio | UI16 |
| Detailed content | Use a detailed content block to display the content of an existing document, such as an incident, knowledge article, or service management request. For more information, see [Configure a detailed content block](https://www.servicenow.com/docs/access?context=t_DetailedContentBlock&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | content_block_detail | UI16 |
| Dynamic content | Dynamic content uses scripting or pulls information from the ServiceNow AI Platform into an app. For example, use dynamic content to create a job posting, where the postings are stored in knowledge articles and displayed in the app with a dynamic block. For more information, see [Configure dynamic blocks](https://www.servicenow.com/docs/access?context=t_CreateADynamicBlock&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | content_block_programmatic | UI16 |
| iFrames | Use iFrames to embed a URL on a page within a frame. You can embed external pages or render ServiceNow content. For more information, see [Configure iFrames](https://www.servicenow.com/docs/access?context=t_IFrame&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | content_block_iframe | UI16 |
| Images | Upload and store images on the ServiceNow AI Platform to be used in apps and forms. You can then reference images from HTML fields by appending the name of the image to the URL of the instance. For more information, see [Storing images in the database](https://www.servicenow.com/docs/access?context=c_StoringImagesInTheDatabase&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | db_image | UI16 |
| Static content | Use static blocks for text that doesn't change. For example, use a static block for a site footer with only the company or organization name. For more information, see [Configure a static HTML block](https://www.servicenow.com/docs/access?context=t_StaticHTMLBlock&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | content_block_static | UI16 |
[Table 4. Content file types]

{#servicenow-studio-file-navigator-taxonomy__table_qkg_rx2_ddc}

## Data files {#servicenow-studio-file-navigator-taxonomy__section_lsm_x1f_ddc}

Data files enable you to use information stored in or referenced by an application in apps built in ServiceNow Studio. Data is the foundation of any app. You can start with a table, or upload spreadsheets and PDFs to get data into the ServiceNow AI Platform for apps to consume.
{#servicenow-studio-file-navigator-taxonomy__table_sb3_bbf_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Form | A form is a content page that displays fields and values for a single record from a database table. For more information, see [Forms in Table Builder](https://www.servicenow.com/docs/lVi_qVVFumk2_rq7gtIa4Q "On the Forms tab in Table Builder, you can visually create, configure, and customize the different form views for your users using the form editor. The views that you define contain the elements that appear when a user opens that form or list."). | sys_ui_form | Form Builder |
| Form section | Use sections to design the layout of a form. For example, you can have one column or two. For more information, see [Customize your form layout in Table Builder](https://www.servicenow.com/docs/Q2osOW3tPTcgX7rkdVf4Gg "Visually design the look of the forms your users see by customizing form views in Table Builder."). | sys_ui_section | Form Builder |
| Many to Many Definition | Use a many to many task to define relationships between different tasks. You can implement one-to-one, one-to-many, and many-to-many relationships. For example, users and roles are a many-to-many relationship because a user can have multiple roles, and multiple users can have any given role. For more information, see [Creating many-to-many task relations](https://www.servicenow.com/docs/access?context=c_ManyToManyTaskRelations&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_m2m | UI16 |
| Relationship | Use relationships to define how tables interact with each other. You can create relationships between tables by extending tables, referencing records in another table, creating many-to-many relationships, and joining tables in a database view. For more information, see [Table relationships](https://www.servicenow.com/docs/access?context=table-relationships&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_relationship | UI16 |
| Table | Tables are the foundation of how the ServiceNow AI Platform stores data. When you view a table as a list, each row is a record, and each column is a field from the record. For example, the Incident table has a record for every customer interaction, or incident. For more information, see [ServiceNow AI Platform tables and data](https://www.servicenow.com/docs/access?context=tables-fields-and-forms&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Table Builder](https://www.servicenow.com/docs/WLrX7Vai~DvWkKGPeoye~A "Table Builder enables you to create, design, and administer tables and forms visually from a single user interface."). Preferred table admins can configure preferred tables for Table Builder. For more information, see [ServiceNow Studio personas and roles](https://www.servicenow.com/docs/7j4~8_70Z7uu_drHQVSneQ "Admins, delegated developers, and users with Guided Application Creator roles have access to work in ServiceNow Studio."). | sys_db_object | Table Builder |
| Table Column | A table column represents a field from a record. For example, a user record might have a column for first name and a separate column for family name. For more information, see [Table properties in Table Builder](https://www.servicenow.com/docs/SHeCMfe5dzhtO8NvoMSOwQ "Various table and table column properties can be modified by using Table Builder."). | sys_dictionary | UI16 |
[Table 5. Data file types]

{#servicenow-studio-file-navigator-taxonomy__table_sb3_bbf_ddc}

## Inbound integration files {#servicenow-studio-file-navigator-taxonomy__section_f5w_1cf_ddc}

Inbound integrations enable you to get information and data onto the ServiceNow AI Platform from another system or source. Inbound integrations enable seamless data flow into ServiceNow from external systems, facilitating efficient communication and integration between systems.
{#servicenow-studio-file-navigator-taxonomy__table_wfy_ycf_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Data Import | Use data imports to view the all the records that are being processed for an import job and also the import jobs that are awaiting approvals. For more information, see [Importing data using import sets](https://www.servicenow.com/docs/access?context=c_ImportDataUsingImportSets&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US) and [Integration Hub - Import](https://www.servicenow.com/docs/access?context=integrationhub-imports&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sn_ihub_integration_instance | Integration Hub |
| Data Source | A data source specifies how and where to get the data you want to import. For more information, see [Data sources](https://www.servicenow.com/docs/access?context=c_DataSources&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US) and [Configure a data source](https://www.servicenow.com/docs/access?context=configure-data-source&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_data_source | UI16 |
| Scheduled Data Import | Scheduled data imports specify to import data from data sources using import sets. Transform maps are applied to the imported data before writing the data to the target table. For more information, see [Run or schedule a data import](https://www.servicenow.com/docs/access?context=run-schedule-data-imports&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | scheduled_import_set | UI16 |
| Scheduled Data Import | Scheduled data imports specify to import data from data sources. Transform maps are applied to the imported data before writing the data to the target table. For more information, see [Run or schedule a data import](https://www.servicenow.com/docs/access?context=run-schedule-data-imports&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | scheduled_data_import | UI16 |
| Scripted REST API | Use scripted REST APIs to build custom web service APIs for your application. You can define service endpoints, query parameters, and headers for a scripted REST API, as well as scripts to manage the request and response. For more information, see [Scripted REST APIs](https://www.servicenow.com/docs/access?context=c_CustomWebServices&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_ws_definition | UI16 |
| Scripted Web Service | Scripted web services enable developers to create their own APIs on the ServiceNow AI Platform. Third-party applications use scripted web services to access records in ServiceNow tables. For more information, see [Web services](https://www.servicenow.com/docs/access?context=r_AvailableWebServices&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_web_service | UI16 |
| Table Transform Map | Transform maps contain a set of field maps that determine the relationships between fields in an import set and fields in an existing ServiceNow table, such as Incident \[incident\] or User \[sys_user\]. After creating a transform map, you can reuse it to map data from another import set to the same table. For more information, see [Transform maps](https://www.servicenow.com/docs/access?context=c_CreatingNewTransformMaps&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_transform_map | UI16 |
[Table 6. Inbound integration file types]

{#servicenow-studio-file-navigator-taxonomy__table_wfy_ycf_ddc}

## Outbound integration files {#servicenow-studio-file-navigator-taxonomy__section_xmc_55k_ddc}

Outbound integrations enable you to work with data that comes from the ServiceNow AI Platform and is sent to an external system or source.
{#servicenow-studio-file-navigator-taxonomy__table_zjf_y5k_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Export Definition | Export definitions determine the data to include in an export set. For more information, see [Create an export definition](https://www.servicenow.com/docs/access?context=t_CreateAnExportDefinition&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_export_definition | UI16 |
| Export Set | Export sets define the data to export, as well as the export target to use when exporting data. For example, you can push data from an instance to an external file. For more information, see [Create an export set](https://www.servicenow.com/docs/access?context=t_CreateAnExportSet&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_export_set | UI16 |
| Export Target | Export targets specify the target file on a MID Server to which the export set data will be written. For more information, see [Create an export target](https://www.servicenow.com/docs/access?context=t_CreateAnExportTarget&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | sys_export_target | UI16 |
| REST Message | A REST message is a record that stores details on how to interact with an external web service through REST. Use REST messages to send requests to a REST web service endpoint by creating a REST message record. For more information, see [Create a REST message](https://www.servicenow.com/docs/access?context=t_ConfiguringARESTMessage&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_rest_message | UI16 |
| Scheduled Data Export | Scheduled data exports specify a schedule when export sets will be run. A single export can be scheduled or regular intervals can be scheduled with support for including only delta records. For more information, see [Schedule an export](https://www.servicenow.com/docs/access?context=t_ScheduleAnExport&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | scheduled_data_export | UI16 |
| SOAP Message | A SOAP message is a record that stores details on how to interact with an external web service through SOAP. SOAP messages define the remote endpoint, web services description language (WSDL), and authentication settings. For more information, see [SOAP message](https://www.servicenow.com/docs/access?context=c_SOAPMessage&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_soap_message | UI16 |
[Table 7. Outbound integration file types]

{#servicenow-studio-file-navigator-taxonomy__table_zjf_y5k_ddc}

## MID Server files {#servicenow-studio-file-navigator-taxonomy__section_mid_server}

Work with management, instrumentation, and discovery (MID) Server files to facilitate communication and data movement between a single ServiceNow instance and external applications, data sources, and services.
{#servicenow-studio-file-navigator-taxonomy__table_dph_wxk_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| MID Server Application | The ServiceNow MID Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. For more information, see [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | ecc_agent_application | UI16 |
| MID Server Capability Value Test | MID Server capabilities define the specific functions of a MID Server within an IP address range. The capability value can be empty, a single value, or a \* (wildcard). You can use value tests to create capabilities that find devices using values without requiring exact string matching. For more information, see [MID Server capabilities](https://www.servicenow.com/docs/access?context=mid-server-capabilities&version=zurich&pubname=zurich-integrate-applications&ft:locale=en-US). | ecc_agent_capability_value_test | UI16 |
| MID Server IP Range | Use MID Server to specify an IP range or the specific IP address of a target. For more information, see [Configure an IP address range for the MID Server](https://www.servicenow.com/docs/access?context=t_ConfigureMIDIPRange&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | ecc_agent_ip_range | UI16 |
| MID Server Property | Use MID Server properties to define the behavior of one or more MID Servers. For more information, see [MID Server properties](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | ecc_agent_property | UI16 |
| MID Server File | Use a MID Server script file to synchronize to a connected MID Server. For more information, see [Attach a script file to a file synchronized MID Server](https://www.servicenow.com/docs/access?context=mid-server-script-attach&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | ecc_agent_script_file | UI16 |
| MID Server Script Include | Use MID Server script includes to make REST calls to cloud providers. For more information, see [CAPI classes in MID Server script includes](https://www.servicenow.com/docs/access?context=mid-server-script-includes&version=zurich&pubname=zurich-it-operations-management&ft:locale=en-US). | ecc_agent_script_include | UI16 |
[Table 8. MID Server file types]

{#servicenow-studio-file-navigator-taxonomy__table_dph_wxk_ddc}

## Mobile App Builder files {#servicenow-studio-file-navigator-taxonomy__section_chp_dcl_ddc}

Mobile App Builder is a configuration tool to build and manage screens and records that make up workflows within ServiceNow mobile apps. The organizational layout and navigation options in the Mobile App Builder facilitate a faster and more intuitive creation of ServiceNow mobile applications.
{#servicenow-studio-file-navigator-taxonomy__table_lly_xcl_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Analytics preview | Analytics previews display previews of data visualization charts and single score reports in your launcher screen's analytics section. Analytics previews enable you to verify that your data is tailored for mobile use and communicates the appropriate information for users. For more information, see [Create a mobile analytics preview](https://www.servicenow.com/docs/access?context=sg-mobile-dashboard-preview&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_chart | Mobile App Builder |
| Calendar screen | Calendar screens display a calendar interface and records associated with the selected date. You can use a calendar screen to display dates that are relevant to application records. For example, you can display when tasks are due or when important events take place. For more information, see [Calendar screen](https://www.servicenow.com/docs/access?context=calendar-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_calendar_screen | Mobile App Builder |
| Chart screen | Chart screens display data visualizations created in the Analytics Center and are displayed in the analytics section of your launcher screen. Adding data visualizations helps you identify trends and turning points through indicator scores and visual representation. For more information, see [Chart screen](https://www.servicenow.com/docs/access?context=chart-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_chart_screen | Mobile App Builder |
| Custom map screen | Custom map screens enable you to create maps that display content for specific records. For more information, see [Configure a map screen](https://www.servicenow.com/docs/access?context=sg-configure-map-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_custom_map_screen | Mobile App Builder |
| Function | Functions determine what actions users can perform in your mobile application. For example, you can create a navigation function that enables users to open a record from a list, or move from an employee user profile screen to a manager user profile screen. For more information, see [Mobile functions](https://www.servicenow.com/docs/access?context=sg-studio-mobile-button-types&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_button | Mobile App Builder |
| Input form screen | Input form screens provide interfaces for users to enter information in mobile applications. For example, you can use input form screens to create or edit records, complete surveys, or any other situation where your users must enter information. For more information, see [Input form screen](https://www.servicenow.com/docs/access?context=parameter-input-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_parameter_screen | Mobile App Builder |
| Launcher screen | Launcher screens serve as landing pages or home pages. Using a launcher screen, you can access screens in various formats, search, perform quick actions, and find user information. For more information, see [Launcher screens](https://www.servicenow.com/docs/access?context=sg-mobile-applet-launcher&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_applet_launcher | Mobile App Builder |
| List screen | List screens display a list of records. Records in list screens appear in a card format, showing a limited selection of the information for the record. For more information, see [List screen](https://www.servicenow.com/docs/access?context=list-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_list_screen | Mobile App Builder |
| Map screen | Map screens display a map with locations that are associated with the records in a data item. For example, map screens can show your users where their assets are located, or which job locations they must travel to. For more information, see [Map screen](https://www.servicenow.com/docs/access?context=map-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_map_screen | Mobile App Builder |
| Mobile App config | Mobile app configs enable you to create customized mobile experiences for the Now Mobile app and Mobile Agent app. For more information, see [Configuring the Mobile Platform](https://www.servicenow.com/docs/access?context=config-mobile-platform-landing&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_native_client | Mobile App Builder |
| Mobile web screen | Mobile web screens open an external URL or a relative URL within your instance. For more information, see [Mobile web screen](https://www.servicenow.com/docs/access?context=url-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_browser_screen | Mobile App Builder |
| Record screen | Record screens display content for a specific single record. You can configure functions on record screens to enable users to make edits and perform actions. For more information, see [Record screen](https://www.servicenow.com/docs/access?context=form-screen&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_form_screen | Mobile App Builder |
[Table 9. Mobile App Builder file types]

{#servicenow-studio-file-navigator-taxonomy__table_lly_xcl_ddc}

## Mobile Card Builder files {#servicenow-studio-file-navigator-taxonomy__section_cp1_s2l_ddc}

Mobile Card Builder files enable you to edit the cards and templates used in applications for iOS and Android.
{#servicenow-studio-file-navigator-taxonomy__table_lrl_gpm_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Card | Cards are predetermined layouts that can show visuals, text, and data in mobile applications. You can define card elements and specify how elements are arranged within a card. For more information, see [Cards and icons](https://www.servicenow.com/docs/access?context=sg-cards-and-icons&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_view_config | Mobile Card Builder |
| Card template | Card templates are preconfigured layouts or frameworks that determine how information is displayed in mobile application cards. You can use the existing Mobile Card Builder card templates or create your own templates. For more information, see [Create a card template with Mobile Card Builder](https://www.servicenow.com/docs/access?context=mcb-create-template&version=zurich&pubname=zurich-mobile&ft:locale=en-US). | sys_sg_view_template | Mobile Card Builder |
[Table 10. Mobile Card Builder file types]

{#servicenow-studio-file-navigator-taxonomy__table_lrl_gpm_ddc}

## Natural Language Understanding (NLU) files {#servicenow-studio-file-navigator-taxonomy__section_mhs_4rm_ddc}

Natural Language Understanding (NLU) is a model that enables a computer to interpret, analyze, and derive meaning from human language. By creating NLU files, you build and train your application's NLU model to help it recognize user
input, or utterances, and determine the corresponding user or system actions.
{#servicenow-studio-file-navigator-taxonomy__table_zbg_bsm_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| NLU Model | A Natural Language Understanding (NLU) model is the collection of utterance examples and their associated intents and entities that an application uses as a reference to infer intents and entities in a new utterance. For more information, see [Natural Language Understanding](https://www.servicenow.com/docs/access?context=nlu-landing&version=zurich&pubname=zurich-intelligent-experiences&ft:locale=en-US). | sys_nlu_model | UI16 |
[Table 11. NLU file types]

{#servicenow-studio-file-navigator-taxonomy__table_zbg_bsm_ddc}

## Properties files {#servicenow-studio-file-navigator-taxonomy__section_d24_3bs_ddc}

Properties files are configurable parameters that enable you to change the behavior of an application without hard-coding the values directly into scripts.
{#servicenow-studio-file-navigator-taxonomy__table_zmh_xbs_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Message | Messages are the text values used in informational messages, confirmation messages, error messages, and other types of system messages in your application. For more information, see [Message table](https://www.servicenow.com/docs/access?context=r_MessageTable&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_ui_message | UI16 |
| System Property | A system property is a way to store important values for an application, like settings or configurations, that you might need in different scripts. Instead of writing these values directly into the script (hard-coding), you can store them as system properties. Creating system properties enables you to update and edit properties in one place, without having to change each script that references the values manually. For more information, see [What are application properties?](https://developer.servicenow.com/dev.do#!/learn/learning-plans/xanadu/new_to_servicenow/app_store_learnv2_automatingapps_xanadu_what_are_application_properties) and [Available system properties](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_properties | UI16 |
| System Property Category | A system property category creates the page layout for an application's system properties. The system property category page contains all the application properties in a single location. For more information, see [Create a system property category](https://developer.servicenow.com/dev.do#!/learn/learning-plans/xanadu/new_to_servicenow/app_store_learnv2_automatingapps_xanadu_create_a_system_property_category). | sys_properties_category | UI16 |
[Table 12. Properties file types]

{#servicenow-studio-file-navigator-taxonomy__table_zmh_xbs_ddc}

## Reporting files {#servicenow-studio-file-navigator-taxonomy__section_b4h_mcs_ddc}

Reporting files enable you to create and distribute reports that show the current state of instance data, such as the number of open incidents of each priority.
{#servicenow-studio-file-navigator-taxonomy__table_v1m_scs_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Chart Colors | Chart colors assign a consistent color to a grouping or stacking value in reports and dashboards. The color stays the same across reports regardless of the order of the values. For more information, see [Chart colors](https://www.servicenow.com/docs/access?context=c_ChartColors&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | sys_report_chart_color | UI16 |
| Color Definition | Color definitions enable you to maintain consistency in the platform's look and feel by applying defined colors to various UI components, such as buttons, backgrounds, text, and other elements. For more information, see [Define system colors for analytics](https://www.servicenow.com/docs/access?context=t_DefiningSystemColors&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | sys_report_color | UI16 |
| Dashboard | Dashboards enable you to display performance analytics, reporting, and other widgets on a single screen. You can use dashboards to create a story with data that you can share with other users. For more information, see [Create and use dashboards](https://www.servicenow.com/docs/access?context=create-and-edit-dashboards&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | pa_dashboards | Dashboard Builder |
| Metric Definition | A metric measures and evaluates the effectiveness of an application process. For example, a metric could measure the effectiveness of the incident resolution process by calculating how long it takes to resolve an incident. You can define metrics and create reports and dashboards using your metrics definitions. For more information, see [Metrics](https://www.servicenow.com/docs/access?context=c_MetricDefinitionSupport&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Define a metric](https://www.servicenow.com/docs/access?context=create-metric&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | metric_definition | UI16 |
| Range | Ranges are defined data intervals that are used in bar and pie charts to segment the data into logical groups. For example, you might create a range to see how many tasks were completed well within the service level agreement (SLA) and how many tasks elapsed during the SLA. For more information, see [Report ranges](https://www.servicenow.com/docs/access?context=c_ReportRanges&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | sys_report_range | UI16 |
| Report | Reports are tools used to display data visually, enabling you to gain insights, track performance, and make data-driven decisions. For example, you can create and distribute reports that show the current state of instance data, such as the number of open incidents of each priority. For more information, see [Exploring reporting](https://www.servicenow.com/docs/access?context=exploring-reporting&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | sys_report | UI16 |
| Scheduled Email of Report | Scheduled emails of reports enable you to generate and distribute scheduled reports via email. For more information, see [Schedule emails of Core UI reports](https://www.servicenow.com/docs/access?context=t_ScheduleAReport&version=zurich&pubname=zurich-now-intelligence&ft:locale=en-US). | sysauto_report | UI16 |
[Table 13. Reporting file types]

{#servicenow-studio-file-navigator-taxonomy__table_v1m_scs_ddc}

## Schedules files {#servicenow-studio-file-navigator-taxonomy__section_f2v_bfs_ddc}

Schedules can help you manage the entire life cycle of your application, from setting up maintenance schedules to defining durations and risks for operations.
{#servicenow-studio-file-navigator-taxonomy__table_nnz_pfs_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Blackout Schedule | A blackout schedule is a time during which certain activities, such as changes or updates, are restricted to avoid disruptions. You can set up blackout schedules to confirm that critical business operations remain unaffected during high-impact or sensitive times, such as holidays, end-of-quarter financial processing, or other key business events. For more information, see [Create blackout and maintenance schedules in Change Management](https://www.servicenow.com/docs/access?context=t_CreateBlkoutMaintSched&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). | cmn_schedule_blackout | UI16 |
| Maintenance Schedule | A maintenance schedule is a time during which planned maintenance activities, such as changes and updates, should take place. Maintenance schedules usually occur during low-impact times to minimize disruptions to business operations. For more information, see [Create blackout and maintenance schedules in Change Management](https://www.servicenow.com/docs/access?context=t_CreateBlkoutMaintSched&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). | cmn_schedule_maintenance | UI16 |
| Relative Duration | Relative durations are a duration type available in ServiceNow Studio that you can select when defining service level agreements (SLAs). Relative durations enable you to calculate how much time you have to work on an SLA by defining the amount of time to wait. For example, you can define a relative duration as three business days by 4pm. For more information, see [Define a relative duration](https://www.servicenow.com/docs/access?context=t_DefineARelativeDuration&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Use a relative duration](https://www.servicenow.com/docs/access?context=t_UseARelativeDuration&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | cmn_relative_duration | UI16 |
| Risk Conditions | A risk condition is a set of rules or criteria that evaluate the potential risks associated with scheduling activities, such as changes, updates, or maintenance tasks. You can define risk conditions and run risk calculations using The Best Practice - Change Risk Calculator. For more information, see [Add or modify risk and impact conditions](https://www.servicenow.com/docs/access?context=define-risk-and-impact-conditions&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US) and [Risk conditions and calculation](https://www.servicenow.com/docs/access?context=change-risk-assess-detect-conflict&version=zurich&pubname=zurich-it-service-management&ft:locale=en-US). | risk_conditions | UI16 |
| Schedule | Schedules are rules that include or exclude time for various actions or tasks. For more information, see [Schedules](https://www.servicenow.com/docs/access?context=c_UseSchedules&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Define a schedule](https://www.servicenow.com/docs/access?context=t_DefineASchedule&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | cmn_schedule | UI16 |
[Table 14. Schedules file types]

{#servicenow-studio-file-navigator-taxonomy__table_nnz_pfs_ddc}

## Security files {#servicenow-studio-file-navigator-taxonomy__section_kzk_c3s_ddc}

Security files enable you to control who has access to application data and help prevent accidental modification or deletion of data.
{#servicenow-studio-file-navigator-taxonomy__table_p1l_pjs_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Access Control | Access control, or access control lists (ACLs), restrict access to data by requiring users to pass a set of requirements before they can interact with application content. For more information, see [Explore Access Control Lists](https://www.servicenow.com/docs/access?context=exploring-access-control-list&version=zurich&pubname=zurich-platform-security&ft:locale=en-US). | sys_security_acl | UI16 |
| Public Pages | Public pages enable users to see the application content without logging in. For more information, see [Make UI pages public or private](https://www.servicenow.com/docs/access?context=t_MakeAPagePublic&version=zurich&pubname=zurich-platform-security&ft:locale=en-US). | sys_public | UI16 |
| Role | Roles determine what application access is granted to which users. For more information, see [Managing roles](https://www.servicenow.com/docs/access?context=ua-creating-roles&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Determine What Roles to Create](https://developer.servicenow.com/dev.do#!/learn/courses/vancouver/app_store_learnv2_aescreateappfromscratch_vancouver_create_an_app_from_scratch_with_app_engine_studio/app_store_learnv2_aescreateappfromscratch_vancouver_secure_apps_and_data/app_store_learnv2_aescreateappfromscratch_vancouver_determining_what_roles_to_create). | sys_user_role | UI16 |
[Table 15. Security file types]

{#servicenow-studio-file-navigator-taxonomy__table_p1l_pjs_ddc}

## Server development files {#servicenow-studio-file-navigator-taxonomy__section_rl4_nks_ddc}

Server development files manage back-end processes in ServiceNow Studio to verify that data is handled appropriately and securely.
{#servicenow-studio-file-navigator-taxonomy__table_dnf_rks_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Business Rule | A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. You can establish server-side conditions to determine when a business rule script should run and what record operations the business rule applies to. For more information, see [Classic Business rules](https://www.servicenow.com/docs/access?context=c_BusinessRules&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_script | UI16 |
| Data Policy | Data policies enable you to enforce data consistency by setting mandatory and read-only states for fields. Data policies are similar to UI policies, but UI policies only apply to data entered on a form through the standard browser. Data policies can apply rules to all data entered into the system, including data brought in through import sets or web services and data entered through the mobile UI. For more information, see [Data policy](https://www.servicenow.com/docs/access?context=c_DataPolicy&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_data_policy2 | UI16 |
| Event Registration | Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response to the conditions. By registering an event, you can define properties about the event and associate the event with the business rule that fires the event. For more information, see [Register an event](https://www.servicenow.com/docs/access?context=t_RegisterAnEvent&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sysevent_register | UI16 |
| Extension Instance | An extension instance is a registered instance of a scripted extension point that links a script include with a scripted extension point. When you want to define custom logic or methods without affecting your original code, you may consider using an extension instance. An extension instance enables you to encapsulate specific logic and functions, making it easier for you to manage, update, and debug your code. For more information, see [Using extension points to extend application functionality](https://www.servicenow.com/docs/access?context=extension-points&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_extension_instance | UI16 |
| Extension Point | An extension point designates where custom script logic can be incorporated into your code, so that you can integrate customizations and new features without altering the existing code for your application. Data or objects returned by an extension point must conform to requirements that are specified by the application creator. For more information, see [Using extension points to extend application functionality](https://www.servicenow.com/docs/access?context=extension-points&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_extension_point | UI16 |
| Fix Script | Fix scripts are server-side JavaScript that run after a custom application is installed or upgraded. You can include fix scripts to make changes that are necessary for the data integrity or product stability of an application. For more information, see [Fix scripts](https://www.servicenow.com/docs/f4qUMFmEnT~VEi1Q9qF6Ew "A fix script is server-side JavaScript code that you run after an application is installed or upgraded.") and [Create a fix script](https://www.servicenow.com/docs/FzjdC8TTfhOMOXI_OvyS8w "Create fix scripts to ensure the system installs or updates an application properly."). | sys_script_fix | UI16 |
| Scheduled Script Execution | Scheduled script executions, also known as scheduled jobs, are automated, server-side script logic that execute at a specific time or on a recurring basis. Use scheduled script executions when application processes require script logic to be executed based on a time schedule. For more information, see [What is a Scheduled Script Execution?](https://developer.servicenow.com/dev.do#!/learn/courses/washingtondc/app_store_learnv2_automatingapps_washingtondc_automating_application_logic/app_store_learnv2_automatingapps_washingtondc_scheduled_script_executions_and_events/app_store_learnv2_automatingapps_washingtondc_what_is_a_scheduled_script_execution) and [Creating a Scheduled Script Execution](https://developer.servicenow.com/dev.do#!/learn/courses/washingtondc/app_store_learnv2_automatingapps_washingtondc_automating_application_logic/app_store_learnv2_automatingapps_washingtondc_scheduled_script_executions_and_events/app_store_learnv2_automatingapps_washingtondc_creating_a_scheduled_script_execution). | sysauto_script | UI16 |
| Script Action | A script action is server-side JavaScript that is executed when a particular event is generated. For more information, see [Script actions](https://www.servicenow.com/docs/access?context=r_ScriptActions&version=zurich&pubname=zurich-build-workflows&ft:locale=en-US). | sysevent_script_action | UI16 |
| Script Include | Script includes are reusable, server-side JavaScript that define a function or class and execute only when explicitly called. For more information, see [Script includes](https://www.servicenow.com/docs/access?context=c_ScriptIncludes&version=zurich&pubname=zurich-api-reference&ft:locale=en-US) and [Script Includes](https://developer.servicenow.com/dev.do#!/learn/courses/washingtondc/app_store_learnv2_scripting_washingtondc_scripting_in_servicenow/app_store_learnv2_scripting_washingtondc_server_side_scripting/app_store_learnv2_scripting_washingtondc_script_includes). | sys_script_include | UI16 |
| UI Action | UI actions are configurations that define the behavior of buttons, links, or context menu items in your application, specifying how they interact with the server-side database. For more information, see [Defining UI actions](https://www.servicenow.com/docs/access?context=c_UIActions&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US) and [Create a UI action](https://www.servicenow.com/docs/access?context=t_EditingAUIAction&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_ui_action | UI16 |
[Table 16. Server development file types]

{#servicenow-studio-file-navigator-taxonomy__table_dnf_rks_ddc}

## User interface files {#servicenow-studio-file-navigator-taxonomy__section_jgb_2ms_ddc}

User interface files define layouts for pages, modules, and tools that users interact with. Some examples of user interface files include catalog items, guided tours, and themes.
{#servicenow-studio-file-navigator-taxonomy__table_fzd_fms_ddc__entry__4}

| File type | Description | Primary table | Primary editing experience |
|-|-|-|-|
| Application Menu | An application menu is a grouping of modules as they appear in the application navigator (UI16) or All menu (Next Experience). You can refer to an Application menu as simply an application. For more information, see [Enable or disable an application menu or module](https://www.servicenow.com/docs/access?context=t_EnDisableAppMenuOrMod&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_app_application | UI16 |
| Assessment Metric | In the Assessments application, a metric is a trait or value used to evaluate assessable records. For more information, see [Assessment metrics](https://www.servicenow.com/docs/access?context=c_AssessmentMetrics&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | asmt_metric | Survey Designer |
| Catalog | A catalog is a section of the Service Catalog where users can order items and services. A catalog is like a portal where your users can request catalog items such as service and product offerings. For example, a hardware catalog may have items to request a new keyboard or a new mouse device. For more information, see [Exploring Service Catalog](https://www.servicenow.com/docs/access?context=exploring-service-catalog&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | sc_catalog | Catalog Builder |
| Catalog Item | A catalog item is essentially a form that describes a good or service you can order in the service catalog. For example, if you're requesting time off using a catalog item, you may enter your name and requested dates off on the form. For more information, see [Service Catalog items](https://www.servicenow.com/docs/access?context=c_IntroductionToCatalogItems&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | sc_cat_item | UI16 |
| Context Menu | The context menu for a form provides controls for a list or form based on the table and user access rights. For more information, see [Form context menu](https://www.servicenow.com/docs/access?context=c_FormContextMenu&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_ui_context_menu | UI16 |
| Embedded Help | Embedded Help provides targeted help content to a user in a UI page, based on their role. Some embedded help content comes with the base instance. Your organization can add or replace embedded help content. For more information, see [Embedded Help](https://www.servicenow.com/docs/access?context=embedded-help&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_embedded_help_content | UI16 |
| Embedded Help Qualifier | An Embedded Help qualifier is an identifier that helps a ServiceNow instance identify the correct Embedded Help topic when there could be more than one topic for a UI page. For more information, see [Use qualifiers in Embedded Help](https://www.servicenow.com/docs/access?context=embedded-help-qualifiers&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_embedded_help_qualifier | UI16 |
| Guided Tour | Guided Tours contain a series of interactive steps that help users complete online tasks within their browser window to help train and onboard users working in a ServiceNow app. For more information, see [Guided Tours](https://www.servicenow.com/docs/access?context=guided-tours&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_embedded_tour_guide | UI16 |
| List | Lists display a set of records from a table, and can be filtered to refine the contents. For example, you can filter the Task list to show only Unassigned tasks. Each row in a list is a record, and each column is a field from the record. For more information, see [Lists in the classic environment](https://www.servicenow.com/docs/access?context=c_UseLists&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US) and [ServiceNow AI Platform® list administration](https://www.servicenow.com/docs/access?context=p_ListAdministration&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_ui_list | UI16 |
| List Control | List controls are settings that specify which features are available on a list, such as the New and Edit buttons. For more information, see [Configure list controls](https://www.servicenow.com/docs/access?context=t_ConfigureListControls&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | sys_ui_list_control | UI16 |
| Map Page | Map pages display ServiceNow data graphically on a Google map page based on location data that you provide. For more information, see [Map pages](https://www.servicenow.com/docs/access?context=c_MapPages&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | cmn_map_page | UI16 |
| Module | A module is any link in the application navigator (UI16) or All menu (Next Experience) that opens a page in the content frame or in a separate tab or window. For more information, see [Modules](https://developer.servicenow.com/dev.do#!/learn/courses/xanadu/app_store_learnv2_buildneedit_xanadu_build_the_needit_application/app_store_learnv2_buildneedit_xanadu_create_the_needit_application_and_application_files/app_store_learnv2_buildneedit_xanadu_modules) on the Developer Site. | sys_app_module | UI16 |
| Page Collection | Page Collections are groups of pages that can be reused across multiple experiences. For more information, see [Page collections](https://www.servicenow.com/docs/CQDST7CE2wIMpnUkCZTUSA "Page Collections are groups of pages that can be used across multiple experiences."). | sys_ux_extension_point | UI Builder |
| Portal | Portals provide users with access to the services, information, and resources they need to get their work done quickly and efficiently. Work with portals in UI Builder. For more information, see [Configure UI Builder portal experiences](https://www.servicenow.com/docs/yR1GIrXpgTNqykn_4mX87A "You can change your UI Builder custom portal experience settings to affect how your users interact with your portal experience."). | sys_ux_page_registry | UI Builder |
| Record Producer | Record producers are catalog items that enable users to create task-based records, such as incident records, from the service catalog. For more information, see [Record Producer](https://www.servicenow.com/docs/access?context=c_RecordProducer&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US). | sc_cat_item_producer | Catalog Builder - Record producer |
| Related List | Related lists appear on forms and show records in tables that have relationships to the current record. For more information, see [Related lists](https://www.servicenow.com/docs/access?context=c_RelatedLists&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_ui_related_list | UI16 |
| Schedule Page | A schedule page is a record that contains a collection of scripts that enable custom generation of a calendar or timeline display. For more information, see [Schedule Pages](https://www.servicenow.com/docs/access?context=c_SchedulePages&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | cmn_schedule_page | UI16 |
| Service Portal | Service Portal enables you to build a mobile-friendly self-service portal experience for your employees or customers. For more information, see [Service Portal](https://www.servicenow.com/docs/access?context=c_ServicePortal&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sp_portal | Service Portal |
| Style | Styles define properties such as font size, border, and alignment for text that appears in your app. For more information, see [Create a Next Experience style](https://www.servicenow.com/docs/access?context=create-next-experience-style&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US) and [Style - Scoped, Global](https://www.servicenow.com/docs/access?context=StyleBothAPI&version=zurich&pubname=zurich-api-reference&ft:locale=en-US). | sys_ui_style | UI16 |
| Template | Templates enable administrators to create reusable content. For example, an email template could have a reusable subject line and message body for email notifications. Form templates simplify the process of submitting new records by populating fields automatically. For more information, see [Email templates](https://www.servicenow.com/docs/access?context=c_EmailTemplates&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US), [Using form templates](https://www.servicenow.com/docs/access?context=c_Templates&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US), and [Page templates](https://www.servicenow.com/docs/access?context=r_PageTemplates&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_template | UI16 |
| Theme | Themes enable you to tailor the visual experience for your users, helping to update the look and feel to be more like your brand. For more information, see [Working with themes in Next Experience](https://www.servicenow.com/docs/access?context=next-experience-theming&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sys_ui_theme | UI16 |
| Timeline Page | Use timeline pages to track any activity bounded by two dates, such as change request start and end dates, or incident open and close dates. For more information, see [Timeline pages](https://www.servicenow.com/docs/access?context=c_TimelinePages&version=zurich&pubname=zurich-platform-administration&ft:locale=en-US). | cmn_timeline_page | UI16 |
| UX App Configuration | UX app configuration files store configuration settings for specific applications built with UI Builder. For more information, see [UI Builder](https://www.servicenow.com/docs/U7abvj8ugcZymnXUEXIR3w "UI Builder is a web user interface builder. Use UI Builder to build pages for App Engine Studio generated workspaces or custom web experiences using Next Experience Components and custom web components."). | sys_ux_app_config | UI16 |
| UX Application | Use UX application files to register and manage pages in UI Builder. For more information, see [UI Builder](https://www.servicenow.com/docs/U7abvj8ugcZymnXUEXIR3w "UI Builder is a web user interface builder. Use UI Builder to build pages for App Engine Studio generated workspaces or custom web experiences using Next Experience Components and custom web components."). | sys_ux_page_registry | UI16 |
| View Rule | Use view rules to force a specified view when users access a page or application. For more information, see [Create a view rule](https://www.servicenow.com/docs/access?context=t_CreateAViewRule&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). | sysrule_view | UI16 |
| Workspace | Workspaces are spaces that provide agents and managers with tools to help answer customer questions and resolve customer problems. Workspaces are primarily used for request and fulfillment processes, such as a service desk to manage tickets. For more information, see [Configurable Workspace UI](https://www.servicenow.com/docs/access?context=workspace-landing-page&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US) and [Workspace Builder](https://www.servicenow.com/docs/e7__n_Z6QFru93Ag8PU6AA "Workspace Builder enables you to quickly create and tailor custom workspaces where agents work on open records."). | sys_ux_page_registry | Workspace Builder |
[Table 17. User interface file types]

{#servicenow-studio-file-navigator-taxonomy__table_fzd_fms_ddc}