{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1879,"path":"application-development/build-agent-supported-metadata.md","title":"Supported metadata in Build Agent","bundle":null,"doc_type":null,"release":"australia","body":"\n# Supported metadata in Build Agent\n\nMetadata and app file types that Build Agent can create and manage.\n\nFor metadata types not listed in this table, query Build Agent directly.\n\n**Important:** Build Agent and Autonomous Engineer only create metadata supported by ServiceNow® Fluent. For more information, see [ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-fluent.md). For the latest API reference, see [https://servicenow.github.io/sdk/](https://servicenow.github.io/sdk/)\n\n\n
\n\nMetadata type\n\n\n\nDescription\n\n
\n\nAutomated Test Framework \\(ATF\\) tests\n\n\n\nAutomated test cases for validating application behavior.\n\n
\n\nApplication menus and modules\n\n\n\nApplication menus are the top-level categories in the application navigator sidebar. Modules are the individual links within those categories and can link to tables, URLs, lists, or other platform resources. When Build Agent creates a new application with tables, it generates the corresponding navigator structure so users can access the application from the sidebar.\n\n
\n\nAssignment rules\n\n\n\nRules that automatically assign records to users or groups based on field conditions.\n\n
\n\nBusiness rules\n\n\n\nServer-side scripts that run when records are displayed, inserted, updated, or deleted.\n\n
\n\nChoice lists\n\n\n\nField value options for select fields on forms and tables.\n\n
\n\nClient scripts\n\n\n\nScripts that run in the browser to control form behavior.\n\n
\n\nClient-side logic\n\n\n\nBrowser-based logic for controlling UI interactions and form behavior.\n\n
\n\nCondition builder and query conditions\n\n\n\nFilter conditions used in business rules, workflows, and list views.\n\n
\n\nConfiguration\n\n\n\nSystem and application configuration settings.\n\n
\n\nConnection and credential alias\n\n\n\nExternal system connections and stored credentials for authenticating with third-party services and platforms.\n\n
\n\nCustom AI agents\n\n\n\nAI agents scoped to application data models, roles, and ACLs. For more information, see [Create agentic workflows, agents, and skills](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/create-custom-ai-agent.md).\n\n
\n\nData policies\n\n\n\nRules that enforce field-level data requirements, such as mandatory or read-only constraints, across all interfaces including the API.\n\n
\n\nData import pipeline\n\n\n\nBuild Agent creates the full data import pipeline: data sources, staging tables, import sets, and transform maps. Supported source types include CSV, Excel, JSON, XML, JDBC, LDAP, and REST. Specify the external data source, target table, and field mapping, and Build Agent generates the pipeline artifacts. The capability covers both one-time bulk loads and recurring scheduled imports.\n\n
\n\nData lookup\n\n\n\nMetadata definitions for data lookup fields that retrieve values from related tables or external sources.\n\n
\n\nDictionary overrides\n\n\n\nField-level customizations that override base system dictionary entries without modifying the original.\n\n
\n\nEvent registry configurations\n\n\n\nEvent definitions that trigger notifications, scripts, or other platform actions.\n\n
\n\nField-level overrides\n\n\n\nAttribute overrides applied at the field level on extended tables.\n\n
\n\nFlows\n\n\n\nAutomated processes built in Workflow Studio using a no-code or low-code interface.\n\n
\n\nForms\n\n\n\nRecord views that define which fields are displayed and how they are arranged.\n\n
\n\nInbound email actions\n\n\n\nRules that process incoming email and create or update records based on message content.\n\n
\n\nJavaScript modules\n\n\n\nBuild Agent creates JavaScript modules for organizing reusable server-side code within an application. Modules support standard import and export patterns and can reference server-side APIs. Use this pattern when multiple business rules, script includes, or other server-side scripts must share utility functions, constants, or logic without duplicating code.\n\n
\n\nKnowledge base access\n\n\n\nConfigurations that control which users and groups can read, contribute to, or manage knowledge bases and knowledge articles.\n\n
\n\nLDAP server configurations\n\n\n\nBuild Agent creates LDAP server configurations and LDAP server URLs for connecting to external directory services such as Active Directory and OpenLDAP. LDAP server configurations include failover and load-balancing URL configurations and SSL settings. For importing records from the directory into ServiceNow tables, use a data import pipeline instead.\n\n
\n\nList controls\n\n\n\nSettings that control list view behavior, including column display and row counts.\n\n
\n\nPlaybooks\n\n\n\nRepresentations of cross-enterprise business processes that organize tasks and activities into logical stages to guide users through a record lifecycle. Playbooks combine triggers that specify when to start, stages that group sequences of activities, and activities that define the automation and user-facing experience. Build Agent can create playbook configurations and activity definitions to help organizations digitize and standardize their business processes.To generate a playbook in Build Agent attach a file, such as an image, an XML, or a text description.\n\nFor more information on playbooks, see [Workflow Studio Playbooks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/workflow-studio-playbooks-landing.md).\n\n
\n\nRecord insertion\n\n\n\nBuild Agent inserts data into any table, including tables that don't have a dedicated build skill. The functionality covers seed data, demo data, reference data, and configuration records. The same approach applies to creating metadata records on platform tables that Build Agent does not have a specialized skill for yet.\n\n
\n\nREST message and HTTP method\n\n\n\nREST message definitions and HTTP method configurations for building API integrations and outbound integrations.\n\n
\n\nScheduled jobs\n\n\n\nAutomated tasks that run on a defined schedule.\n\n
\n\nScript includes\n\n\n\nReusable server-side JavaScript libraries callable from other scripts.\n\n
\n\nScripted REST APIs\n\n\n\nCustom REST endpoints built with server-side scripting.\n\n
\n\nSecurity\n\n\n\nAccess control lists \\(ACLs\\), roles, and related security configurations.\n\n
\n\nServer-side logic\n\n\n\nScripts and business rules that execute on the server.\n\n
\n\nService Catalog items and configurations\n\n\n\nCatalog items, variables, and fulfillment flows for the Service Catalog. Includes `dependentQuestion` support for variables, enabling dynamic default values that auto-populate based on a referenced variable's record. For example, when a user changes the **Requested for** field, related fields such as **Department** and **Location** can be populated automatically.\n\n
\n\nService Portal configuration, pages, and widgets\n\n\n\nPortal structure, page definitions, and custom widgets.\n\n
\n\nSkills\n\n\n\nServiceNow Otto skills for AI-powered responses and actions.\n\n
\n\nTables\n\n\n\nDatabase tables that store application data, including fields, relationships, and access controls.\n\n
\n\nTransition conditions\n\n\n\nConditions that determine when a record can move from one state to another in a workflow or flow, enforcing stage-gate logic and data requirements.\n\n
\n\nUI actions\n\n\n\nButtons, context menu items, and links that trigger scripts or navigation on forms and lists.\n\n
\n\nUI components\n\n\n\nReusable interface elements built with UI Builder.\n\n
\n\nUI pages\n\n\n\nCustom pages built outside of standard form and list views.\n\n
\n\nUI styles\n\n\n\nStyle definitions stored in the `sys_ui_style` table that control the visual appearance of forms and fields.\n\n
\n\nUI policies\n\n\n\nClient-side rules that show, hide, require, or lock fields based on conditions.\n\n
\n\nUI views\n\n\n\nNamed configurations of form layouts for different user contexts.\n\n
\n\nUser criteria\n\n\n\nRules and criteria definitions for filtering and selecting users based on field conditions and organizational structures.\n\n
\n\nWorkflows\n\n\n\nAutomated process sequences built in the legacy workflow editor.\n\n
\n\nWorkspaces\n\n\n\nAgent-facing interfaces built with configurable workspace components.\n\n
**Parent Topic:**[Build Agent reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/build-agent-reference-landing.md)\n\n"}}