ServiceNow Studio Navigator panel taxonomy
Reference 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, the following sections list the available file types 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.
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.
AI files
AI files provide ways to use generative AI to enhance user productivity 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.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Agentic Workflow | Agentic workflows are 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. | 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. | 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. | sn\_nowassist\_skill\_config | UI16 |
Automation files
Automations manage recurring tasks with fewer steps, reducing human input and effort. For example, configure an email notification to send automatically when a record is approved. Add automations such as actions, flows, and other automatic tasks to streamline how apps work.
| 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. | 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. | sys\_pd\_activity\_definition | UI16 |
| Connection and Credential Aliases | Connection and credential aliases define 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. | sys\_alias | UI16 |
| Data stream | Data streams are reusable actions that process 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. | 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. | 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. | sysevent\_email\_template | UI16 |
| External trigger | External triggers are reusable triggers that respond to external events through webhooks. When an event occurs in the configured third-party application that meets the specified conditions, the trigger is activated.For more information, see Create a saved external trigger. | sys\_ih\_external\_trigger\_definition | 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. | 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. | 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 Building your first playbook. | 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 do not have a trigger but instead run when called from a playbook, flow, another subflow, or a script. For more information, see Exploring subflows. | sys\_hub\_flow | Workflow Studio |
| Trigger | Triggers contain the start conditions for your automation. You can create separate triggers for each flow or create a reusable saved trigger that you can use in multiple flows.For more information, see Building triggers. | sys\_hub\_trigger\_template | Workflow Studio |
Client development files
Client development files define operations that occur based on actions users take when working with an app built in ServiceNow Studio.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Assignment Data Lookup | Assignment data lookups 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. | 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. | 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 help prevent custom code interactions from breaking after an upgrade when custom code is directly embedded into application code. For more information, see Using extension points to extend application functionality. | sys\_client\_extension\_point | UI16 |
| Client Script | Client scripts run JavaScript on the client \(web browser\) when client-based events occur. For example, a client script could run when a form loads, after form submission, or when a field changes value. For more information, see Client scripts. | sys\_script\_client | UI16 |
| Data Lookup Definitions | Data lookup definitions are no-code solutions that retrieve 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. | dl\_definition | UI16 |
| Priority Data Lookup | Priority data lookups define the impact and urgency of an incident to calculate how it should be prioritized. For more information, see Define priority lookup rules. | 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. | sys\_ui\_extension\_instance | UI16 |
| UI Extension Point | UI extension points add custom content to a UI page without modifying the page directly. Create the UI extension points first, 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. | 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, 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. | sys\_ui\_policy | UI16 |
| UI Script | UI scripts package client-side JavaScript into a reusable form, similar to how script includes store server-side JavaScript. For more information, see UI scripts. | sys\_ui\_script | UI16 |
Content files
Content files 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 built in ServiceNow Studio.
| 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. | 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. | 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. | 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. | content\_block\_iframe | UI16 |
| Images | Upload and store images on the ServiceNow AI Platform to be used in apps and forms. 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. | db\_image | UI16 |
| Static content | Use static blocks for text that does not 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. | content\_block\_static | UI16 |
Data files
Data files store and reference the information that applications consume. Start with a table, or upload spreadsheets and PDFs to get data into the ServiceNow AI Platform for apps to use.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Form | Forms are content pages that display fields and values for a single record from a database table. For more information, see Forms in Table Builder. | sys\_ui\_form | Form Builder |
| Form section | Sections control 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. | sys\_ui\_section | Form Builder |
| Many to Many Definition | Many to many tasks 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. | sys\_m2m | UI16 |
| Relationship | Relationships 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. | 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 and Table Builder. Preferred table admins can configure preferred tables for Table Builder. For more information, see ServiceNow Studio personas and roles. | sys\_db\_object | Table Builder |
| Table Column | Table columns represent 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. | sys\_dictionary | UI16 |
Inbound integration files
Inbound integrations bring information and data onto the ServiceNow AI Platform from another system or source, enabling data flow from external systems into ServiceNow.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Data Import | Data imports show all records being processed for an import job and the import jobs awaiting approvals. For more information, see Importing data using import sets and Integration Hub - Import. | sn\_ihub\_integration\_instance | Integration Hub |
| Data Source | Data sources specify how and where to get the data you want to import. For more information, see Data sources and Configure a data source. | 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. | 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. | scheduled\_data\_import | UI16 |
| Scripted REST API | Scripted REST APIs build custom web service APIs for your application. You can define service endpoints, query parameters, and headers for a scripted REST API, and scripts to manage the request and response. For more information, see Scripted REST APIs. | 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. | 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. | sys\_transform\_map | UI16 |
Outbound integration files
Outbound integrations send data from the ServiceNow AI Platform to an external system or source.
| 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. | sys\_export\_definition | UI16 |
| Export Set | Export sets define the data to export and the export target to use. For example, push data from an instance to an external file. For more information, see Create an export set. | sys\_export\_set | UI16 |
| Export Target | Export targets specify the target file on a MID Server to which the export set data is written. For more information, see Create an export target. | sys\_export\_target | UI16 |
| REST Message | REST messages store 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. | sys\_rest\_message | UI16 |
| Scheduled Data Export | Scheduled data exports specify a schedule for running export sets. A single export can be scheduled, or regular intervals can be scheduled with support for delta records only. For more information, see Schedule an export. | scheduled\_data\_export | UI16 |
| SOAP Message | SOAP messages store 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. | sys\_soap\_message | UI16 |
MID Server files
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.
| 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. | 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\). Use value tests to create capabilities that find devices using values without requiring exact string matching. For more information, see MID Server capabilities. | ecc\_agent\_capability\_value\_test | UI16 |
| MID Server IP Range | MID Server IP ranges 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. | ecc\_agent\_ip\_range | UI16 |
| MID Server Property | MID Server properties define the behavior of one or more MID Servers. For more information, see MID Server properties. | ecc\_agent\_property | UI16 |
| MID Server Script File | MID Server script files synchronize to a connected MID Server. For more information, see Attach a script file to a file synchronized MID Server. | ecc\_agent\_script\_file | UI16 |
| MID Server Script Include | MID Server script includes make REST calls to cloud providers. For more information, see CAPI classes in MID Server script includes. | ecc\_agent\_script\_include | UI16 |
Mobile files
Mobile App Builder builds and manages screens and records that make up workflows within ServiceNow mobile apps. Mobile Card Builder files edit the cards and templates used in applications for iOS and Android.
| 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 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. | sys\_sg\_chart | Mobile App Builder |
| Calendar screen | Calendar screens display a calendar interface and records associated with the selected date. Use a calendar screen to display dates relevant to application records. For example, display when tasks are due or when important events take place. For more information, see Calendar screen. | sys\_sg\_calendar\_screen | Mobile App Builder |
| 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. | 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. 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. | sys\_sg\_view\_template | Mobile Card Builder |
| Chart screen | Chart screens display data visualizations created in the Analytics Overview in the analytics section of your launcher screen. Adding data visualizations helps identify trends and turning points through indicator scores and visual representation. For more information, see Chart screen. | sys\_sg\_chart\_screen | Mobile App Builder |
| Custom Map Screen | Custom map screens create maps that display content for specific records. For more information, see Configure a map screen. | sys\_sg\_custom\_map\_screen | Mobile App Builder |
| Function | Functions determine what actions users can perform in your mobile application. For example, 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. | sys\_sg\_button | Mobile App Builder |
| Input form screen | Input form screens provide interfaces for users to enter information in mobile applications. For example, use input form screens to create or edit records, complete surveys, or any other situation where users must enter information. For more information, see Input form screen. | 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. | 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. | sys\_sg\_list\_screen | Mobile App Builder |
| Map screen | Map screens display a map with locations associated with the records in a data item. For example, map screens can show users where their assets are located, or which job locations they must travel to. For more information, see Map screen. | sys\_sg\_map\_screen | Mobile App Builder |
| Mobile app config | Mobile app configs create customized mobile experiences for the Now Mobile app and Mobile Agent app. For more information, see Configuring the Mobile Platform. | 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. | sys\_sg\_browser\_screen | Mobile App Builder |
| Record screen | Record screens display content for a specific single record. Configure functions on record screens to enable users to make edits and perform actions. For more information, see Record screen. | sys\_sg\_form\_screen | Mobile App Builder |
Natural Language Understanding (NLU) files
Natural Language Understanding (NLU) is a model that enables a computer to interpret, analyze, and derive meaning from human language. Create NLU files to build and train an application's NLU model to recognize user input, or utterances, and determine the corresponding user or system actions.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| NLU Model | Natural Language Understanding \(NLU\) models are 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. | sys\_nlu\_model | UI16 |
Properties files
Properties files are configurable parameters that change the behavior of an application without hard-coding values directly into scripts.
| 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. | sys\_ui\_message | UI16 |
| System Property | System properties store important values for an application, such as settings or configurations, that scripts may need to reference. Storing values as system properties allows updates in one place without changing each script that references the values. For more information, see What are application properties? and Available system properties. | sys\_properties | UI16 |
| System Property Category | System property categories create the page layout for an application's system properties, displaying all application properties in a single location. For more information, see Create a system property category. | sys\_properties\_category | UI16 |
Reporting files
Reporting files create and distribute reports that show the current state of instance data, such as the number of open incidents of each priority.
| 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. | sys\_report\_chart\_color | UI16 |
| Color Definition | Color definitions 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. | sys\_report\_color | UI16 |
| Dashboard | Dashboards display performance analytics, reporting, and other widgets on a single screen. Use dashboards to create a story with data that you can share with other users. For more information, see Create and use dashboards. | pa\_dashboards | Dashboard Builder |
| Metric Definition | Metric definitions measure and evaluate 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. Define metrics and create reports and dashboards using your metrics definitions. For more information, see Metrics and Define a metric. | metric\_definition | UI16 |
| Range | Ranges are defined data intervals used in bar and pie charts to segment data into logical groups. For example, 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. | sys\_report\_range | UI16 |
| Report | Reports display data visually to provide insights, track performance, and support data-driven decisions. For example, 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. | sys\_report | UI16 |
| Scheduled Email of Report | Scheduled emails of reports generate and distribute scheduled reports via email. For more information, see Schedule emails of Core UI reports. | sysauto\_report | UI16 |
Schedules files
Schedules manage the life cycle of an application, from setting up maintenance schedules to defining durations and risks for operations.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Blackout Schedule | Blackout schedules are times during which certain activities, such as changes or updates, are restricted to avoid disruptions. 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. | cmn\_schedule\_blackout | UI16 |
| Maintenance Schedule | Maintenance schedules are times 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. | 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 calculate how much time is available to work on an SLA by defining the amount of time to wait. For example, define a relative duration as three business days by 4pm. For more information, see Define a relative duration and Use a relative duration. | cmn\_relative\_duration | UI16 |
| Risk Conditions | Risk conditions are sets of rules or criteria that evaluate the potential risks associated with scheduling activities, such as changes, updates, or maintenance tasks. 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 and Risk conditions and calculation. | risk\_conditions | UI16 |
| Schedule | Schedules are rules that include or exclude time for various actions or tasks. For more information, see Schedules and Define a schedule. | cmn\_schedule | UI16 |
Security files
Security files control who has access to application data and help prevent accidental modification or deletion of data.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Access Control | Access controls, 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. | sys\_security\_acl | UI16 |
| Public Pages | Public pages allow users to see the application content without logging in. For more information, see Make UI pages public or private. | sys\_public | UI16 |
| Role | Roles determine what application access is granted to which users. For more information, see Managing roles and Determine What Roles to Create. | sys\_user\_role | UI16 |
Server development files
Server development files manage back-end processes in ServiceNow Studio to verify that data is handled appropriately and securely.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Business Rule | Business rules are a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. 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. | sys\_script | UI16 |
| Data Policy | Data policies 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 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. | 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. 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. | sysevent\_register | UI16 |
| Extension Instance | Extension instances are registered instances of a scripted extension point that links a script include with a scripted extension point. Use an extension instance to define custom logic or methods without affecting original code. An extension instance encapsulates specific logic and functions, making it easier to manage, update, and debug code. For more information, see Using extension points to extend application functionality. | sys\_extension\_instance | UI16 |
| Extension Point | Extension points designate where custom script logic can be incorporated into your code to integrate customizations and new features without altering existing application code. Data or objects returned by an extension point must conform to requirements specified by the application creator. For more information, see Using extension points to extend application functionality. | sys\_extension\_point | UI16 |
| Fix Script | Fix scripts are server-side JavaScript that run after a custom application is installed or upgraded. Include fix scripts to make changes necessary for the data integrity or product stability of an application. For more information, see Fix scripts and Create a fix script. | 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 execute based on a time schedule. For more information, see What is a Scheduled Script Execution? and Creating a Scheduled Script Execution. | sysauto\_script | UI16 |
| Script Action | Script actions are server-side JavaScript that executes when a particular event is generated. For more information, see Script actions. | 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 and Script Includes. | sys\_script\_include | UI16 |
| UI Action | UI actions 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 and Create a UI action. | sys\_ui\_action | UI16 |
UI Builder files
UI Builder files build pages for workspaces generated in ServiceNow Studio, or custom web experiences using Next Experience Components and custom web components.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Components | Components are used in the UI Builder to build pages. Components have an interface that an end user can view and interact with. Components can talk to each other through events and properties. Commonly used components include Heading, Image, List, Form, and Button.For more information, see Customize UI Builder pages using components. | sys\_ux\_macroponent | UI16 |
| Controllers | Controllers are a type of data resource that includes data and event logic and enables component presets. Controllers are added automatically when using a page template. There are two types of controllers: - Data controllers contain data resources and can be manually added to a page. - UI controllers are added to pages when using page templates and cannot be added manually. For more information, see Bind data to UI Builder pages using controllers (advanced feature). | sys\_ux\_controller | UI16 |
| Experiences | Experiences are a collection of web pages for users to interact with an application.For more information, see Create an experience for UI Builder. | sys\_ux\_page\_registry | UI16 |
| Page collections | Page collections are groups of pages that can be reused in experiences within tabs or modals.For more information, see Page collections. | sys\_ux\_extension\_point | UI16 |
| UI interactions | UI interactions are reusable flows that combine UI elements and logic into a single unit that you can trigger from component events in UI Builder. They help avoid repeating the same wiring across multiple pages and make designs easier to maintain.For more information, see UI interactions. | sys\_ui\_interaction | UI16 |
User interface files
User interface files define layouts for pages, modules, and tools that users interact with. Examples include catalog items, guided tours, and themes.
| File type | Description | Primary table | Primary editing experience |
|---|---|---|---|
| Application Menu | Application menus are groupings 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. | sys\_app\_application | UI16 |
| Assessment Metric | In the Assessments application, metrics are traits or values used to evaluate assessable records. For more information, see Assessment metrics. | asmt\_metric | Survey Designer |
| Catalog | Catalogs are sections of the Service Catalog where users can order items and services. A catalog is like a portal where 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. | sc\_catalog | Catalog Builder |
| Catalog Item | Catalog items are forms that describe a good or service available to order in the service catalog. For example, when 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. | sc\_cat\_item | UI16 |
| Context Menu | Context menus for forms provide controls for a list or form based on the table and user access rights. For more information, see Form context menu. | 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. | sys\_embedded\_help\_content | UI16 |
| Embedded Help Qualifier | Embedded Help qualifiers are identifiers that help 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. | 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 train and onboard users working in a ServiceNow app. For more information, see Guided Tours. | 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, 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 and ServiceNow AI Platform® list administration. | sys\_ui\_list | UI16 |
| List Control | List controls specify which features are available on a list, such as the New and Edit buttons. For more information, see Configure list controls. | 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. | cmn\_map\_page | UI16 |
| Module | Modules are any links 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 on the Developer Site. | sys\_app\_module | UI16 |
| Portal | Portals provide users with access to the services, information, and resources they need to complete their work. Work with portals in UI Builder. For more information, see Configure UI Builder portal experiences. | sys\_ux\_page\_registry | UI Builder |
| Record Producer | Record producers are catalog items that create task-based records, such as incident records, from the service catalog. For more information, see Record Producer. | 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. | sys\_ui\_related\_list | UI16 |
| Schedule Page | Schedule pages are records that contain a collection of scripts that enable custom generation of a calendar or timeline display. For more information, see Schedule Pages. | cmn\_schedule\_page | UI16 |
| Service Portal | Service Portal builds a mobile-friendly self-service portal experience for employees or customers. For more information, see Service Portal. | 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 and Style - Scoped, Global. | sys\_ui\_style | UI16 |
| Template | Templates create reusable content for administrators. 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, Using form templates, and Page templates. | sys\_template | UI16 |
| Theme | Themes tailor the visual experience for users by updating the look and feel to match your brand. For more information, see Working with themes in Next Experience. | sys\_ui\_theme | UI16 |
| Timeline Page | Timeline pages 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. | cmn\_timeline\_page | UI16 |
| View Rule | View rules force a specified view when users access a page or application. For more information, see Create a view rule. | sysrule\_view | UI16 |
| Workspace | Workspaces provide agents and managers with tools to 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 and Workspace Builder. | sys\_ux\_page\_registry | Workspace Builder |
Parent Topic:ServiceNow Studio reference