--- sourceDocument: Australia API Reference sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/api-reference Release : - australia ft:locale : - en-US ft:publication_title : - Australia API Reference ft:clusterId : - crapiref bundleId : - crapiref workflow : - Creator --- # ServiceNow Fluent # ServiceNow Fluent {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of ServiceNow Fluent ServiceNow Fluent is a declarative, domain-specific language (DSL) based on TypeScript designed for defining application metadata files (sysmetadata) in ServiceNow. It enables developers to define metadata such as tables, roles, ACLs, business rules, and Automated Test Framework tests directly in source code rather than using UI forms or builder tools. Fluent supports two-way synchronization, allowing metadata changes to sync between ServiceNow AI Platform interfaces and source code, facilitating consistent and efficient application development. Show full answer Show less This language is supported in applications created or converted with the ServiceNow IDE or SDK, making it practical for developers to use modern tools and workflows for metadata management. ## Key Features * **Declarative Metadata Definition:** Use TypeScript-based Fluent APIs to define complex metadata objects with concise code, improving clarity and maintainability. * **Two-Way Synchronization:** Changes in metadata are synchronized between the instance and source code, ensuring alignment and reducing manual updates. * **Broad API Coverage:** Fluent includes APIs for many metadata types. The Record API covers types without dedicated Fluent APIs. * **Integration with JavaScript Modules:** Server-side scripts like BusinessRules can import and use functions from JavaScript modules for modular and reusable code. * **Selective Sync Control:** Use code directives (@fluent-ignore, @fluent-disable-sync, and @fluent-disable-sync-for-file) to manage synchronization behavior and suppress warnings where necessary. ## Practical Usage Developers write metadata definitions in files with the `.now.ts` extension, importing Fluent APIs from `@servicenow/sdk/core`. For example, you can define a table with columns, create client scripts that execute on record load, and define business rules that react to record updates---all via source code: * Define tables with columns and choice lists * Attach client scripts referencing external script files * Create business rules that invoke JavaScript module functions for server-side logic After building the application, the Fluent source code generates the corresponding application metadata files on the ServiceNow instance, ready for deployment and runtime use. ## Limitations Certain metadata types, such as Metadata Snapshots (`sysmetadatalink`) and UX Assets (`sysuxlibasset`), cannot be represented in Fluent code and remain as XML files within the application. ## Next Steps for ServiceNow Customers * Use the ServiceNow IDE or SDK to start defining application metadata using Fluent. * Refer to the ServiceNow Fluent API reference and the SDK GitHub examples to explore supported metadata types and coding patterns. * Leverage Fluent's synchronization features to maintain consistency between metadata source code and instance configurations. * Incorporate directives to control sync behavior where needed for specialized development scenarios. Define application metadata in source code using the ServiceNow Fluent domain-specific programming language. ## Overview of ServiceNow Fluent {#servicenow-fluent__section_jnb_vvg_z1c} ServiceNow Fluent is a declarative, domain-specific language (DSL) based on TypeScript for defining the metadata files \[sys_metadata\] that make up applications and includes APIs for the different types of metadata, such as tables, roles, ACLs, business rules, and Automated Test Framework tests. Developers define this metadata in a few lines of code instead of through a form or builder tool user interface. Applications created or converted with the ServiceNow IDE or ServiceNow SDK support development in ServiceNow Fluent. ServiceNow Fluent supports two-way synchronization, which allows changes to metadata to be synced from other ServiceNow AI Platform user interfaces into source code and changes to source code to be synced back to metadata across the instance. To get started using the ServiceNow IDE or ServiceNow SDK, see the [ServiceNow IDE](https://www.servicenow.com/docs/access?context=servicenow-ide-landing&version=australia&pubname=australia-application-development&ft:locale=en-US) or [ServiceNow SDK](https://www.servicenow.com/docs/access?context=servicenow-sdk-landing&version=australia&pubname=australia-application-development&ft:locale=en-US) documentation. ## ServiceNow Fluent APIs {#servicenow-fluent__section_nyj_y13_zbc} ServiceNow Fluent includes APIs for many types of metadata. You can use the Record API to define application metadata that doesn't have a dedicated API. For the latest list of supported APIs and examples, see the [ServiceNow Fluent API reference](https://servicenow.github.io/sdk/) and [ServiceNow SDK examples repository](https://github.com/ServiceNow/sdk-examples) on GitHub. Note: A limited number of metadata types, such as Metadata Snapshots \[sys_metadata_link\] and UX Assets \[sys_ux_lib_asset\], can't be represented as ServiceNow Fluent code and aren't transformed. These metadata types remain as metadata XML files in the metadata directory of your application. ## ServiceNow Fluent usage {#servicenow-fluent__section_dgj_1b3_zbc} In files with the .now.ts extension, use objects in the ServiceNow Fluent APIs to define metadata in the application. You must also include the required imports for the APIs from @servicenow/sdk/core. For objects with server-side scripts, such as the BusinessRule object, you can import and use code from JavaScript modules. The following example includes the definitions of a table, client script, and business rule in the application. The client script uses a script from the client-script.js file. The business rule uses a function from the script.js JavaScript module. import '@servicenow/sdk/global' import { BusinessRule, ClientScript, DateColumn, StringColumn, Table } from '@servicenow/sdk/core' import { showStateUpdate } from '../server/script.js' //creates todo table, with three columns (deadline, status and task) export const x_snc_example_to_do = Table({ name: 'x_snc_example_to_do', schema: { deadline: DateColumn({ label: 'Deadline' }), state: StringColumn({ label: 'State', choices: { ready: { label: 'Ready' }, completed: { label: 'Completed' }, inProgress: { label: 'In Progress' }, }, }), task: StringColumn({ label: 'Task', maxLength: 120 }), }, }) //creates a client script that pops up 'Table loaded successfully!!' message everytime todo record is loaded ClientScript({ $id: Now.ID['cs0'], name: 'my_client_script', table: 'x_snc_example_to_do', active: true, appliesExtended: false, global: true, uiType: 'all', description: 'Custom client script generated by Now SDK', isolateScript: false, type: 'onLoad', script: Now.include('../client/client-script.js'), }) //creates a business rule that pops up state change message whenever a todo record is updated BusinessRule({ $id: Now.ID['br0'], action: ['update'], table: 'x_snc_example_to_do', script: showStateUpdate, name: 'LogStateChange', order: 100, when: 'after', active: true, }) The client script referenced from the ClientScript object: function onLoad() { g_form.addInfoMessage("Table loaded successfully!!") } The JavaScript module referenced from the BusinessRule object: import { gs } from '@servicenow/glide' export function showStateUpdate(current, previous) { const currentState = current.getValue('state') const previousState = previous.getValue('state') gs.addInfoMessage(`state updated from "${previousState}" to "${currentState}"`) } After building the application, this source code generates the following application metadata files on the instance. Figure 1. Application metadata generated from ServiceNow Fluent code Tip: You can use the following directives in a code comment to help manage your code: * `@fluent-ignore`: Suppresses ServiceNow Fluent diagnostic warnings and errors in the following line of code. * `@fluent-disable-sync`: Turns off syncing changes to a ServiceNow Fluent object. Use before a call expression (for example, `Record({ ... })`) to turn off syncing for that object and its child objects. Only use this directive if you want to ignore changes made outside of the source code to the object and never update it when syncing. * `@fluent-disable-sync-for-file`: Turns off syncing changes to a ServiceNow Fluent file (.now.ts). Use in the first line of the file to turn off syncing for all code in the file. Only use this directive if you want to ignore changes made outside of the source code to the file and never update it when syncing. {#servicenow-fluent__ul_dzm_xxw_ldc} **Related topics** * [ServiceNow Fluent API reference](https://www.servicenow.com/docs/access?context=servicenow-fluent-api-reference&version=australia&pubname=australia-application-development&ft:locale=en-US) * [Define application metadata in code with ServiceNow Fluent in the ServiceNow IDE](https://www.servicenow.com/docs/access?context=define-metadata-code-fluent-ide&version=australia&pubname=australia-application-development&ft:locale=en-US) * [Define application metadata in code with ServiceNow Fluent and the ServiceNow SDK](https://www.servicenow.com/docs/access?context=define-metadata-code-fluent-sdk&version=australia&pubname=australia-application-development&ft:locale=en-US)