| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAgentic Workflow\n\n | \n\nAgentic 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.\n\n For more information, see [Create an agentic workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/configure-use-case-ai-agents.md).\n\n | \n\nsn\\_aia\\_usecase\n\n | \n\nAI Agent Studio\n\n |
| \n\nAI Agent\n\n | \n\nAI 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.\n\n For more information, see [Create an AI agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/configure-next-best-action-agent.md).\n\n | \n\nsn\\_aia\\_agent\n\n | \n\nAI Agent Studio\n\n |
| \n\nSkill\n\n | \n\nSkills are user-defined AI capabilities tailored to meet specific business needs. Custom skills are created using ServiceNow Otto Skill Kit, which allows for a user to define input data, prompts, LLM providers and deployment areas for custom skills.\n\n For more information, see [Create a skill](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/create-new-skill.md).\n\n | \n\nsn\\_nowassist\\_skill\\_config\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAction\n\n | \n\nActions 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.\n\n For more information, see [Exploring actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/exploring-actions.md).\n\n | \n\nsys\\_hub\\_action\\_type\\_definition\n\n | \n\nWorkflow Studio\n\n |
| \n\nActivity definition\n\n | \n\nActivity 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.\n\n For more information, see [Activity definitions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/activity-definitions.md).\n\n | \n\nsys\\_pd\\_activity\\_definition\n\n | \n\nUI16\n\n |
| \n\nConnection and Credential Aliases\n\n | \n\nConnection and credential aliases define an alias that labels a credential or connection record, enabling an app to connect to another system or component.\n\n For more information, see [Connections and Credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r-credentials.md).\n\n | \n\nsys\\_alias\n\n | \n\nUI16\n\n |
| \n\nData stream\n\n | \n\nData 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.\n\n For more information, see [Data Stream actions and pagination](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/data-stream-actions.md).\n\n | \n\nsys\\_hub\\_action\\_type\\_definition\n\n | \n\nWorkflow Studio\n\n |
| \n\nDecision table\n\n | \n\nDecision 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.\n\n For more information, see [Exploring decision tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/decision-designer-overview.md).\n\n | \n\nsys\\_decision\n\n | \n\nWorkflow Studio\n\n |
| \n\nEmail Template\n\n | \n\nEmail 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.\n\n For more information, see [Email templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_EmailTemplates.md).\n\n | \n\nsysevent\\_email\\_template\n\n | \n\nUI16\n\n |
| \n\nExternal trigger\n\n | \n\nExternal 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-saved-external-trigger.md).\n\n | \n\nsys\\_ih\\_external\\_trigger\\_definition\n\n | \n\nUI16\n\n |
| \n\nFlow\n\n | \n\nFlows 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.\n\n For more information, see [Exploring flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/exploring-flows.md).\n\n | \n\nsys\\_hub\\_flow\n\n | \n\nWorkflow Studio\n\n |
| \n\nNotification\n\n | \n\nNotifications alert users when a record changes. For example, you could get a push notification when a request is rejected.\n\n For more information, see [System notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/system-notifications-landing.md).\n\n | \n\nsysevent\\_email\\_action\n\n | \n\nUI16\n\n |
| \n\nPlaybook\n\n | \n\nPlaybooks 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.\n\n For more information, see [Building your first playbook](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/getting-started-processes.md).\n\n | \n\nsys\\_pd\\_process\\_definition\n\n | \n\nWorkflow Studio\n\n |
| \n\nSubflow\n\n | \n\nSubflows 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.\n\n For more information, see [Exploring subflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/exploring-subflows.md).\n\n | \n\nsys\\_hub\\_flow\n\n | \n\nWorkflow Studio\n\n |
| \n\nTrigger\n\n | \n\nTriggers 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/building-triggers.md).\n\n | \n\nsys\\_hub\\_trigger\\_template\n\n | \n\nWorkflow Studio\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAssignment Data Lookup\n\n | \n\nAssignment data lookups assign a record automatically using Data Lookup and Record Matching. For example, 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.\n\n For more information, see [Defining assignment rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_DefineAssignmentRules.md).\n\n | \n\ndl\\_u\\_assignment\n\n | \n\nUI16\n\n |
| \n\nClient Extension Instance\n\n | \n\nUse 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.\n\n For more information, see [Using extension points to extend application functionality](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/extension-points.md).\n\n | \n\nsys\\_client\\_extension\\_instance\n\n | \n\nUI16\n\n |
| \n\nClient Extension Point\n\n | \n\nClient 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.\n\n For more information, see [Using extension points to extend application functionality](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/extension-points.md).\n\n | \n\nsys\\_client\\_extension\\_point\n\n | \n\nUI16\n\n |
| \n\nClient Script\n\n | \n\nClient 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.\n\n For more information, see [Client scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/client-scripts.md).\n\n | \n\nsys\\_script\\_client\n\n | \n\nUI16\n\n |
| \n\nData Lookup Definitions\n\n | \n\nData 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.\n\n For more information, see [Create a catalog lookup definition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_CreatACatDataLookupDefRec.md).\n\n | \n\ndl\\_definition\n\n | \n\nUI16\n\n |
| \n\nPriority Data Lookup\n\n | \n\nPriority data lookups define the impact and urgency of an incident to calculate how it should be prioritized.\n\n For more information, see [Define priority lookup rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/def-prio-lookup-rules.md).\n\n | \n\ndl\\_u\\_priority\n\n | \n\nUI16\n\n |
| \n\nUI Extension Instance\n\n | \n\nUse 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.\n\n For more information, see [Creating and adding a UI extension point](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/impl-ui-ext-pts-base-code.md).\n\n | \n\nsys\\_ui\\_extension\\_instance\n\n | \n\nUI16\n\n |
| \n\nUI Extension Point\n\n | \n\nUI 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.\n\n For more information, see [Using UI extension points in server-side UI macros](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/ui-extension-points.md).\n\n | \n\nsys\\_ui\\_extension\\_point\n\n | \n\nUI16\n\n |
| \n\nUI Policy\n\n | \n\nUI 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.\n\n For more information, see [Using UI policies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateAUIPolicy.md).\n\n | \n\nsys\\_ui\\_policy\n\n | \n\nUI16\n\n |
| \n\nUI Script\n\n | \n\nUI scripts package client-side JavaScript into a reusable form, similar to how script includes store server-side JavaScript.\n\n For more information, see [UI scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_UIScripts.md).\n\n | \n\nsys\\_ui\\_script\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAudio\n\n | \n\nUse audio files to upload sounds and recordings that your app can use on the ServiceNow AI Platform.\n\n For more information, see [Manage audio files](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_UploadAnAudioFile.md).\n\n | \n\ndb\\_audio\n\n | \n\nUI16\n\n |
| \n\nDetailed content\n\n | \n\nUse a detailed content block to display the content of an existing document, such as an incident, knowledge article, or service management request.\n\n For more information, see [Configure a detailed content block](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_DetailedContentBlock.md).\n\n | \n\ncontent\\_block\\_detail\n\n | \n\nUI16\n\n |
| \n\nDynamic content\n\n | \n\nDynamic 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.\n\n For more information, see [Configure dynamic blocks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_CreateADynamicBlock.md).\n\n | \n\ncontent\\_block\\_programmatic\n\n | \n\nUI16\n\n |
| \n\niFrames\n\n | \n\nUse iFrames to embed a URL on a page within a frame. You can embed external pages or render ServiceNow content.\n\n For more information, see [Configure iFrames](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_IFrame.md).\n\n | \n\ncontent\\_block\\_iframe\n\n | \n\nUI16\n\n |
| \n\nImages\n\n | \n\nUpload 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.\n\n For more information, see [Storing images in the database](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_StoringImagesInTheDatabase.md).\n\n | \n\ndb\\_image\n\n | \n\nUI16\n\n |
| \n\nStatic content\n\n | \n\nUse 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.\n\n For more information, see [Configure a static HTML block](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_StaticHTMLBlock.md).\n\n | \n\ncontent\\_block\\_static\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nForm\n\n | \n\nForms are content pages that display fields and values for a single record from a database table.\n\n For more information, see [Forms in Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/form-view-configuration.md).\n\n | \n\nsys\\_ui\\_form\n\n | \n\nForm Builder\n\n |
| \n\nForm section\n\n | \n\nSections control the layout of a form. For example, you can have one column or two.\n\n For more information, see [Customize your form layout in Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/customize-form-layout.md).\n\n | \n\nsys\\_ui\\_section\n\n | \n\nForm Builder\n\n |
| \n\nMany to Many Definition\n\n | \n\nMany 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.\n\n For more information, see [Creating many-to-many task relations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_ManyToManyTaskRelations.md).\n\n | \n\nsys\\_m2m\n\n | \n\nUI16\n\n |
| \n\nRelationship\n\n | \n\nRelationships 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.\n\n For more information, see [Table relationships](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/table-relationships.md).\n\n | \n\nsys\\_relationship\n\n | \n\nUI16\n\n |
| \n\nTable\n\n | \n\nTables 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.\n\n For more information, see [ServiceNow AI Platform tables and data](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/tables-fields-and-forms.md) and [Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/tb-landing-page.md).\n\n Preferred table admins can configure preferred tables for Table Builder. For more information, see [ServiceNow Studio personas and roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-studio-classic/sn-studio-personas-roles.md).\n\n | \n\nsys\\_db\\_object\n\n | \n\nTable Builder\n\n |
| \n\nTable Column\n\n | \n\nTable 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.\n\n For more information, see [Table properties in Table Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/form-builder-glide-family-release/table-parameters.md).\n\n | \n\nsys\\_dictionary\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nData Import\n\n | \n\nData imports show all records being processed for an import job and the import jobs awaiting approvals.\n\n For more information, see [Importing data using import sets](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/c_ImportDataUsingImportSets.md) and [Integration Hub - Import](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/integrationhub-imports.md).\n\n | \n\nsn\\_ihub\\_integration\\_instance\n\n | \n\nIntegration Hub\n\n |
| \n\nData Source\n\n | \n\nData sources specify how and where to get the data you want to import.\n\n For more information, see [Data sources](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/c_DataSources.md) and [Configure a data source](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/configure-data-source.md).\n\n | \n\nsys\\_data\\_source\n\n | \n\nUI16\n\n |
| \n\nScheduled Data Import\n\n | \n\nScheduled 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.\n\n For more information, see [Run or schedule a data import](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/run-schedule-data-imports.md).\n\n | \n\nscheduled\\_import\\_set\n\n | \n\nUI16\n\n |
| \n\nScheduled Data Import\n\n | \n\nScheduled 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.\n\n For more information, see [Run or schedule a data import](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/run-schedule-data-imports.md).\n\n | \n\nscheduled\\_data\\_import\n\n | \n\nUI16\n\n |
| \n\nScripted REST API\n\n | \n\nScripted 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.\n\n For more information, see [Scripted REST APIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/c_CustomWebServices.md).\n\n | \n\nsys\\_ws\\_definition\n\n | \n\nUI16\n\n |
| \n\nScripted Web Service\n\n | \n\nScripted 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.\n\n For more information, see [Web services](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/r_AvailableWebServices.md).\n\n | \n\nsys\\_web\\_service\n\n | \n\nUI16\n\n |
| \n\nTable Transform Map\n\n | \n\nTransform 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.\n\n For more information, see [Transform maps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/c_CreatingNewTransformMaps.md).\n\n | \n\nsys\\_transform\\_map\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nExport Definition\n\n | \n\nExport definitions determine the data to include in an export set.\n\n For more information, see [Create an export definition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_CreateAnExportDefinition.md).\n\n | \n\nsys\\_export\\_definition\n\n | \n\nUI16\n\n |
| \n\nExport Set\n\n | \n\nExport sets define the data to export and the export target to use. For example, push data from an instance to an external file.\n\n For more information, see [Create an export set](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_CreateAnExportSet.md).\n\n | \n\nsys\\_export\\_set\n\n | \n\nUI16\n\n |
| \n\nExport Target\n\n | \n\nExport targets specify the target file on a MID Server to which the export set data is written.\n\n For more information, see [Create an export target](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_CreateAnExportTarget.md).\n\n | \n\nsys\\_export\\_target\n\n | \n\nUI16\n\n |
| \n\nREST Message\n\n | \n\nREST 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.\n\n For more information, see [Create a REST message](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/t_ConfiguringARESTMessage.md).\n\n | \n\nsys\\_rest\\_message\n\n | \n\nUI16\n\n |
| \n\nScheduled Data Export\n\n | \n\nScheduled 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.\n\n For more information, see [Schedule an export](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_ScheduleAnExport.md).\n\n | \n\nscheduled\\_data\\_export\n\n | \n\nUI16\n\n |
| \n\nSOAP Message\n\n | \n\nSOAP 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.\n\n For more information, see [SOAP message](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/c_SOAPMessage.md).\n\n | \n\nsys\\_soap\\_message\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nMID Server Application\n\n | \n\nThe ServiceNow MID Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network.\n\n For more information, see [MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-landing.md).\n\n | \n\necc\\_agent\\_application\n\n | \n\nUI16\n\n |
| \n\nMID Server Capability Value Test\n\n | \n\nMID 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.\n\n For more information, see [MID Server capabilities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/mid-server-capabilities.md).\n\n | \n\necc\\_agent\\_capability\\_value\\_test\n\n | \n\nUI16\n\n |
| \n\nMID Server IP Range\n\n | \n\nMID Server IP ranges specify an IP range or the specific IP address of a target.\n\n For more information, see [Configure an IP address range for the MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ConfigureMIDIPRange.md).\n\n | \n\necc\\_agent\\_ip\\_range\n\n | \n\nUI16\n\n |
| \n\nMID Server Property\n\n | \n\nMID Server properties define the behavior of one or more MID Servers.\n\n For more information, see [MID Server properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerProperties.md).\n\n | \n\necc\\_agent\\_property\n\n | \n\nUI16\n\n |
| \n\nMID Server Script File\n\n | \n\nMID Server script files synchronize to a connected MID Server.\n\n For more information, see [Attach a script file to a file synchronized MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-script-attach.md).\n\n | \n\necc\\_agent\\_script\\_file\n\n | \n\nUI16\n\n |
| \n\nMID Server Script Include\n\n | \n\nMID Server script includes make REST calls to cloud providers.\n\n For more information, see [CAPI classes in MID Server script includes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/mid-server-script-includes.md).\n\n | \n\necc\\_agent\\_script\\_include\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAnalytics preview\n\n | \n\nAnalytics 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.\n\n For more information, see [Create a mobile analytics preview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/sg-mobile-dashboard-preview.md).\n\n | \n\nsys\\_sg\\_chart\n\n | \n\nMobile App Builder\n\n |
| \n\nCalendar screen\n\n | \n\nCalendar 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.\n\n For more information, see [Calendar screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/calendar-screen.md).\n\n | \n\nsys\\_sg\\_calendar\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nCard\n\n | \n\nCards 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.\n\n For more information, see [Cards and icons](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/sg-cards-and-icons.md).\n\n | \n\nsys\\_sg\\_view\\_config\n\n | \n\nMobile Card Builder\n\n |
| \n\nCard template\n\n | \n\nCard 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.\n\n For more information, see [Create a card template with Mobile Card Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/mcb-create-template.md).\n\n | \n\nsys\\_sg\\_view\\_template\n\n | \n\nMobile Card Builder\n\n |
| \n\nChart screen\n\n | \n\nChart 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.\n\n For more information, see [Chart screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/chart-screen.md).\n\n | \n\nsys\\_sg\\_chart\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nCustom Map Screen\n\n | \n\nCustom map screens create maps that display content for specific records.\n\n For more information, see [Configure a map screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/sg-configure-map-screen.md).\n\n | \n\nsys\\_sg\\_custom\\_map\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nFunction\n\n | \n\nFunctions 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.\n\n For more information, see [Mobile functions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/sg-studio-mobile-button-types.md).\n\n | \n\nsys\\_sg\\_button\n\n | \n\nMobile App Builder\n\n |
| \n\nInput form screen\n\n | \n\nInput 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.\n\n For more information, see [Input form screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/parameter-input-screen.md).\n\n | \n\nsys\\_sg\\_parameter\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nLauncher screen\n\n | \n\nLauncher 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.\n\n For more information, see [Launcher screens](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/sg-mobile-applet-launcher.md).\n\n | \n\nsys\\_sg\\_applet\\_launcher\n\n | \n\nMobile App Builder\n\n |
| \n\nList screen\n\n | \n\nList 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.\n\n For more information, see [List screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/list-screen.md).\n\n | \n\nsys\\_sg\\_list\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nMap screen\n\n | \n\nMap 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.\n\n For more information, see [Map screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/map-screen.md).\n\n | \n\nsys\\_sg\\_map\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nMobile app config\n\n | \n\nMobile app configs create customized mobile experiences for the Now Mobile app and Mobile Agent app.\n\n For more information, see [Configuring the Mobile Platform](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/config-mobile-platform-landing.md).\n\n | \n\nsys\\_sg\\_native\\_client\n\n | \n\nMobile App Builder\n\n |
| \n\nMobile web screen\n\n | \n\nMobile web screens open an external URL or a relative URL within your instance.\n\n For more information, see [Mobile web screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/url-screen.md).\n\n | \n\nsys\\_sg\\_browser\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nRecord screen\n\n | \n\nRecord screens display content for a specific single record. Configure functions on record screens to enable users to make edits and perform actions.\n\n For more information, see [Record screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/mobile/form-screen.md).\n\n | \n\nsys\\_sg\\_form\\_screen\n\n | \n\nMobile App Builder\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nNLU Model\n\n | \n\nNatural 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.\n\n For more information, see [Natural Language Understanding](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/nlu-landing.md).\n\n | \n\nsys\\_nlu\\_model\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nMessage\n\n | \n\nMessages are the text values used in informational messages, confirmation messages, error messages, and other types of system messages in your application.\n\n For more information, see [Message table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_MessageTable.md).\n\n | \n\nsys\\_ui\\_message\n\n | \n\nUI16\n\n |
| \n\nSystem Property\n\n | \n\nSystem 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.\n\n 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_AvailableSystemProperties.md).\n\n | \n\nsys\\_properties\n\n | \n\nUI16\n\n |
| \n\nSystem Property Category\n\n | \n\nSystem property categories create the page layout for an application's system properties, displaying all application properties in a single location.\n\n 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).\n\n | \n\nsys\\_properties\\_category\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nChart Colors\n\n | \n\nChart 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.\n\n For more information, see [Chart colors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/c_ChartColors.md).\n\n | \n\nsys\\_report\\_chart\\_color\n\n | \n\nUI16\n\n |
| \n\nColor Definition\n\n | \n\nColor 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.\n\n For more information, see [Define system colors for analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/t_DefiningSystemColors.md).\n\n | \n\nsys\\_report\\_color\n\n | \n\nUI16\n\n |
| \n\nDashboard\n\n | \n\nDashboards 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.\n\n For more information, see [Create and use Core UI dashboards](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/create-and-edit-dashboards.md).\n\n | \n\npa\\_dashboards\n\n | \n\nDashboard Builder\n\n |
| \n\nMetric Definition\n\n | \n\nMetric 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.\n\n For more information, see [Metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_MetricDefinitionSupport.md) and [Define a metric](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-metric.md).\n\n | \n\nmetric\\_definition\n\n | \n\nUI16\n\n |
| \n\nRange\n\n | \n\nRanges 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.\n\n For more information, see [Report ranges](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/c_ReportRanges.md).\n\n | \n\nsys\\_report\\_range\n\n | \n\nUI16\n\n |
| \n\nReport\n\n | \n\nReports 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.\n\n For more information, see [Exploring reporting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/exploring-reporting.md).\n\n | \n\nsys\\_report\n\n | \n\nUI16\n\n |
| \n\nScheduled Email of Report\n\n | \n\nScheduled emails of reports generate and distribute scheduled reports via email.\n\n For more information, see [Schedule emails of Core UI reports](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/now-intelligence/t_ScheduleAReport.md).\n\n | \n\nsysauto\\_report\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nBlackout Schedule\n\n | \n\nBlackout 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.\n\n For more information, see [Create blackout and maintenance schedules in Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/t_CreateBlkoutMaintSched.md).\n\n | \n\ncmn\\_schedule\\_blackout\n\n | \n\nUI16\n\n |
| \n\nMaintenance Schedule\n\n | \n\nMaintenance 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.\n\n For more information, see [Create blackout and maintenance schedules in Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/t_CreateBlkoutMaintSched.md).\n\n | \n\ncmn\\_schedule\\_maintenance\n\n | \n\nUI16\n\n |
| \n\nRelative Duration\n\n | \n\nRelative 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.\n\n For more information, see [Define a relative duration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_DefineARelativeDuration.md) and [Use a relative duration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_UseARelativeDuration.md).\n\n | \n\ncmn\\_relative\\_duration\n\n | \n\nUI16\n\n |
| \n\nRisk Conditions\n\n | \n\nRisk 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.\n\n For more information, see [Add or modify risk and impact conditions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/define-risk-and-impact-conditions.md) and [Risk conditions and calculation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/change-risk-assess-detect-conflict.md).\n\n | \n\nrisk\\_conditions\n\n | \n\nUI16\n\n |
| \n\nSchedule\n\n | \n\nSchedules are rules that include or exclude time for various actions or tasks.\n\n For more information, see [Schedules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_UseSchedules.md) and [Define a schedule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_DefineASchedule.md).\n\n | \n\ncmn\\_schedule\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nAccess Control\n\n | \n\nAccess 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.\n\n For more information, see [Explore Access Control Lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/exploring-access-control-list.md).\n\n | \n\nsys\\_security\\_acl\n\n | \n\nUI16\n\n |
| \n\nPublic Pages\n\n | \n\nPublic pages allow users to see the application content without logging in.\n\n For more information, see [Make UI pages public or private](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/t_MakeAPagePublic.md).\n\n | \n\nsys\\_public\n\n | \n\nUI16\n\n |
| \n\nRole\n\n | \n\nRoles determine what application access is granted to which users.\n\n For more information, see [Managing roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/ua-creating-roles.md) 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).\n\n | \n\nsys\\_user\\_role\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nBusiness Rule\n\n | \n\nBusiness 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.\n\n For more information, see [Classic Business rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/c_BusinessRules.md).\n\n | \n\nsys\\_script\n\n | \n\nUI16\n\n |
| \n\nData Policy\n\n | \n\nData 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.\n\n For more information, see [Data policy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_DataPolicy.md).\n\n | \n\nsys\\_data\\_policy2\n\n | \n\nUI16\n\n |
| \n\nEvent Registration\n\n | \n\nEvents 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.\n\n For more information, see [Register an event](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/t_RegisterAnEvent.md).\n\n | \n\nsysevent\\_register\n\n | \n\nUI16\n\n |
| \n\nExtension Instance\n\n | \n\nExtension 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.\n\n For more information, see [Using extension points to extend application functionality](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/extension-points.md).\n\n | \n\nsys\\_extension\\_instance\n\n | \n\nUI16\n\n |
| \n\nExtension Point\n\n | \n\nExtension 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.\n\n For more information, see [Using extension points to extend application functionality](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/extension-points.md).\n\n | \n\nsys\\_extension\\_point\n\n | \n\nUI16\n\n |
| \n\nFix Script\n\n | \n\nFix 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.\n\n For more information, see [Fix scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/c_FixScripts.md) and [Create a fix script](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/t_CreateFixScripts.md).\n\n | \n\nsys\\_script\\_fix\n\n | \n\nUI16\n\n |
| \n\nScheduled Script Execution\n\n | \n\nScheduled 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.\n\n 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).\n\n | \n\nsysauto\\_script\n\n | \n\nUI16\n\n |
| \n\nScript Action\n\n | \n\nScript actions are server-side JavaScript that executes when a particular event is generated.\n\n For more information, see [Script actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/r_ScriptActions.md).\n\n | \n\nsysevent\\_script\\_action\n\n | \n\nUI16\n\n |
| \n\nScript Include\n\n | \n\nScript includes are reusable, server-side JavaScript that define a function or class and execute only when explicitly called.\n\n For more information, see [Script includes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_ScriptIncludes.md) 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).\n\n | \n\nsys\\_script\\_include\n\n | \n\nUI16\n\n |
| \n\nUI Action\n\n | \n\nUI actions define the behavior of buttons, links, or context menu items in your application, specifying how they interact with the server-side database.\n\n For more information, see [Defining UI actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_UIActions.md) and [Create a UI action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_EditingAUIAction.md).\n\n | \n\nsys\\_ui\\_action\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nComponents\n\n | \n\nComponents 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/work-components.md).\n\n | \n\nsys\\_ux\\_macroponent\n\n | \n\nUI16\n\n |
| \n\nControllers\n\n | \n\nControllers 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:\n\n- Data controllers contain data resources and can be manually added to a page.\n- UI controllers are added to pages when using page templates and cannot be added manually.\n\nFor more information, see [Bind data to UI Builder pages using controllers \\(advanced feature\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/controllers.md).\n\n | \n\nsys\\_ux\\_controller\n\n | \n\nUI16\n\n |
| \n\nExperiences\n\n | \n\nExperiences are a collection of web pages for users to interact with an application.For more information, see [Create an experience for UI Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/create-experience.md).\n\n | \n\nsys\\_ux\\_page\\_registry\n\n | \n\nUI16\n\n |
| \n\nPage collections\n\n | \n\nPage collections are groups of pages that can be reused in experiences within tabs or modals.For more information, see [Page collections](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/page-collections.md).\n\n | \n\nsys\\_ux\\_extension\\_point\n\n | \n\nUI16\n\n |
| \n\nUI interactions\n\n | \n\nUI 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/uib-ui-interactions.md).\n\n | \n\nsys\\_ui\\_interaction\n\n | \n\nUI16\n\n |
| \n\nFile type\n\n | \n\nDescription\n\n | \n\nPrimary table\n\n | \n\nPrimary editing experience\n\n |
|---|---|---|---|
| \n\nApplication Module\n\n | \n\nApplication modules 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.\n\n For more information, see [Enable or disable an application menu or module](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_EnDisableAppMenuOrMod.md).\n\n | \n\nsys\\_app\\_application\n\n | \n\nUI16\n\n |
| \n\nAssessment Metric\n\n | \n\nIn the Assessments application, metrics are traits or values used to evaluate assessable records.\n\n For more information, see [Assessment metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_AssessmentMetrics.md).\n\n | \n\nasmt\\_metric\n\n | \n\nSurvey Designer\n\n |
| \n\nCatalog\n\n | \n\nCatalogs 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.\n\n For more information, see [Exploring Service Catalog](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/exploring-service-catalog.md).\n\n | \n\nsc\\_catalog\n\n | \n\nCatalog Builder\n\n |
| \n\nCatalog Item\n\n | \n\nCatalog 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.\n\n For more information, see [Service Catalog items](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_IntroductionToCatalogItems.md).\n\n | \n\nsc\\_cat\\_item\n\n | \n\nUI16\n\n |
| \n\nContext Menu\n\n | \n\nContext menus for forms provide controls for a list or form based on the table and user access rights.\n\n For more information, see [Form context menu](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_FormContextMenu.md).\n\n | \n\nsys\\_ui\\_context\\_menu\n\n | \n\nUI16\n\n |
| \n\nEmbedded Help\n\n | \n\nEmbedded 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.\n\n For more information, see [Embedded Help](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/embedded-help.md).\n\n | \n\nsys\\_embedded\\_help\\_content\n\n | \n\nUI16\n\n |
| \n\nEmbedded Help Qualifier\n\n | \n\nEmbedded 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.\n\n For more information, see [Use qualifiers in Embedded Help](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/embedded-help-qualifiers.md).\n\n | \n\nsys\\_embedded\\_help\\_qualifier\n\n | \n\nUI16\n\n |
| \n\nGuided Tour\n\n | \n\nGuided 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.\n\n For more information, see [Guided Tours](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/guided-tours.md).\n\n | \n\nsys\\_embedded\\_tour\\_guide\n\n | \n\nUI16\n\n |
| \n\nList\n\n | \n\nLists 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.\n\n For more information, see [Lists in the classic environment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_UseLists.md) and [ServiceNow AI Platform® list administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/p_ListAdministration.md).\n\n | \n\nsys\\_ui\\_list\n\n | \n\nUI16\n\n |
| \n\nList Control\n\n | \n\nList controls specify which features are available on a list, such as the **New** and **Edit** buttons.\n\n For more information, see [Configure list controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_ConfigureListControls.md).\n\n | \n\nsys\\_ui\\_list\\_control\n\n | \n\nUI16\n\n |
| \n\nMap Page\n\n | \n\nMap pages display ServiceNow data graphically on a Google map page based on location data that you provide.\n\n For more information, see [Map pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_MapPages.md).\n\n | \n\ncmn\\_map\\_page\n\n | \n\nUI16\n\n |
| \n\nModule\n\n | \n\nModules 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.\n\n 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.\n\n | \n\nsys\\_app\\_module\n\n | \n\nUI16\n\n |
| \n\nPortal\n\n | \n\nPortals provide users with access to the services, information, and resources they need to complete their work. Work with portals in UI Builder.\n\n For more information, see [Configure UI Builder portal experiences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/ui-builder/ui-builder-portal-settings.md).\n\n | \n\nsys\\_ux\\_page\\_registry\n\n | \n\nUI Builder\n\n |
| \n\nRecord Producer\n\n | \n\nRecord producers are catalog items that create task-based records, such as incident records, from the service catalog.\n\n For more information, see [Record Producer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_RecordProducer.md).\n\n | \n\nsc\\_cat\\_item\\_producer\n\n | \n\nCatalog Builder - Record producer\n\n |
| \n\nRelated List\n\n | \n\nRelated lists appear on forms and show records in tables that have relationships to the current record.\n\n For more information, see [Related lists](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_RelatedLists.md).\n\n | \n\nsys\\_ui\\_related\\_list\n\n | \n\nUI16\n\n |
| \n\nSchedule Page\n\n | \n\nSchedule pages are records that contain a collection of scripts that enable custom generation of a calendar or timeline display.\n\n For more information, see [Schedule Pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_SchedulePages.md).\n\n | \n\ncmn\\_schedule\\_page\n\n | \n\nUI16\n\n |
| \n\nService Portal\n\n | \n\nService Portal builds a mobile-friendly self-service portal experience for employees or customers.\n\n For more information, see [Service Portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_ServicePortal.md).\n\n | \n\nsp\\_portal\n\n | \n\nService Portal\n\n |
| \n\nStyle\n\n | \n\nStyles define properties such as font size, border, and alignment for text that appears in your app.\n\n For more information, see [Create a Next Experience style](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/create-next-experience-style.md) and [Style - Scoped, Global](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/server-api-reference/StyleBothAPI.md).\n\n | \n\nsys\\_ui\\_style\n\n | \n\nUI16\n\n |
| \n\nTemplate\n\n | \n\nTemplates 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.\n\n For more information, see [Email templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_EmailTemplates.md), [Using form templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_Templates.md), and [Page templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/r_PageTemplates.md).\n\n | \n\nsys\\_template\n\n | \n\nUI16\n\n |
| \n\nTheme\n\n | \n\nThemes tailor the visual experience for users by updating the look and feel to match your brand.\n\n For more information, see [Working with themes in Next Experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/next-experience-theming.md).\n\n | \n\nsys\\_ui\\_theme\n\n | \n\nUI16\n\n |
| \n\nTimeline Page\n\n | \n\nTimeline pages track any activity bounded by two dates, such as change request start and end dates, or incident open and close dates.\n\n For more information, see [Timeline pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_TimelinePages.md).\n\n | \n\ncmn\\_timeline\\_page\n\n | \n\nUI16\n\n |
| \n\nUI Page\n\n | \n\nUI pages can be used to create and display forms, dialogs, lists, and other UI components. Use UI pages as widgets on dashboards. To find the UI pages, navigate to System UI > UI Pages.\n\n For more information, see [UI pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/r_UIPages.md).\n\n | \n\nsys\\_ui\\_page\n\n | \n\nFluent source\n\n |
| \n\nView Rule\n\n | \n\nView rules force a specified view when users access a page or application.\n\n For more information, see [Create a view rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_CreateAViewRule.md).\n\n | \n\nsysrule\\_view\n\n | \n\nUI16\n\n |
| \n\nWorkspace\n\n | \n\nWorkspaces 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.\n\n For more information, see [Configurable Workspace UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/workspace-landing-page.md) and [Workspace Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/workspace-builder/workspace-builder-landing.md).\n\n | \n\nsys\\_ux\\_page\\_registry\n\n | \n\nWorkspace Builder\n\n |