Building applications -- Learn how to become an application developer using ServiceNow AI Platform low-code tools. Start with what you know and use a library of reusable components and published applications to modernize your legacy processes.
Getting Started guide for developers -- The ServiceNow AI Platform is a unified development environment for building intelligent, enterprise-grade applications. Use it to automate workflows, connect data across systems, and deliver experiences to your users — without managing underlying infrastructure.
AI-native app development -- Learn about the suite of AI tools available on the ServiceNow AI Platform and how you can use them to build applications more efficiently.
Contextual assistance -- Now Assist for Creator contains AI assets that provide contextual assistance for handling development tasks more efficiently.
Agentic development -- Agentic development is an AI-driven approach to app development in which you build applications through conversations with AI. On the ServiceNow AI Platform, developers can use Build Agent to build entire applications through agentic development.
General guidelines for agentic development -- When using agentic development tools to build applications and app components on the ServiceNow AI Platform, the quality of the output depends on the quality of your instructions. Use these guidelines to write effective instructions and improve the products of your conversations with AI tools.
Choosing your build approach -- Understand when to use AI-assisted tools like the app generation skill with Now Assist for Creator and Build Agent versus when to build an application manually on the ServiceNow AI Platform.
Adding AI to your apps -- Learn about how you can add AI assets, such as skills, AI agents, and agentic workflows, to your custom apps using Now Assist for App Engine.
AI assets -- Learn about the AI assets that you can create on the ServiceNow AI Platform.
Platform and App Engine tools -- To create AI assets and integrate them into your custom applications, you can use a combination of Platform tools and Now Assist for App Engine.
Maintaining AI assets -- There are important maintenance considerations for applications that include AI assets, which go beyond the maintenance practices for traditional custom applications. Learn about how to maintain applications that contain AI assets on the ServiceNow AI Platform.
Standard app development -- The ServiceNow AI Platform enables you to create global and custom applications. You can work in classic lists and forms, or you can build apps using App Engine products such as ServiceNow Studio.
Configure, customize, or build apps -- Configuration and customization are hallmarks of the ServiceNow AI Platform that enable your company to customize workflows to fit its specific needs. You can also build new apps for novel use cases or departmental processes that don't fit within the scope of your current applications.
Plan your app before you start building -- Planning your application before development ensures scalability, governance, and alignment with organizational goals. Effective planning reduces duplication, helps prevent technical debt, and ensures compliance with ServiceNow best practices. It also helps define clear objectives, timelines, and resource requirements.
Design an app -- Horizon is a modern UX framework that enables developers to create responsive, accessible, and consistent user experiences across applications. Horizon provides a unified design system that improves usability and performance. It supports accessibility standards and ensures a consistent look and feel across the ServiceNow AI Platform.
Check timelines and SDLC guidelines -- Engage your platform administrator early to confirm development timelines and follow ServiceNow software development lifecycle (SDLC) best practices. Coordinating with your admin ensures that your app development aligns with organizational governance, avoids delays, and uses approved environments and tools.
Plan data for reuse -- Design your data model to support scalability, interoperability, and future reuse across applications on the ServiceNow AI Platform.
Planning for analytics and reporting -- Include analytics requirements during the design phase to enable meaningful reporting and insights from the start. Analytics cannot be an afterthought when building on the ServiceNow AI Platform. Defining KPIs and reporting needs during app design ensures that data is captured correctly and supports dashboards, performance metrics, and decision-making.
ServiceNow files in applications -- ServiceNow files are digital documents and assets stored within the ServiceNow AI Platform that serve various purposes across applications and workflows.
ServiceNow metadata in applications -- ServiceNow metadata refers to the configuration and structural definitions that make up a ServiceNow application itself.
Build your first app -- Build, configure, and deploy custom apps from a single development environment, ServiceNow Studio. ServiceNow Studio gives admins and developers integrated tools to create app files, edit scoped and global app metadata, and package changes for deployment.
Parts of an application -- Applications in ServiceNow have tables, UI elements, application files, integrations, and dependencies, all with a layer of security through the entire app.
Tables and data models -- Tables are the foundation of ServiceNow applications, as they define what data you're storing and how it's structured. Each table consists of fields (columns) that hold specific data types such as strings, dates, numbers, and references to other tables.
Building a data model -- Plan your data model carefully before building an application on the ServiceNow AI Platform. It defines what information you're managing, how it connects, and ultimately determines what your application can do.
Automation basics for apps -- Automation is central to ServiceNow application development and is a core strength of the ServiceNow AI Platform. Automation enables developers to build applications that reduce manual work, enforce consistency, and respond intelligently to business events.
Dependencies for custom applications -- Every custom application record includes a related list identifying its dependencies on other applications. Dependencies are references from your custom application to functionality provided by other applications or plugins installed on the instance.
Forms and list layouts -- Forms and list layouts control how an app's data appears to users. A form displays a single record so users can view or edit it. A list displays multiple records so users can browse, filter, and find the data they need.
Adding business logic to apps -- Business logic lets your app respond automatically to data changes, enforce rules, and perform calculations without requiring user intervention.
Building workflows and automations -- Workflows and automation let your app take action automatically in response to events, record changes, or schedules. Rather than relying on users to manually move work forward, you define the logic once and let the platform execute it consistently.
Advanced scripting -- As an app grows in complexity, it may reach the limits of what business rules, script includes, and Flow Designer actions can accomplish through configuration alone. Advanced scripting means writing directly against ServiceNow's server-side JavaScript APIs to handle logic that requires more precision or flexibility than low-code tools provide.
User interface and experiences -- Learn about user interfaces and tools for building them as you create applications on the ServiceNow AI Platform.
What is an experience? -- Discover what a user interface experience is on the ServiceNow AI Platform.
Service Portal vs Workspace -- Understand the similarities and differences between a Service Portal and a Workspace on the ServiceNow AI Platform.
Learn about personas -- Learn about personas and how to analyze personas before creating an application on the ServiceNow AI Platform.
Tools for building UIs -- Learn about the tools available on the ServiceNow AI Platform for building user interfaces in applications.
Integrations -- Integrations enable you to connect your custom app to external systems to send and receive data. The ServiceNow AI Platform supports multiple integration capabilities to fit your use case.
Inbound web services -- Inbound web services enable external systems to read data from or write data to your custom application. External systems can query your data, create records, or exchange information.
Outbound web services -- Outbound web services send data from your custom app to external systems. With outbound web services, your app can notify, request, or update external platforms in real time or on a schedule.
Integration Hub -- Integration Hub is a prebuilt low-code platform for adding integrations to prebuilt connectors. Use Integration Hub to connect your custom app to third-party applications without having to write custom code.
Deployment -- Deploying custom applications from development to non-production and production instances is one of the most critical processes in ServiceNow platform management. Knowing the ServiceNow application deployment life cycle, including migration methods, security considerations, and organizational best practices ensures stability, security, and traceability.
Moving applications between instances -- ServiceNow applications are built in Development instances, then promoted through Test and Production environments using update sets or the Application Repository to package and migrate changes. This multi-instance workflow ensures applications are thoroughly tested before reaching end users in Production.
Managing application versions -- Semantic versioning (Major.Minor.Patch) is the standard approach for ServiceNow applications. Each time you publish from ServiceNow Studio, you assign a version number, which gives your team a clear audit trail of all changes.
Deployment management options -- ServiceNow offers multiple management options for orchestrating deployments. Your choice depends on your organization’s maturity, licensing, and operational preferences. You can choose between ReleaseOps, App Engine Management Center Pipelines and Deployments, or System Update Sets.
Standard operating procedure for deployment -- Every ServiceNow organization should have a documented deployment standard operating procedure. The procedure should specify the approved method for orchestrating deployments, the pipeline stages and approval gates, and the roles authorized to perform deployments.
Guidelines for using source control -- Source control (Git) combined with the Application Repository is the preferred deployment method for custom scoped applications. Using System Update Sets is also an approved deployment mechanism for application development.
Version control -- Version control is how you track, manage, and protect every change made to your application across its entire development lifecycle on the ServiceNow AI Platform.
Updating your app for a ServiceNow platform version -- When ServiceNow releases a new platform version, your app may need updates to keep working correctly. Learn how platform upgrades affect your app helps you plan and complete the upgrade with confidence.
Finding ServiceNow developer products -- Use the following widget to find ServiceNow developer products that help you create applications that run on the powerful ServiceNow AI Platform.
Reporting on data from pro-code apps -- Most applications that you create have some level of reporting requirements. Reports should be actionable to drive change.
Reporting on data from low-code apps -- Most applications that you create have some level of reporting requirements. Reports should be actionable to drive change.
Programming basics -- Software development usually encompasses a standard set of steps. If you're new to developing applications, read on.
Anatomy of an application -- Applications consist of several types of files and records that collectively deliver a service.
Custom application record -- The custom application record defines and identifies an application and all its associated artifacts.
Application versions -- Each installed application has a version as defined by its application developer in the custom application record.
Application scope -- Application scoping protects applications by identifying and restricting access to application files and data.
Global scope -- The global scope is a special application scope that identifies applications developed prior to application scoping, or applications intended to be accessible to all other global applications.
Namespace identifier -- The system adds a namespace identifier to the front of application artifacts such as tables, scripts, and configuration records.
Namespace identifier examples -- The following examples illustrate generating namespace identifiers for applications, tables, and fields.
Application tables -- Application developers create tables and their associated lists and forms for users to add and update records.
Application files -- Application files are configuration records that allow developers to extend application functionality.
View file properties -- Administrators can view the application file properties of a single record.
Application File form -- Use the Application File form to view relationships between applications and configuration records.
Application file protection policy -- A read-only protection policy prevents anyone from modifying an application file or its related record.
Fix scripts -- A fix script is server-side JavaScript code that you run after an application is installed or upgraded.
Create a fix script -- Create fix scripts to ensure the system installs or updates an application properly.
Test a fix script -- Test your fix scripts to ensure they install or update applications as expected.
Run fix scripts -- Fix scripts run at the first installation or updated after they have been added to an application. However, previous fix scripts do not run on subsequent application updates, and you must manually run any necessary fix scripts.
Fulfillment tables -- To enable a production instance to enforce entitled usage of your ServiceNow Store App, you configure the tables where only record owners or subscribed app users can make updates.
Specify that a table is a fulfillment table -- You configure a table as a fulfillment table to enable the system to prevent updates by users who are not subscribed to the app. For ServiceNow Store apps, you configure a table as a fulfillment table to enforce that fulfillment usage complies with your subscription use policy.
Personal developer instance guide -- ServiceNow offers free personal developer instances (PDIs) to Developer Program members to learn, explore, and experiment with the ServiceNow AI Platform.
Understanding PDIs -- PDIs require you to select a specific release and maintain consistent usage to avoid hibernation.
Releasing your PDI -- Release your PDI to unassign the instance from you, reset to its original state, and reassign it to another Developer Program member.
Changing your instance user role -- Change your PDI user role to either App Engine Studio Creator or Admin for different views and levels of access.
Early Availability guide -- Early Availability provides you with exclusive access to the latest release over a month before market launch makes the release available for any customer to use.
Modifying versus building an application -- At a certain point in the lifetime of your applications, it might make sense to create an application to replace the old one. Cost savings, maintenance effort, and features available in new apps can help you determine if it's better to build a new application or modify an existing one.
Understand the ServiceNow UI experiences -- You can develop in the following ServiceNow AI Platform user interfaces: the Next Experience UI, the Workspace UI, the Classic Environment, and the Core UI. This topic explains these user interfaces.
Add permissions to collaboration descriptors -- Add permissions to collaboration descriptors to manage your user's capabilities, such as the ability to delete the application or manage collaborators.
Assign collaboration descriptors to users -- Assign collaboration descriptors to your users for a specific application so that you can define specific permissions for these users.
Assign collaboration descriptors to groups -- Assign collaboration descriptors to user groups for a specific application so that you can define specific permissions for these user groups.
Contextual development environment -- The platform is a contextual development environment that displays the currently selected application, identifies the scope of every application artifact, and prevents any changes that violate the access settings for an application.
Application context -- When application developers create new records, the system automatically assigns the records to the currently selected application in the application picker.
Application access settings -- Application access settings determine whether one application can access resources from another application.
Runtime access tracking -- Runtime access tracking allows administrators to manage script access to application resources by creating a list of script operations and targets that the system authorizes to run.
Cross-scope privilege record -- Runtime access tracking uses cross-scope privilege records to determine which script operations and targets the system allows to run.
Application design access record -- Administrators use application design access records to specify which other applications are available to developers during application creation.
Table design and runtime settings -- The Application access fields determine whether a table is accessible to other applications during design-time or run-time operations.
Design-time access to application tables -- As the application developer, you can grant or deny other applications the permission to create configuration records, also known as application files, that extend the functionality of an application.
Default design access permissions -- By default, new application tables prevent other application scopes from creating configuration records on application data tables. This prevents any other applications from changing the functionality of a table.
Restricted caller access privilege settings -- Define cross-scope access to an application, application resource (such as an access control role, a business rule, a UI action, or a script include), or event. You can even use these settings to allow or deny requests for access.
Activate application restricted caller access -- You can activate the Scoped Application Restricted Caller Access plugin (com.glide.scope.access.restricted_caller) if you have the admin role.
Set the application scope, application resource, and event access -- Create a record in the Restricted Caller Access Privileges [sys_restricted_caller_access] table to set cross-scope resource access requests. Approve or deny requests from a source scope or source scope application resources to a target scope or to target scope application resources.
Scope-to-scope settings -- Allow or deny access of all application resources in a source scope to all application resources in a target scope. This setting combination is a many-to-many relationship.
Scope-to-target settings -- Allow or deny access of all application resources in a source scope to a specific application resource (business rule, table, script include, or event) in a target scope.
Source-to-scope settings -- Allow or deny access of a specific application resource in a source scope to all application resources in a target scope.
Source-to-target settings -- Allow or deny access of a specific application resource in a source scope to a specific application resource in a target scope.
Requested restricted caller access (RCA) -- You can use a requested RCA to grant store apps access to protected resources in the ServiceNow AI Platform without the need to wait for the next family release. If you have the system admin or application admin role, you can review requested RCAs and approve and deny them.
Application list -- The applications list allows application developers to view and select applications.
Application picker -- The application picker enables application developers to view and select the application scope where their changes apply.
Lists and forms in scoped applications -- The current application context determines what customization and form design options are available when working with lists and forms in scoped applications.
Available layout and design actions -- The system allows the following layout and design actions when working on lists or forms in custom applications.
Form design visual indicators -- The UI displays the following visual indicators when designing forms in custom applications.
Layout visual indicators -- The UI displays the following visual indicators when configuring the layout of a custom application's list or form.
Contextual development edit messages -- The platform displays a message if you attempt to edit a Store Application record when you're in a different application scope.
Script protection policy -- Application developers can set a protection policy for script includes published as part of a custom application. The policy determines whether someone can view or edit the script include after the application is installed on their instance.
Application administration -- Protect sensitive application data by using application administration to restrict how users acquire application-specific roles.
Restrict access to an application -- Restrict management of an application and access to that application to prevent unauthorized users from assigning administrative rights to the application or accessing sensitive information in the application records.
Access control rules in application administration apps -- By default, when application administration is enabled for a scoped application, ACL rules for the scoped application are applied. If no ACL rules for the scoped application are found, global ACL rules can apply.
Access enforcement for ServiceNow Store apps -- All production instances monitor and generate reports on usage patterns for ServiceNow Store apps. When subscription enforcement is enabled, users who are not subscribed to the app are blocked from performing fulfiller actions in the app.
Licensing -- Understand the different types of software licenses and subscriptions available with ServiceNow applications.
Creation restrictions across application scopes -- The system restricts the creation of some configuration records when the current application scope does not match the application scope of the configuration record's target table.
Governing app development -- To deliver the most value with your custom applications, you must have the right governance in place. The ServiceNow App Engine Management Center and related features empower you to govern app development easily and efficiently in one centralized location.
App Engine Management Center -- The App Engine Management Center (AEMC) provides an innovative experience for you to manage the full life cycle for custom app development. You can use AEMC to handle application intake, configure pipelines, oversee developer productivity, and view insights about custom applications across your development environments, all in one centralized location.
Explore -- Learn about how the App Engine Management Center (AEMC) can help to centralize and streamline your application development and governance at scale.
User interface -- Learn about the App Engine Management Center user interface.
Pipelines and Deployments workflow -- As you manage requests for app deployment in App Engine Management Center (AEMC), use this workflow to understand how app deployments move through your pipelines in versions 24.1.2 and later.
Deployment requests -- AEMC enables you to deploy changes to production through deployment requests. Learn more about what deployment requests are and where to view them in AEMC. Starting with version 28.2.1 of AEMC, you can also manage ReleaseOps deployment requests from AEMC.
Testing applications in AEMC -- Testing an application helps to ensure the viability of the changes on the production instance. Learn about how testing works in AEMC and the different kinds of tests that automatically run during the deployment process.
App Readiness and Compliance Report -- App Engine Admins can use the App Readiness and Compliance Report dashboard to check if the apps they’re creating are ready to go live.
Migrating App Engine pipelines to ReleaseOps -- Starting with version 28.2.1 of AEMC, you can migrate your existing App Engine pipelines to ReleaseOps. Learn more about the migration process and benefits of migrating to ReleaseOps.
Get help with AEMC -- To get help with App Engine Management Center, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company.
Configure -- Learn about the configuration process for AEMC.
Configure AEMC -- Complete AEMC guided setup to initially configure Application Intake and your preferred deployment option (Pipelines and Deployments, ReleaseOps, or a standalone environment). The Application Intake guided setup is optional, but setup of one of the deployment options is required.
Test AEMC functionality -- Test App Engine Management Center (AEMC) on a non-production instance to confirm that everything is working as expected before moving to production.
Configure Application Intake -- Use the App Engine Studio (AES) Application Intake guided setup to step through the initial configuration of the Application Intake application. Detailed instructions for each step are provided in subsequent sections of the product documentation.
Configuration tasks -- As you work through the App Engine Studio (AES) Application Intake guided setup, you must perform different configuration tasks.
Activate the Apply for Citizen Development catalog item -- Enable citizen developers to submit their ideas for applications by activating the Apply for Citizen Development catalog item. This is the first step in configuring the App Engine Studio (AES) Application Intake app.
Customize the App Intake form -- Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder.
Change the question order -- Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder.
Define dynamic behavior for a question -- Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder.
Deactivate a question -- Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder.
Manage user groups -- Control which user groups are available for admins to give Creator Studio and App Engine Studio app development permissions to during the Application Intake process. These groups are managed on the User Groups Permission Types [sn_app_intake_permission_type] table.
Configure ReleaseOps -- Complete ReleaseOps guided setup in AEMC to start using ReleaseOps for your deployments.
Enable ReleaseOps system property -- Enable the ReleaseOps system property to have AEMC fetch data from the environments configured in ReleaseOps.
Run trust profile setup -- After completing ReleaseOps guided setup in AEMC, run trust profile setup to complete the configuration process.
Configure Pipelines and Deployments -- Use the Pipelines and Deployments guided setup to complete the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation.
Configuration tasks -- As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances.
Configure environment credentials -- Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances.
Configure OAuth credentials -- Use OAuth credentials in your pipelines to add another level of security to your pipeline. This task helps you create and configure OAuth credentials for use in your pipelines.
Create API endpoints for external clients -- Create OAuth API endpoints to enable your controller instance to have two-way communication with your non-production instances. Follow and complete each step carefully on the specified instances before moving on to create your third-party OAuth provider records.
Create third-party provider records -- Create third-party OAuth provider records to enable each of your instances to access the API endpoints you've created.
Create pipeline credentials -- Create credential records on each of your instances to enable OAuth use in your pipeline.
Configure pipeline environments -- Set up your app development production and non-production environments (for example, development, test, and/or staging) by adding the URLs and credentials used to access each instance.
Configure your pipeline -- Configure your app development pipeline so that your administrator can quickly move an application from one environment to another.
Configure your controller instance -- You must identify one of the instances in your app development pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance.
Add ATF and instance scan suites -- Add your customized test suites as part of an application deployment in addition to the instance scan and Automated Test Framework (ATF) testing suites that are standard in AEMC.
Enable ATF properties -- Pipelines and Deployments includes an Application Test Framework (ATF) suite called the Application Deployment Test Suite. Two system properties control whether the test runs automatically whenever an app is deployed to a Test environment.
Enable Change Management integration -- Enable Change Management integration with AEMC so that deployments through the pipeline to the production environment are automatically scheduled based on the Change request state and planned change window.
Configure Change Management integration -- Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional.
Configure the change model -- Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional.
Configure the change template -- Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional.
Configure CI creation subflow -- Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional.
Migration tasks -- You must complete several tasks to migrate your App Engine pipelines to ReleaseOps.
Map deployment request states -- If your ReleaseOps deployment request has custom states, you must configure the Deployment Request State Map table so that your ReleaseOps deployment request states map to the correct App Engine states.
Configure a standalone environment -- With App Engine Management Center (AEMC), you no longer need an active deployment pipeline to get started. Complete the standalone environment setup to start deploying changes quickly. You can add a pipeline later when you're ready to automate deployments.
Use -- AEMC enables you to manage app development and deployments, all in one centralized location. Learn about how you can use AEMC to govern your organization's app development.
Manage app development -- Track and manage requests, deployments, applications, and collaborative developers for your custom applications using the App Engine Management Center (AEMC) in your production instance.
Manage requests -- You can track and approve or reject Intake, App, Collaboration, and Deployment requests using the App Engine Management Center (AEMC).
Manage intake requests -- View details of intake requests submitted by developers in App Engine Studio in the App Engine Management Center (AEMC) dashboard, and approve or reject them.
Manage app requests from Creator Studio -- View and manage new app requests in App Engine Management Center (AEMC) that users with the Creator Studio Restricted role (sn_creator_studio_restricted_user) submit for apps they want to create.
Manage collaboration requests -- As an admin, view and approve or reject collaboration requests in the App Engine Management Center (AEMC) from developers who want assistance building their applications.
Manage deployment requests -- Review and approve or reject deployment requests in the App Engine Management Center (AEMC) as applications move from development to production.
Filter and search for requests -- The App Engine Management Center (AEMC) application provides tools for locating requests. You can perform a global search for request records or filter the list of current requests to locate the ones you want to work on.
Manage custom apps -- Review custom app metrics and manage apps through the development life cycle using the App Engine Management Center (AEMC).
Manage developers -- View details about developers working on apps in App Engine Studio and Creator Studio using App Engine Management Center (AEMC).
Manage deployments -- Manage deployments using Pipelines and Deployments in the App Engine Management Center (AEMC).
Schedule app deployments -- Schedule apps to deploy to production at a future time to load balance your systems using the App Engine Management Center (AEMC).
Update a deployment request -- Change the details of a deployment request in App Engine Management Center (AEMC).
Cancel a scheduled deployment -- Cancel a scheduled app deployment in App Engine Management Center (AEMC) if you no longer need to deploy the app to production. Canceling the scheduled deployment request cancels the scheduled deployment and also the entire request itself.
Planning your application -- The application development process starts with planning. Consider how the application will work, who will use it, and how it improves user experience.
Submit your idea for app development -- With your carefully-planned idea in hand, you are ready to submit it through Application Intake for approval and development in App Engine Studio (AES).
Specify data for your application -- In its most basic form, building applications on the ServiceNow AI Platform means you're storing and using data in some way. Defining your application's data model is up to you and is based on the type of application you want to build.
Delegated Development -- Delegated development allows designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform.
Explore -- Delegated Development allows designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform.
Deployment -- Delegated development allows designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform.
Domain separation -- Domain separation is unsupported in the Delegated Development feature. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Configure -- Configure Delegated Development to assign, delete, display or hide permissions.
Assign source control permissions -- Ability to assign full access to source control for a particular scope to a delegated developer. The Source Control menu is only visible if you have the correct permissions for the application that you are working in.
Assign delete permissions -- Ability to assign the ability to delete an application to a delegated developer.
Deployment permissions -- Display or hide deployment permissions for update sets from the Manage Developers dialog.
User roles -- Assign roles that enable non-admin users install or upgrade all applications in specific instances. You delegate these tasks by manually assigning specific user roles per instance.
Add user roles -- A system administrator can assign user roles to specific personnel that allow them to perform first application installations only, or install and upgrade applications in a local instance.
System user roles -- Although system admins can still manually assign and remove the user roles, they are encouraged to let the system manage the following delegated developer roles.
Administer -- Perform administrative duties in Delegated Development.
Delegate permissions -- A system administrator can assign a non-administrator user or group as a developer or deployment resource for a specific application. You can set permissions that designate what specific actions the assigned user can perform in the current instance, or make the user a Delegated Admin to grant access to all permissions at once.
Developer and deployment permissions -- Using Manage Developers, administrators can assign one or more developer and deployment permissions to a group or user for a specific application. These permissions designate the specific actions the assigned user can perform for the application.
Remove a developer -- Removing a user as a developer prevents the user from developing, changing, or deploying the application in the current instance.
Team Development -- Team Development supports parallel development on multiple, non-production ServiceNow instances.
Explore -- Team Development supports parallel development on multiple, non-production ServiceNow instances.
Local changes -- The Local Changes table tracks which customized records have current versions that exist on the development instance but not on the parent instance.
Local change lists -- On the team dashboard, the Local Changes list shows the local changes that have not been queued for the next push or ignored for all pushes.
Pull exceptions -- Pulling ignores versions when certain conditions occur.
Team dashboard -- The team dashboard provides a central place to manage all Team Development activities on your development instance.
Approve or reject a push -- Code reviewers must approve or reject a push from the Team Development application.
Back out a local change -- Back out all local changes and restore the last version reconciled with the parent instance.
Cancel a code review request -- Developers can cancel any push they submitted that is in the Awaiting Code Review stage.
Change the parent instance -- If it becomes necessary to modify the instance hierarchy, you can change the parent for a development instance.
Check the review status of a pushed change -- If the parent instance requires pushed changes to undergo code review, changes are placed in the Awaiting Code Review stage.
Compare to peer instances -- You can compare the local instance to any other remote instance and commit any current versions from the remote instance on your development instance.
Ignore a local change -- Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list.
Pull a version -- Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.
Push a version -- Pushing promotes changes from the development instance to the parent instance and commits the current version of a customized record on the development instance as the current version on the parent instance.
Back out a push -- Application developers can back out a push to remove unwanted changes.
Queue a local change for a push -- Application developers can queue a local change for a push to ensure the changes are available to other developers.
Reconcile changes -- Reconciling first compares the local instance to the parent, and then generates the list of local changes and calculates the number of changes that are ready to pull from the parent.
Resolve a collision in Team Development -- A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.
Limitations on updating records -- There are some types of records that you cannot merge while resolving differences on the Compare to Current and Resolve Collision pages.
Resolve multiple collisions -- You can resolve multiple collisions without reviewing the differences between the local and pulled versions.
Configure -- Configure Team Development for your instance.
Access rights for developers -- To use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.
Create an exclusion policy -- Application developers can create an exclusion policy to prevent pushes or pulls to particular instances in the team development hierarchy.
Define a remote instance -- For each instance, define other instances in the hierarchy as remote instances.
Enable a code review -- You can require a code review of all changes pushed to an instance.
Select the parent instance -- An instance can have multiple peer instances but only one parent instance.
Administer -- Administer Team Development within your instance to compare instances, push or pull record versions, or view the team development dashboard.
Code reviews -- Team Development administrators can require that pushes undergo code review before accepting pushes.
Notifications -- You must enable email notifications on the instance requiring code review for that instance to send code review notifications.
Workflow -- The Team Development Code Review workflow manages how changes are pushed to the parent.
Exclusion policies -- You can exclude certain files from change tracking by creating an exclusion policy.
Instance hierarchies -- Team Development allows you to set up a distributed version control system between multiple ServiceNow instances where each instance acts as a source repository, or branch.
Pulls and pushes -- Developers synchronize their instances to the parent instance by pulling and pushing versions of customized records and resolving collisions between versions on the parent instance and the development instance.
Development process -- The basic Team Development process sets up the instance hierarchy, grants developer access rights, manages the movement of development changes from development instances to test instances, and promotes applications to the production instance.
Roles -- To use Team Development, developers must have admin access to their development instance.
Versions -- Version records track changes to a customized record over time so that administrators can compare or revert to specific versions later.
Version record navigation -- There are a variety of methods for viewing a list of versions for an object.
Versions transferring -- Administrators transfer version records between instances by moving customizations with Update Sets or the Team Development application.
Version records -- The Update Versions [sys_update_version] table contains records that represent the state of a customizable object at a particular time.
Merge tool -- The Diff Merge tool enables administrative users to compare differences between two versions of a record.
Compare to the current version -- You can compare a version to the current version for any customizable object that a user has modified, such as a form layout or business rule. You can also compare the local and current pulled version of an object in Team Development. Administrators can suppress versions for specific tables.
Revert a change -- You can undo changes to a customized record by reverting to an older version.
Suppress versions -- Administrators can configure a table so that it does not track customizations in the Versions [sys_update_version] table.
Versions and local changes -- Version records track changes to a customizable record over time so that you can compare or revert to a specific version later.
Agentic development on the ServiceNow AI Platform -- Build and enhance custom applications using the generative and agentic AI capabilities available on the ServiceNow AI Platform. The capabilities support every stage of development, from generating application components to vibe coding full-stack applications through natural language conversations.
Build Agent -- Use Build Agent, an autonomous AI agent, for creating and updating ServiceNow applications. You can also ask Build Agent general ServiceNow development questions.
Explore -- Build Agent enables developers to create, edit, and deploy full-stack ServiceNow applications to update sets that encompass both user interface and back-end components.
Use cases -- Use Build Agent for a wide range of development scenarios beyond application creation, including app analysis, modernization, documentation, governance, and learning assistance. Reference these scenarios to identify ways to apply Build Agent across your development workflow.
Workflow -- The Build Agent workflow automates building applications, testing, and deploying update sets on the ServiceNow AI Platform. Build Agent streamlines development by handling code compilation, quality checks, and deployment steps without manual intervention.
Tutorial for Build Agent in ServiceNow Studio -- Learn to develop reusable server-side logic and build a ServiceNow application in Build Agent, from data modeling through testing, using AI-assisted development.
General guidelines -- Use these guidelines to get the most out of Build Agent in your development workflow.
Build Agent tools -- Build Agent tools support application development tasks such as semantic search, schema inspection, code search, planning, UI validation, database querying, and app navigation. Each tool extends what Build Agent can do during a build session.
MCP connections and Build Agent -- MCP connections enable Build Agent to access external tools and resources through standardized communication. Use these connections to integrate third-party applications like Figma for accelerated design-to-development workflows.
Governance -- Governance controls in Build Agent help with code quality, security, and compliance when generating applications. The Build Agent automated safeguards prevent common development issues and enforce organizational standards.
Limitations -- Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance.
Configure -- Build Agent connects your instance to AI-powered design workflows. Set up the required application and MCP server connections to start using it.
Install Build Agent -- For the Premium version of Build Agent, install the Now Assist for Creator application from the ServiceNow Store.
Build Agent plugins -- The plugins for Build Agent depend on whether you're using the free/trial version or premium version.
Connect to supported MCP servers -- Connect a supported MCP server to Build Agent to access external tools and resources in the chat panel when building and editing apps.
Use -- Build Agent is an autonomous AI agent native to ServiceNow that translates plain language instructions into ready-to-deploy applications and metadata, using the platform’s domain language and guardrails. It's purpose-built for full-stack creation and editing across tables, flows, UI, and scripts, and it operates as the core engine for agentic development on the ServiceNow AI Platform.
Accessing Build Agent -- Build Agent is available in ServiceNow Studio (UI-first, declarative workflows) and the ServiceNow IDE (code-first, autonomous full-stack development).
Create an application -- Build custom ServiceNow applications by describing your requirements in plain language to Build Agent. The AI agent generates and builds the application code automatically.
Edit an existing application -- Modify existing ServiceNow applications using natural language prompts with Build Agent.
Adding or updating app files -- Use Build Agent to add new files or modify existing files in ServiceNow applications to assist with ongoing metadata and app development and maintenance.
Agentic workflows, agents, and skills -- Build Agent can generate agentic workflows, agents, and skills scoped to your custom app. Turn business requirements into configured AI artifacts without building from scratch.
Create workflows, agents, and skills -- Build custom agentic workflows, AI agents, and skills for your applications using automated generation tools with Build Agent. You can streamline development by creating the necessary instructions, tools, and access controls based on your requirements.
Revert app changes -- Restore your development to a previous state when you want to undo recent changes. Use checkpoints created during Build Agent conversations to revert both code and chat history.
Testing what you built -- Test Agent generates test coverage for code created by Build Agent, executes tests, and performs root cause analysis on failures. Prompt Test Agent to complete build-to-test workflows in a single development session without manual test authoring or failure investigation.
Document an application -- Generate documentation for the structure, tables, and UI components of an application. Build Agent reads the codebase and creates a README file describing the application architecture.
Checkpoints and conversation change log -- The conversation change log tracks every change Build Agent makes to your application. It appears automatically in an integrated tab in ServiceNow Studio and lets you view updates, roll back to a previous checkpoint, and deploy changes to an update set.
Update sets -- When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio.
Deploying -- Learn about deployment methods and workflows for moving applications created with Build Agent from development to production environments. Choose the right deployment approach based on your application complexity and organizational requirements.
Reference -- Reference topics provide additional information about using Build Agent to create and edit apps, as well as ServiceNow metadata.
Supported metadata -- Metadata and app file types that Build Agent can create and manage.
Example prompts -- Explore example prompts for building apps, as well as adding governance, UI and other ServiceNow metadata to help you get started with prompting Build Agent.
Supported file types for Build Agent -- Build Agent accepts images, documents, code files, and file types specific to ServiceNow as uploads. Supported formats, size limits, and general guidelines apply when generating apps and metadata.
Agentic development -- Agentic development, or vibe coding, is an AI-driven approach to application development. Use agentic development and ServiceNow agentic-assisted app building tools to describe your goals in natural language, and have the ServiceNow AI Platform generate full-stack applications, workflows, and integrations. The ServiceNow AI Platform automatically incorporates governance into the app creation process.
Explore -- To build apps agentically on the ServiceNow AI Platform, you interact with tools through a multi-turn conversation interface to build apps, write documentation, or brainstorm ideas. Describe what you want in plain language, and the ServiceNow AI Platform generates complete applications including logic, UI, configuration, and tests.
Audience -- This guide provides a holistic view of agentic development on the ServiceNow AI Platform. It helps you understand the range of agentic development approaches available, from fully automated code generation to agentic development workflows.
What is agentic development -- Agentic development uses AI to turn a natural language description of the outcome you want into applications using prompts in a conversation. Autonomous app development is agentic development on the ServiceNow AI Platform.
Governance -- Agentic development on the ServiceNow AI Platform accelerates application development by using AI to generate code and configurations from natural language prompts. However, speed must not compromise security, compliance, and maintainability.
Tool comparison -- Compare ServiceNow development tools to select the right approach for your agentic development needs.
Workflow -- The agentic development workflow begins with developers providing conversational prompts to the Build Agent tool, which then creates tables, forms, workflows, and automation rules.
General guidelines -- General guidelines for agentic development on the ServiceNow AI Platform cover prompt writing, context management, compliance validation, and development environment setup.
Onboard -- The following checklist helps to ensure your environment is properly configured, that you understand the core tools and general guidelines, and that you adopt secure, compliant workflows. Whether you're new to ServiceNow or transitioning to agentic development, this resource will set you up for success.
Develop -- Use ServiceNow AI Platform environments, products, tools, and skills to develop, expand, test, and deploy apps using a conversational interface. Autonomous app development on the ServiceNow AI Platform is agentic development.
Environments -- You can develop apps agentically with AI tools on the ServiceNow AI Platform in a safe, isolated environment using a non-production instance with Developer Sandboxes, or on a Personal Developer Instance (PDI).
Build Agent overview -- Build Agent is the primary AI-powered development tool that works directly with the ServiceNow AI Platform to help you build applications. It generates code based on natural language descriptions, suggests improvements, and automates repetitive development tasks while you retain control of your application.
Get started -- Use Build Agent on the ServiceNow AI Platform to build apps agentically by executing complex configuration and development tasks through conversational prompts. This approach simplifies editing and creating ServiceNow applications and metadata such as tables, relationships, and access controls, without manual navigation.
Build Agent and tools -- Compare how Build Agent behaves in ServiceNow Studio (UI-first, declarative workflows) versus the ServiceNow IDE (code-first, autonomous full-stack development), so you can choose the right environment for your task and audience.
Custom in-app agents, workflows, skills -- Use Build Agent to create and deploy custom agentic workflows, AI agents, and skills that add agentic experiences to your ServiceNow custom applications, supported by the built-in governance framework.
Limitations -- Build Agent accelerates agentic app development, but it also has some limitations that you should understand before using it. These constraints span feature coverage, platform compatibility, and governance requirements, all of which affect how and when you can use the tool effectively in agentic development workflows.
With ServiceNow Studio -- ServiceNow Studio connects AI-generated apps to enterprise-grade solutions, where you can review, edit, and enhance your application in a dedicated development environment.
With ServiceNow IDE -- The ServiceNow IDE provides a VS Code, file-based editing experience with syntax highlighting, code completion, and real-time installing to your instance. Use this approach to harden generated, scaffolded apps into production-grade solutions.
Now Assist for Creator -- Now Assist for Creator provides core skills for rapid conversational app development. Use the integrated tools to generate scripts, optimize code, scaffold applications, and automate testing through natural language prompts.
Now Assist for App Engine -- Now Assist for App Engine enables you to embed AI functionality into an application that you built on the ServiceNow AI Platform.
Testing -- As part of the agentic development process on the ServiceNow AI Platform, one of the key features is the automatic generation of Automated Test Framework (ATF) tests.
Deployment -- After you generate and expand an app on the ServiceNow AI Platform, the deployment process is tightly integrated into the workflow.
Reference -- Find reference material for agentic development on the ServiceNow AI Platform, including a list of tools and prompt examples.
Skills -- The ServiceNow AI Platform offers a range of skills that support efficiency in each development workflow.
Example prompts -- Use these example prompts to build data models, implement security, create business rules, and generate user interfaces when building an app with ServiceNow AI Platform agentic development tools.
Now Assist for App Engine -- Use Now Assist for App Engine to supercharge custom applications with AI agents and skills.
Explore -- Explore the AI capabilities, users, benefits, and workflow for using Now Assist for App Engine to enhance your custom applications with AI.
AI capabilities -- Learn about the AI capabilities available with Now Assist for App Engine that you can use to enhance custom applications, including skills, AI agents, and agentic workflows.
Record summarization skill -- The Now Assist for App Engine custom app record summarization skill generates AI summaries for the contents of records in custom applications and tables.
Tools included -- Learn about the tools and applications included with Now Assist for App Engine.
Choosing the right AI capability -- Choosing the right AI capability for your custom application is important. Learn about the differences between skills, AI agents, and agentic workflows, use cases for each, and when to choose one capability over another.
Configure -- Learn about the configuration process for Now Assist for App Engine.
Install -- You can install Now Assist for App Engine if you have the admin role.
Now Assist for Creator -- Now Assist for Creator includes generative and agentic AI capabilities that can make developing on the ServiceNow AI Platform more efficient.
Explore -- Explore the AI capabilities, users, benefits, and workflow for using Now Assist for Creator.
Configure -- To get started using Now Assist for Creator, install Now Assist for Creator. Then turn on the skills, AI agents, or agentic workflows that you want to use.
Install -- Install the Now Assist for Creator application to add generative AI functionality to your workflows.
Role -- This role grants users access to Now Assist for Creator skills.
Use generative AI -- Use the generative AI skills available with Now Assist for Creator to help you build faster and smarter on the ServiceNow AI Platform.
App generation -- Use the app generation skill available with Now Assist for Creator to create applications through conversation with generative AI. Describe the app you want to build, and Now Assist for Creator generates it so you can review and modify it.
Explore -- App generation enables you to create applications in ServiceNow Studio by describing your business process in a conversation with Now Assist.
Guidelines for use -- To get the best results from app generation, provide clear and detailed descriptions of your application requirements during your conversation with Now Assist.
Configure -- To build applications with app generation, install Now Assist for Creator and enable the app generation skill in the Now Assist Admin console.
Turn on the skill -- Install the Now Assist for Creator application so that you can get started with creating an application for your organization.
Use the app generation skill to generate apps -- By default, ServiceNow Studio uses Build Agent to create apps with AI. To use the app generation skill instead, disable the Build Agent setting in your ServiceNow Studio preferences.
Generate apps -- Use the app generation skill to build an application in ServiceNow Studio by describing your business process in a conversation with Now Assist.
Add a workspace -- Add a workspace to a custom application by asking Now Assist. Describe what you want in the workspace, or ask Now Assist for recommendations.
Add a flow -- Add a flow to a custom application by asking Now Assist. Describe what you want the flow to do, or ask Now Assist for suggestions.
Review and edit apps -- After app generation creates an application, review and modify it in ServiceNow Studio to verify accuracy and extend functionality.
Reference -- Use these reference topics to look up configuration properties, roles, and related details for app generation.
Roles -- Assign the correct role before using the Now Assist for Creator app generation skill. The role you need depends on whether you are creating or editing an application.
Administrator [admin] role for app generation -- Assign the correct role before using the Now Assist for Creator app generation skill. The role you need depends on whether you are creating or editing an application.
Supported metadata types -- App generation creates seven metadata types, including tables, roles, and record producers. Use this reference to understand what each metadata type does and how app generation uses it.
Supported field types -- App generation supports nine field types, including choice, reference, and string. Use this list to confirm which field types are available when generating an application.
App summary generation -- Use the ServiceNow Now Assist for Creator application to use generative AI for summarizing an app. With a single button, Now Assist for Creator generates the app summary that you can then copy to the app description, or use to find duplicate apps.
Exploring -- With the Now Assist for Creator application, you can generate a summary of an app. You can then copy the summary to the description for the app, and use it to check for duplicate apps.
Configuring -- Enable the app summary generation skill in the Now Assist for Creator application so that you can get started with summarizing applications.
Install -- Install the Now Assist for Creator application so that you can use app summary generation for your organization.
Summarize the app content -- Generate a summary of your app using Now Assist for Creator in ServiceNow Studio. After reviewing the summary, you can use it as a description for your app.
Reference -- The following roles are required for use with the Now Assist for Creator app summary generation skill.
Flow execution analysis -- Analyze flow execution details to identify errors and suggest potential fixes.
Explore flow execution analysis -- Summarize flow execution details and get recommendations to resolve errors with generative AI.
Analyze a flow -- Have Now Assist scan a flow's execution details, identify errors, and suggest fixes.
Turn on the Flow execution analysis skill -- Turn on the flow execution analysis skill to summarize flow execution details and generate recommendations for flow in an error state.
Flow generation -- Use Now Assist for Creator to create a flow or subflow from a text description.
Explore -- Create multiple step flows and subflows with generative AI. Generate appropriate data pill values for supported flow triggers and action inputs.
Turn on skill -- Turn on the flow generation skill to use generative AI to create and edit flows.
Explore -- Create a flow or a subflow from an image by using Now Assist. Capture the detailed process in an image and attach the image to Workflow Studio. Now Assist generates a preview of the flow that you can modify and regenerate.
Turn on skill -- Turn on the flow generation with images skill to use generative AI to create flows and subflows from an image.
Flow recommendations -- Select the next component in your flow from a list of AI-generated recommendations.
Explore -- Select the next component in your flow from a list of AI-generated recommendations. The system generates recommendations based on the current position in the flow and the flow component names listed before.
Turn on skill -- Turn on the flow recommendations skill to get recommendations for the next step of your flow with generative AI.
Flow summarization -- Summarize what a flow or subflow does by using generative AI.
Explore -- Summarize what a flow or subflow does by using generative AI.
Turn on skill -- Turn on the flow summarization skill to generate a summary of what a flow or subflow does.
Playbook generation -- Generate a playbook using AI from text prompt or image inputs. For example, you can enter a text description to generate a playbook for managing customer support cases.
Playbook generation from text prompt or image -- Generate a playbook using AI from text prompt or image inputs. For example, you can enter a text description to generate a playbook for managing customer support cases.
Configure -- Turn on the Now Assist for Creator playbook generation skill to use generative AI to create playbook outlines.
Configure -- Turn on the playbook recommendations skill to get recommendations for the activity definition to use in your placeholder activities with AI Search.
Generate recommendations for placeholder activities -- Select the activity definition for a placeholder activity from a list of AI-generated recommendations. The system generates recommendations based on an activity’s name and description.
Test generation -- Simplify your automated test authoring by leveraging the power of ServiceNow's Test generation skill available with Now Assist for Creator. Simply describe your test requirements, and Test generation generates the test for you. You can then review the generated test before accepting it or make any edits with an updated prompt.
Exploring Test generation -- If you are new to Test generation application, read this overview to learn what the app can do.
Using Test generation -- Leverage the power of Now Assist technology to streamline test creation with the Test generation application.
Generate a test using Test generation -- Simplify and automate your testing process with Test generation. Describe your desired test, and Now Assist empowered Test generation application automatically generates the necessary tests.
UI generation -- UI generation in Now Assist for Creator uses AI-powered skills to help app developers, UI Builder admins, and low-code developers build experiences on the ServiceNow AI Platform using natural language.
Explore -- Learn how UI generation uses AI-powered skills to help app developers, UI Builder admins, and low-code developers build experiences on the ServiceNow AI Platform using natural language.
Experience Generation -- Experience Generation is a Now Assist capability in UI Generation that uses AI to generate fully functional, multi-page experiences from plain-English descriptions.
UI Builder Agent -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Client script summarization -- Client script summarization uses Now Assist to create easy-to-understand explanations of client scripts within the UI Builder editor. This feature helps creators to learn what a script does without needing to read the complex code.
Data binding generation -- Now Assist generates data bindings for component properties using natural language instructions, reducing the need to manually navigate data trees or construct formulas.
Event handler generation -- Now Assist event handler generation enables you to configure event handlers for UI components using natural language, eliminating the need for manual configuration of complex routing parameters and binding expressions.
Module generation -- Now Assist generates application modules in UI Builder workspaces using natural-language prompts.
Install -- Install the Now Assist for Creator application from the ServiceNow Store to enable UI generation.
Grant UI Builder admin role -- Assign the UI Builder administrator role to a user by editing the user record and adding the ui_builder_admin role.
Configure UI Builder Agent -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Install required applications for UI Builder Agent -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Enable UI Builder Agent in AI Agent Studio -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Enable the Now Assist panel -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Activate AI search -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Activate the Now Assist Panel- Platform (default) assistant -- The UI Builder Agent is a Now Assist AI agent that assists low-code developers working in UI Builder by responding to questions, information requests, and page editing instructions.
Use -- UI generation in Now Assist for Creator enables developers to build ServiceNow portal experiences faster using natural language. Instead of manually configuring each page, module, or data binding, you describe what you need, and Now Assist for Creator it for you.
Experience generation -- Use Now Assist in UI Builder to generate a multi-page experience from a natural language description of what you want to build.
Review and save an experience preview -- Use Now Assist in UI Builder to generate a multi-page experience from a natural language description of what you want to build.
Verify the generated experience -- Use Now Assist in UI Builder to generate a multi-page experience from a natural language description of what you want to build.
Using UI Builder agent -- Use the UI Builder agent to learn about features and functionality, understand your page setup, and accelerate page configuration.
Learn about UI Builder -- Use the UI Builder agent to learn about features and functionality, understand your page setup, and accelerate page configuration.
Understand page configuration -- Use the UI Builder agent to learn about features and functionality, understand your page setup, and accelerate page configuration.
Accelerate page configuration -- Use the UI Builder agent to learn about features and functionality, understand your page setup, and accelerate page configuration.
Client script summarization -- Use the client script summarization skill to generate a plain-language summary of a client script directly in the UI Builder editor.
Data binding generation -- Automatically generate a data binding and formula using natural language with correct syntax.
Event handler generation -- Use Now Assist in UI Builder to configure event handlers. At present, you can configure Open page or URL, Open or close modal, and View load requested event handlers.
Module generation -- Use Now Assist to generate modules for your application by entering natural language prompts instead of manually configuring them.
Use case -- Learn how UI Generation capabilities in Now Assist for Creator support developers in creating and configuring UI Builder experiences using natural language.
Experience generation -- Learn how to generate a multi-page UI experience from a natural language description.
UI Builder Agent -- Learn UI Builder features and accelerate page configuration using conversational AI.
Formula operators and synonyms -- Data Binding Generation enables Now Assist to recognize property names by using a set of frequently used synonyms.
Use agentic AI -- Use the AI agents and agentic workflows available with Now Assist for Creator to help you build on the ServiceNow AI Platform more efficiently.
ATF troubleshooting agent -- Use ATF troubleshooting agent to simplify test failure diagnosis on specific metadata.
Explore -- ATF troubleshooting agent streamlines the process of figuring out why tests are failing on specific metadata.
Install -- Install the Now Assist for Creator application from the ServiceNow Store to get the ATF troubleshooting agent application.
Use -- Use ATF troubleshooting agent to significantly reduce the skills and resources needed to troubleshoot test failures on covered metadata.
References -- The reference topics provide additional information about ATF troubleshooting agent.
Release lifecycle documentation AI agent -- Automate documentation tasks across the app development lifecycle with the release lifecycle documentation AI agent, available with Now Assist for Creator.
Explore -- Learn about how the release lifecycle documentation AI agent works to help you to manage application development at scale by generating useful, transparent documentation throughout the app lifecycle.
Configure -- Configure the release lifecycle documentation AI agent to start automating your app governance tasks.
Roles -- Learn about which roles are required for using the release lifecycle documentation AI agent.
Generate release notes -- Generate release notes to document app changes and versions over time.
Test Agent -- Use Test Agent to streamline the process of authoring, running, and troubleshooting tests autonomously from a single interface. Test Agent generates test coverage for code produced by Build Agent, executes tests, and performs root cause analysis on failures, enabling end‑to‑end build‑to‑test workflows within a single development session.
Explore -- Test Agent autonomously manages end‑to‑end test authoring, execution, and troubleshooting from a single prompt.
Install -- Learn about the prerequisites required to access and use Test Agent.
Use -- Use Test Agent to significantly reduce the skills and resources needed to troubleshoot test failures on covered metadata.
References -- The reference topics provide additional information about Test Agent.
Test Agent guidelines -- Leverage the full potential of Test Agent by following these guidelines.
Developing your application -- Build a custom application to meet the business needs of your organization. Choose a builder for the type of user experience or workflow that you want to create.
App Engine products and offerings -- App Engine is a ServiceNow AI Platform suite of products to help boost productivity by automating workflows.
Creator Studio -- Creator Studio is a no-code application builder on the ServiceNow AI Platform that lets non-developers create request-fulfillment apps without writing code. Use Creator Studio to build apps that manage employee requests, approvals, and fulfillments, such as equipment requests or travel approvals, directly on the ServiceNow AI Platform.
Explore -- Creator Studio makes creating apps easier by dividing their creation into simple steps. In this section, we'll explain each one.
Example apps -- Creator Studio enables you to build apps where people can make requests.
App Engine instead of customizing -- App Engine development tools, such as Creator Studio, offer an excellent alternative to customizing existing applications on the ServiceNow AI Platform.
Customize vs. configure -- There are important differences between customizing and configuring ServiceNow applications. The ServiceNow platform is built to embrace customization and configuration but how you do so can have significant impacts on ServiceNow support, upgrading to future ServiceNow platform versions, and the functionality of the ServiceNow platform.
Create your first app -- Creator Studio helps you create your app by dividing it into smaller parts. Each does something special, and you work on them sequentially.
Quick start -- This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.
Quick start part 1: Create an app -- This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.
Quick start part 2: Add a form -- This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.
Quick start part 4: Add a playbook -- This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.
Get help -- To get help with Creator Studio, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company. You can also check some helpful resources.
Choose development experience -- If you want to develop apps in a more robust environment than Creator Studio, which was designed for no-code developers, you can select a different experience directly from within Creator Studio.
Service desk apps -- Service desk apps enable users to request things, such as IT equipment or travel bookings, and track their fulfillment.
Migrate from Service Creator -- Creator Studio is replacing the older Service Creator tool, which will be retired in the Australia release.
App compatibility -- You can open apps built in Creator Studio in other ServiceNow products, but only apps built in Creator Studio can be opened in Creator Studio.
Apps and tables -- Creator Studio uses catalog templates to streamline the app creation process. Apps use the Request Task table by default, generating a new row for each submitted request, though admins can change the associated table for an app.
Publishing and deployment for apps -- When you build an app in Creator Studio, you must create forms and automation. You can also customize the workspace list configurations and records that fulfillers use before everything is deployed to production.
Configure -- Admins need to install Creator Studio before it can be configured for users to start building apps.
Install -- Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.
Development instance strategy -- Make sure to install Creator Studio on all ServiceNow instances where users will be building applications, including the production instance.
Installed components -- When you activate the Creator Studio plugin, various components like tables and user roles are automatically installed.
Configure using Guided Setup -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Admin group -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Collaboration descriptors -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Full access users -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Restricted access users -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Notification emails -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Playbook activities -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Associated table for an app -- So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Pipelines and Deployments to deploy apps -- You can install Pipelines and Deployments and configure a controller instance to deploy apps built in Creator Studio to production instances.
Roles and personas -- Roles control what everyone you work with can do in Creator Studio. Administrators assign roles to give team members permission to configure or use Creator Studio.
Domain separation -- Domain separation is not supported in Creator Studio. This means that you can't separate data, processes, and administrative tasks into distinct groups, called domains, within the ServiceNow AI Platform.
Form generation -- Install and configure Now Assist for Creator in Creator Studio.
Administer -- Admins have special privileges to approve and update tasks in Creator Studio that regular users can't.
Approve app creation requests -- Respond to app creation requests made by users who can't create apps themselves, ensuring that your organization doesn't have too many or redundant apps.
The experience switcher -- The experience switcher can provide access to Creator Studio, ServiceNow Studio, ServiceNow IDE. However, whether you can see and select all of those depends on your role or access level.
Role access to switch experiences -- Add more roles to the Experience Visibility Controls table [sn_udc_experience_visibility_control] to give them access to other products in the experience switcher, such as ServiceNow Studio.
Collaboration -- In Creator Studio, as an administrator or App Engine admin, you have the power to manage how people work together on projects.
Approve collaboration requests -- Admins and App Engine admin can review and approve (or reject) people's requests to join an app's development in Creator Studio.
Manage collaboration permissions -- In Creator Studio, you can control how people work together on apps by setting up permissions called collaboration descriptors. These descriptors define what users can and cannot do.
Customize collaboration permissions -- When you customize collaboration permissions, you can choose more granular actions and parts of the app that users can work with in Creator Studio.
Templates and forms -- As an admin, you can create custom templates and pre-configured questions to help streamline and guide users when they build apps in Creator Studio.
Create catalog templates -- As a ServiceNow admin, you can create customized catalog templates in Service Catalog to guide users through adding forms in Creator Studio.
Create question sets -- Admins can create pre-configured question sets that can be reused across multiple forms without being changed in Creator Studio.
Display AES template -- You can make the App Engine Studio (AES) template, which is hidden by default, appear for users when they create an app in Creator Studio.
An app's table -- Admins can change the default table that apps built in Creator Studio save their requests to.
About changing an app's table -- Admins can change the associated table for an app built in Creator Studio. That is, you can change the table that the app saves its requests to.
Change an app's table -- Change the table associated with an app if you want one that differs from the default.
Notification emails -- Admins can customize existing email notifications and create templates for new email notifications that Creator Studio apps send. For example, you can add branding to notification emails that a request was opened.
About custom activities -- As an admin, you can define custom activities, make them available in Creator Studio, and hide existing activities to help guide users when they add automation to apps.
Create a custom activity -- You must add custom activities to the Creator Studio Activities table [sn_creatorstudio_activity] before users can add them to playbooks when building apps.
Reorder activities -- Change the order that activities appear in the activity picker in Creator Studio to present them in the order you want.
Deactivate an activity -- Deactivate an activity to stop users from adding it to playbooks in Creator Studio.
Disable App type page -- Hide the App type page that appears when users select to create an app by adding a system property to streamline the app creation process.
Manage app deployments and monitor use -- After users create apps, they submit them for you, the admin, to review and deploy. How you deploy them depends on whether you have App Engine Management Center (AEMC) installed on the instance.
Administer access to deployed apps -- After users build apps in Creator Studio and you deploy them to production, as an admin, you are responsible for granting access to those apps to users.
Metadata artifacts for an app -- When a user creates an app in Creator Studio, the ServiceNow AI Platform creates several metadata artifacts, such as tables.
Creator Studio tutorial -- Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.
Tutorial part 1: Create the app -- Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.
Tutorial part 2: Add a form -- Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.
Tutorial part 3: Customize the form -- Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.
Tutorial part 7: Admin deploys the app -- Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.
Build apps -- By now, your admin has set up Creator Studio, given you permission to build an app, and you've got a great idea for a request-fulfillment app! How should you think about using Creator Studio to create your app?
Find apps -- Perhaps you’ve been given permission to work on an app someone else created, or you want to add new items to the catalog in your app. The Creator Studio home page acts as your central hub, listing all the apps people in your company have built using Creator Studio.
Bookmarked apps -- Bookmark an app to quickly find it in Creator Studio, as well as ServiceNow Studio.
Change development experience -- Choose a different development experience if you want a more robust environment using the experience switcher in Creator Studio.
App creation -- Have you ever dreamed of creating your own app? With Creator Studio, you might be closer than you think! The following links will send you to the sections in this guide that will walk you through the steps.
Create an app -- Get started creating an app by specifying basic info for the app that you're building in Creator Studio.
Request admins create an app -- Don't have permission to build an app? Ask your admin to get you started by creating a basic app for you. Just give them a name and tell them what you want the app to do. Once they start it, you’ll take over and modify it.
Edit app settings -- Maybe you want to jazz up your app a bit, for example by giving it a new name, tweaking the description, or swapping in a new image. All it takes is just a few clicks in the settings! Let's dive into how you can do it, even if you're not a tech whiz.
Delete an app -- Delete an app to remove it from Creator Studio.
Collaborate to build apps -- Sometimes you need help with building out your app, and that’s OK! And sometimes other people need your help building their apps, which is great! This point is where collaboration comes into play.
Request app collaboration -- Want to work on an app but don't have access to it? No problem. We'll show you how to ask for access.
Manage collaborators -- Add or remove people who can work on an app, or change their permissions for the app using the Manage collaborators option.
Forms in apps -- To add items or services to your catalog, you must create a different form for each thing being requested.
Add a form -- Add a form to the app you just created. Forms contain questions that people respond to when submitting a service desk request.
Customize a form -- Forms help people ask for things they need, such as a new keyboard or permission to take time off. The default form that's added when you create an app in Creator Studio needs some changes to fit your needs. For example, you must add question labels to gather information about the request.
Now Assist form generation -- Learn how Now Assist for Creator helps you to create forms for you in Creator Studio.
Add dynamic behavior to a form -- Make a form update based on how users answer a question using dynamic behavior. For example, if a user says they want a T-shirt for an event they're attending, you can make a T-shirt size field required.
Form development states -- Think of your app as an online store that contains a catalog of items. To request something, a person needs to fill out a form. It’s your job to create and customize forms for every item in your catalog using Creator Studio.
Add more forms -- Add as many forms as you need to create catalog items for your app. For example, you could have an office booking app with three different forms: one for requesting parking spaces, one for requesting a desk, and one for reserving conference rooms.
Edit form settings -- Edit form settings if you need to change its basic attributes, such as its associated image or attachments are allowed.
Publish a form -- Publishing forms once they're ready makes them available as catalog items in the production instance for published apps.
Work with published forms -- After a form has been published, you can update it, undo changes, and hide it from being visible.
Deleting forms and questions -- Deleting unpublished forms and questions from Creator Studio removes them completely from the ServiceNow AI Platform.
Delete a form -- Delete an unpublished form from a Creator Studio app to remove it completely from the ServiceNow AI Platform.
Hide a form -- Hiding a catalog item for your app's form effectively makes the form inactive. Hidden forms are unavailable in both the app and the catalog it belongs to.
Automation in apps -- How do you simplify and streamline tasks for fulfillers? Use automation! For example, you can have a task assigned automatically to someone based on what type of request it is. We’ll use playbooks to accomplish adding this automation to your app.
Create automations workflow -- Provide your organization's fulfillers with guidance when addressing records generated from the app by adding automated playbooks to it.
Add a playbook -- Create an automated playbook, which is a process that runs whenever a record is created or updated by the app's specified form.
Copy a playbook -- Duplicate an existing playbook and make small changes to it, which may be faster than creating an entirely new automated playbook.
Add activities to a playbook -- Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes.
Add a decision to a playbook -- Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio.
Edit a playbook trigger -- Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running.
Edit a playbook -- Update a playbook to change its settings, or rearrange or remove tasks, to make it work for your app.
Activate a playbook -- Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production.
Delete a playbook -- Delete a playbook to remove it from the app completely.
Configure workspace lists and records -- So, you’ve built your app, and people are submitting requests through it, that’s great! However, you might be wondering where those requests go after they’re submitted. They live in lists in a workspace where fulfillers can work on submitted forms, which you can customize in Creator Studio to suit your needs.
Add a filtered list -- Create custom filtered lists in the app submission workspace to view records that meet specific conditions. For example, if your app has multiple forms, you can create a list for each form by filtering on the record type.
Customize workspace configuration -- Make changes to the app's workspace category where fulfillers review submitted requests from apps built in Creator Studio to adjust how it appears. For example, you can rearrange columns in its lists and customize how the record generated by the request app looks.
Change an app's record layout -- Adjust how the submitted records that your app generates will look, such as the order in which fields appear.
Request App Workspace to fulfill requests -- After users submit a request through an app built in Creator Studio, fulfillers work on the request's submitted record in the Request App Workspace.
Testing and previewing apps -- Before you request deployment for your app, you can test out submitting a form and interact with any associated automation results on the record it creates.
Test a form -- Use the Try it button on the Request forms tab to submit a request, which triggers any associated playbooks and creates a record that you can work with in Creator Studio.
Preview an app's records -- You can preview and interact with the submitted records generated by your app directly in Creator Studio, which mimics what the fullfiller sees in the workspace category for the app.
Deploying apps -- Congrats, you’ve built your app and are ready to share the first version of it with the world. That’s great! Deployment is the next step in the process.
App versions and release notes -- Each deployed version of an app must have a version number and release notes, which helps administrators track app usage and changes.
Request app deployment -- After you've tested your app's forms, playbooks, and workspace category on a non-production instance, for example a development instance, deploy it to a production instance so users can access it.
What happens after I build an app? -- You've added forms and automation to your app, and customized the workspace list configurations. Now what?
Closing requests and notifications -- The records that your app creates when a form is completed are not automatically closed, and some notifications are not automatic and must be configured.
Reference -- Find details on the parts of building apps in Creator Studio, such as descriptions of all possible types of questions or layout options for forms.
Form settings -- You can edit the settings for an app's form in Creator Studio at any time. For example, to change who can access it.
Question types -- Build apps using different types of questions on a form in Creator Studio.
Form layout options -- Adjust how your form, which creates a catalog item, appears in Creator Studio using layout options.
Glossary -- Learn about the terms and concepts used in Creator Studio.
activity -- Learn about the terms and concepts used in Creator Studio.
automation -- Learn about the terms and concepts used in Creator Studio.
board view -- Learn about the terms and concepts used in Creator Studio.
catalog -- Learn about the terms and concepts used in Creator Studio.
App Engine Studio -- ServiceNow App Engine Studio (AES) is a guided, low-code tool for developing rich web applications to store information, automate business processes, and solve business problems. Work that was once assigned to administrators can now be delegated to employees with little to no training using AES.
Explore -- Learn how you can use the low-code app development tool, App Engine Studio (AES), to build powerful applications using guided setup, predefined templates, and workflows.
User interface -- Learn about the App Engine Studio (AES) user interface.
App Engine instead of customizing -- App Engine development tools, such as App Engine Studio, offer an excellent alternative to customizing existing applications on the ServiceNow AI Platform.
Customization vs. configuration with App Engine Studio -- There are important differences between customizing and configuring ServiceNow applications. The ServiceNow platform is built to embrace customization and configuration, but how you do so can have significant impacts on ServiceNow support, upgrading to future ServiceNow platform versions, and the functionality of the ServiceNow platform.
Integrated development tools -- App Engine Studio (AES) provides instant access to several tools available in the ServiceNow AI Platform development suite.
Get help with App Engine Studio -- To get help with App Engine Studio, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company.
App Engine and AES -- Learn about the differences between App Engine and App Engine Studio.
Getting started -- ServiceNow provides citizen developers with several quick training modules for getting started building low-code apps in App Engine Studio (AES).
Configure -- App Engine Studio (AES) configuration involves installing the application and completing guided setup, which walks you through the implementation process, one step at a time. After you finish each setup procedure, you're prompted to begin the next one.
Domain separation -- In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conkeyref at the end that describes domain separation.Domain separation is unsupported for App Engine Studio (AES). Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Installing -- You can install the App Engine Studio (AES) application (com.snc.app-engine-studio) if you have the admin role. The application installs related ServiceNow Store applications and plugins if they are not already installed.
Instance strategy -- You should install App Engine Studio (AES) on all ServiceNow instances where users will develop applications.
AES and the ServiceNow Store -- App Engine Studio (AES) enables you to obtain new and updated features more rapidly. Before you can use AES, you must verify that you have entitlement to it, meaning that you have valid licenses to use it. Then, you can install AES and its plugins from the ServiceNow Store.
Get entitlements -- Install App Engine Studio (AES) by verifying that the application or the product and its associated applications have valid ServiceNow entitlements. An entitlement means you have a license to install the product.
Install AES from the ServiceNow Store for the first time -- Install App Engine Studio (AES) from the ServiceNow Store for the first time. The installation involves several easy steps. Some steps are performed on the ServiceNow Store and some in your ServiceNow AI Platform instance.
Install the AES product and integrations -- Install the App Engine Studio (AES) product to verify that you get all the dependencies, integrations, and tools, such as templates and builders.
Update a previous version -- If you previously installed App Engine Studio (AES) from the ServiceNow Store and if a new version is available, then update the version in your instance.
Upgrade your AES instance to the next family release -- If you are currently running a family release (Australia, for example) and want to upgrade App Engine Studio (AES) to the next release, you don't need to acquire the applications from the ServiceNow Store.
Components installed -- Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles.
Configure AES -- App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance.
Configure personas and roles -- The responsibilities of your staff are controlled by roles assigned to each member. Personas aren’t explicitly part of App Engine Studio (AES) but administrators assign roles to give team members permission to configure or use AES.
Perform configuration tasks -- As you work through the App Engine Studio (AES) guided setup, you must perform different configuration tasks.
Add users to the App Engine Admin group -- Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests.
Grant user access -- Control who has access to build applications in App Engine Studio (AES) by adding users to AES Users group or the AES User Limited group.
Manage template access -- Control who has access to templates in App Engine Studio (AES) using the app_template_admin role. App template admins activate and deactivate templates and grant other users access to share their templates.
Delegate developers -- Delegated development enables designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform. This enables administrators and delegated developers to work together to deliver custom applications through App Engine Studio (AES).
Integrate with Git source control -- Enable application developers to integrate App Engine Studio (AES) with a Git source control repository to save and manage multiple versions of an application from a non-production instance.
Link an app to source control -- Linking an application or application-customization to source control allows application developers to manage changes in App Engine Studio (AES) from a Git repository.
Edit a Git repository configuration -- You can edit a Git repository's integration with App Engine Studio (AES) to change the network protocol selection, credentials or other field entries.
Cloning instances -- Learn how to protect the data, tables, and templates you've created in App Engine Studio when using System Clone to copy instances from production to non-production.
Build -- Meet the business needs of your organization by building custom applications in App Engine Studio (AES).
App creation tutorial -- This App Engine Studio tutorial series guides you through the entire process of building an application using the low-code tools available in the ServiceNow AI Platform.
Planning your application -- Plan out your application before building it in App Engine Studio to streamline the development process.
Create an app -- When you're ready to start building your application, begin creating your application in App Engine Studio.
Building a data model -- After creating an application, start building the data model for the application. Learn about what a data model is and how we build the data model for the tutorial application.
Create a data table -- Create a table to store the data for your application.
Configure a data table -- Configure a table to capture the necessary data for your application.
Creating user experiences -- Create the user experiences for your application. Learn about experiences in App Engine Studio and how we build the user experience for the employee travel request application.
Add a record producer -- Create a record producer to start building user experiences for the employee travel request application.
Configure a record producer -- Configure the record producer so that it contains the necessary questions for employee travel requests.
Adding logic and automation -- Add logic and automation to your application. Learn about logic and automation in App Engine Studio and how we automate the employee travel request application.
Build a decision table -- Build a decision table for the employee travel request application that determines which regional head to route travel requests to.
Create a flow -- Automate the workflow for the employee travel request application by creating a flow.
Add If flow logic -- Automate the workflow for the employee travel request application by creating a flow.
Integrate decision tables -- Automate the workflow for the employee travel request application by creating a flow.
Duplicate repeating actions -- Automate the workflow for the employee travel request application by creating a flow.
Add an Update Record action -- Automate the workflow for the employee travel request application by creating a flow.
Add Else flow logic -- Automate the workflow for the employee travel request application by creating a flow.
Add a Send Email action -- Automate the workflow for the employee travel request application by creating a flow.
Add End Flow flow logic -- Automate the workflow for the employee travel request application by creating a flow.
Test your application -- Verify that your application works as intended before publishing by testing the application experience and flow.
Plan your app development -- The application development process in App Engine Studio (AES) begins with your idea for the next effective app. Careful planning is the key to creating a successful app that is beneficial to your business.
Create your app -- Use a template in App Engine Studio (AES) to build data, experience, logic and automation, and security into your application automatically. Or, create your app from scratch and customize it as needed.
Use an app template -- Build an application in App Engine Studio (AES) that uses predefined data, experience, logic and automation, and security. Add to the template contents to customize the app for your organization.
Available templates -- Use an application template to create an application in App Engine Studio (AES) with preconfigured data, experience, logic and automation, and security.
Document Approval template -- Build an application in App Engine Studio (AES) using the Document Approval template to manage the approval of documents in your organization.
Document Approval template contents -- Build an application in App Engine Studio (AES) using the Document Approval template to manage the approval of documents in your organization.
Emergency Alert template -- Build an application in App Engine Studio (AES) using the Emergency Alert template to manage communications and track essential resources during an emergency.
Emergency Alert template contents -- Build an application in App Engine Studio (AES) using the Emergency Alert template to manage communications and track essential resources during an emergency.
Event Registration template -- Build an application in App Engine Studio (AES) using the Event Registration template to manage scheduling, booking, and registration for company events.
Event Registration template contents -- Build an application in App Engine Studio (AES) using the Event Registration template to manage scheduling, booking, and registration for company events.
Expense Pre-Approval template -- Build an application in App Engine Studio (AES) using the Expense Pre-Approval template to create, track, and manage planned expenses in your organization.
Expense Pre-Approval template contents -- Build an application in App Engine Studio (AES) using the Expense Pre-Approval template to create, track, and manage planned expenses in your organization.
Inventory Tracker template -- Build an application in App Engine Studio (AES) using the Inventory Tracker template to track the status of inventory and assets.
Inventory Tracker template contents -- Build an application in App Engine Studio (AES) using the Inventory Tracker template to track the status of inventory and assets.
Performance Review template -- Build an application in App Engine Studio (AES) using the Performance Review template to automate scheduling, notifications, and feedback for performance reviews.
Performance Review template contents -- Build an application in App Engine Studio (AES) using the Performance Review template to automate scheduling, notifications, and feedback for performance reviews.
Service Request Management template -- Build an application in App Engine Studio (AES) using the Service Request Management template to create, track, and manage service requests in your organization.
Service Request Management template contents -- Build an application in App Engine Studio (AES) using the Service Request Management template to create, track, and manage service requests in your organization.
Team Contacts template -- Build an application in App Engine Studio (AES) using the Team Contacts template to manage contact information for the people in your organization.
Team Contacts template contents -- Build an application in App Engine Studio (AES) using the Team Contacts template to manage contact information for the people in your organization.
Time Off template -- Build an application in App Engine Studio (AES) using the Time Off Requests template to schedule employee vacations and time-off.
Time Off template contents -- Build an application in App Engine Studio (AES) using the Time Off Requests template to schedule employee vacations and time-off.
Build a custom template -- App Engine Studio (AES) provides various predefined application templates. However, creating custom templates can speed up time to production if you have types of applications that you want to create more than once.
Build from an existing application -- Use an existing application as a starting point to build a custom template in App Engine Studio (AES). Existing data, experience, logic and automation, and security roles from the application are automatically added to the custom template.
Build from scratch -- Build your custom template from scratch if none of the predefined App Engine Studio (AES) templates fit your business needs or you don't have an existing application as a starting point.
App template errors -- Learn how to identify and fix your app when unsupported features or metadata stop the template creation process in App Engine Studio (AES).
Scan Failure table -- Learn how to identify and fix your app when unsupported features or metadata stop the template creation process in App Engine Studio (AES).
Assign permissions to publish custom templates -- Assign permissions for developers to publish a custom template to the application repository or the ServiceNow Store. You can grant permissions to publish either a specific custom template or publish all existing custom templates in App Engine Studio (AES).
Individual custom template publishing permissions -- Assign permissions for developers to publish a custom template to the application repository or the ServiceNow Store. You can grant permissions to publish either a specific custom template or publish all existing custom templates in App Engine Studio (AES).
Custom templates and apps publishing permissions -- Assign permissions for developers to publish a custom template to the application repository or the ServiceNow Store. You can grant permissions to publish either a specific custom template or publish all existing custom templates in App Engine Studio (AES).
Publish a custom template -- You can publish a custom template that is built from scratch or from an existing application using App Engine Studio (AES).
Manage template activation -- Manage template activation and deactivation to ensure that users creating apps in App Engine Studio (AES) have access to the best application templates for their needs.
App template sharing -- Specify which users and groups have access to predefined and custom templates in App Engine Studio (AES).
Manage template sharing permissions -- Specify which users and groups have access to predefined and custom templates in App Engine Studio (AES).
Create from scratch -- If the available application templates in App Engine Studio (AES) don't fit your application goal, create an empty application to which you can add data, experience, logic and automation, and security.
Prepare your app for approval -- Prepare your app for the approval process by making any needed changes, such as renaming your app, editing the app description, or replacing the app image. You can also delete the app from App Engine Studio (AES) if it has taken a wrong turn.
Enhance your app -- Whether you use a template or create your app from scratch in App Engine Studio (AES), you must enhance it by creating a data model, user experiences, logic and automation, and security.
Resources -- As you add data, experience, logic and automation, and security to your application, you might interact with several different parts of the ServiceNow AI Platform. The links in the following table point you to resources for adding content in App Engine Studio and also Table Builder, UI Builder, Decision Builder, App Engine Management Center, and the ServiceNow AI Platform.
Create a data model -- Create a data model in App Engine Studio (AES) for your application by creating the tables that will house your application data. Create data tables that will be used in your application by creating the table from scratch, uploading a spreadsheet or PDF, or by using an existing table as a template. You can also create and schedule data imports by mapping a spreadsheet to an existing table in your application.
Create a blank table -- Add a data table to your application from an existing table that you or someone else previously created or from scratch.
Use a spreadsheet -- Add data tables and records to your application by uploading a Microsoft Excel spreadsheet.
Import a spreadsheet -- Upload a Microsoft Excel spreadsheet and use it to create your application data model.
Create a table -- Create new tables directly from a Microsoft Excel spreadsheet import.
Create a table from an extensible table -- Create a new table by extending an existing table, and then using a Microsoft Excel spreadsheet import to update or customize it.
Modify a table -- Use a Microsoft Excel spreadsheet import to update an existing application table.
Use a PDF -- Create tables from a PDF form using the PDF extractor tool in App Engine Studio.
Create a table -- Create tables from a PDF form using the PDF extractor tool in App Engine Studio.
Add fields from a PDF -- Create tables from a PDF form using the PDF extractor tool in App Engine Studio.
Add a reference table -- Create tables from a PDF form using the PDF extractor tool in App Engine Studio.
Create a data integration -- Add new or updated information to your current data sets by importing it into existing tables in your application through the power of Integration Hub. Schedule future imports to add data at specific times.
Modify data tables -- Use Table Builder to modify data tables used in your application.
Add an experience -- Use App Engine Studio (AES) to add an experience to your app. Experiences are the interface, or wrapper, for how users interact with your app.
Record producers vs. catalog items -- Both the record producer and standard catalog item in App Engine Studio (AES) create experiences where users can submit requests through a service portal. However, record producers are more extensible, and enable users to create a record in any table.
Add a record producer -- A record producer enables users to create task-based records, such as an incident record, in apps you create in App Engine Studio (AES) without creating a request. It enables a better end-user experience by standardizing requests using a simplified form.
Sample record producer -- A record producer experience that you create in App Engine Studio (AES) is a service catalog form that generates a task record, such as an incident, instead of a request.
Add a standard catalog item -- Add a standard catalog item to your application in App Engine Studio (AES) so users can submit requests for services and offerings.
Sample standard catalog item -- A standard catalog item displays a form that users can fill in to create requests, such as a form to request an item or service. Standard catalog items make use of the Request table and produce a request record. In addition, generated request items are linked with a workflow, a catalog task, and any related approvals. Using standard catalog items, users can add multiple items to a cart and generate a request for each requested item. Use a catalog item when you want the service catalog form to generate a request, complete with a workflow, approvals, tasks, etc.
Add a workspace -- Create a workspace using Workspace Builder in App Engine Studio (AES). Workspaces provide agents, case managers, help desk professionals, and managers with tools to help answer customer questions and resolve customer problems.
Add a portal -- Create a portal in App Engine Studio (AES) to give your users a site where they can find information, create requests, and complete business tasks.
Sample portals you can build -- A portal is a site where users inside of your organization can find information, submit requests, and complete business tasks.
Add a mobile experience -- Add a mobile experience, or interface, to enable users to access your application from a ServiceNow native mobile app.
Sample mobile experience -- A mobile experience enables users to access your application from a ServiceNow native mobile app.
Editing an experience -- Tailor your app's experience to suit your business needs by building interfaces in App Engine Studio (AES), such as for mobile apps or catalog items.
Preview an experience -- See what an application experience built in App Engine Studio (AES) looks like to your users by previewing it in a browser.
Delete an experience -- Delete an experience, such as a portal or record producer form, that you no longer need within App Engine Studio (AES).
Add logic and automation -- Replace manual work by adding logic and automation to your app in App Engine Studio (AES).
Add a pre-built flow using a template -- Use a pre-built flow to quickly automate manual work in the app you're building in App Engine Studio (AES).
Add a flow from scratch -- If an existing automation template doesn't fit your application goal, define custom automation in App Engine Studio (AES) by building a new flow.
Modify a flow -- To update or change an existing flow for an app you built in App Engine Studio (AES), edit it.
Add a decision -- Create automation for decisions in App Engine Studio (AES). The automation decouples decision logic from code by enabling you to create and manage decision rules.
Edit a decision -- To update or change an existing decision for an app built in App Engine Studio (AES), edit it in Workflow Studio.
Add an email notification -- Build notifications in App Engine Studio (AES) to create automated emails for events using templates or custom messages.
Modify an email notification -- Edit an email notification created for an app in App Engine Studio (AES) to change it. For example, modify when to send the email notification, who receives it, and what it contains.
Edit a process -- To update or change an existing process for an app built in App Engine Studio (AES), edit it in Playbooks.
Add application security -- Control who is permitted to use or edit your application by configuring roles in App Engine Studio (AES).
Build a new role -- Create a custom role for your application in App Engine Studio (AES).
Use an existing role -- Use a previously created role for your application in App Engine Studio (AES).
Source control operations -- The source control integration primarily supports operations from App Engine Studio (AES), but can also support some operations directly from the Git repository.
Import apps from source control -- Import an app or app customization from a source control repository into App Engine Studio (AES) to continue developing it on this instance.
Work with changes in Git -- Developers using App Engine Studio (AES) can pull and commit changes in their Git repository.
Pull changes from a repository -- App developers using App Engine Studio (AES) can pull changes from a linked Git repository to apply remote changes to the local instance.
Commit changes to a repository -- Commit changes made in your application in App Engine Studio (AES) to a linked Git repository. You can either select a few changes to commit, or commit all changes on the instance at once.
Create versions and branches -- App developers using App Engine Studio (AES) can create versions and branches in their Git repositories.
Switch branches -- App developers using App Engine Studio (AES) can create versions and branches in their Git repositories.
Create a branch -- App developers using App Engine Studio (AES) can create versions and branches in their Git repositories.
Set the default branch -- App developers using App Engine Studio (AES) can create versions and branches in their Git repositories.
Stash changes -- Developers can remove and save changes locally to apply them later, and manage stashed changes from App Engine Studio (AES).
Stash local changes -- App developers can remove and save changes locally to apply them later in App Engine Studio (AES).
Manage stashes -- App developers can apply or delete stashed changes from App Engine Studio (AES).
Resolve conflicts -- App developers can select the app file version to use when applying remote or stashed changes in App Engine Studio (AES).
View commit history -- App developers can view the commit history of apps linked to a source control repository in App Engine Studio (AES).
Move application files in a Git repository -- Move application files linked to source control to any folder of the repository when working in App Engine Studio (AES). Allow application developers to store supporting content such as automated tests in the same repository as the applications they support.
Publish your app -- When you have completed your app in App Engine Studio (AES), you need to submit it for approval and publishing. The process you use depends on whether you are linked to source control.
Submit your app for approval and publishing -- Start the process of getting the application you built in App Engine Studio (AES) published by submitting it for administrator review.
Remove an app -- If you have the appropriate permissions, you can remove an application from App Engine Studio (AES).
Use App Engine Management Center -- Track and manage your requests, deployments, applications, and collaborative developers using the App Engine Management Center (AEMC) in your production instance. Additionally, AEMC allows admins to manage app development from intake through production.
Reference -- Reference topics provide additional information about the lists and forms that you use to configure and administer App Engine Studio (AES).
Glossary -- Learn about terms and concepts that are unique to App Engine Studio (AES).
Properties -- System properties control system behavior. The properties in this section are specific to the App Engine Studio (AES) application. You can access system properties for AES by navigating to All App Engine Studio Configuration Properties .
Supported features and metadata in custom templates -- Custom templates in App Engine Studio (AES) support most features and metadata, including, but not limited to tables, forms, roles, ACLs, record producers, simple workspaces, flows, and actions.
ServiceNow CLI -- The ServiceNow CLI is a command-line interface that lets you perform instance operations from your local system. You can extend the CLI to include new commands that meet your application's needs.
Create a default profile -- Create a connection profile that the ServiceNow CLI uses by default. You must create a default profile to set up the CLI's initial connection with an instance.
Create a named profile -- Create a named connection profile to use with specific commands. This allows you to specify a different instance or connection protocol for a specific command.
View profiles -- View all connection profiles set in the configuration file, or view information about a specific profile.
Remove a profile -- Remove a named connection profile that you no longer need from the configuration file.
Refresh your connection -- Update the available commands from the instance for the given profile. Refresh your connection after modifying any of the commands on the corresponding instance in order to keep the CLI up-to-date.
Get help with ServiceNow CLI -- See available commands, command options, and examples, or generate debug logging output.
Manage ServiceNow CLI extensions -- Add extensions to the ServiceNow CLI to load additional functionality and commands, update existing extensions, or remove extensions you no longer need.
ServiceNow Studio -- Use ServiceNow Studio to build, configure, and deploy custom ServiceNow apps from a single development environment. ServiceNow Studio gives admins and developers integrated tools to create app files, edit scoped and global app metadata, and package changes for deployment.
Explore -- ServiceNow Studio is a unified development environment where platform developers create, modify, and deploy apps. Use ServiceNow Studio to manage app files, edit metadata, and package changes for deployment without switching between tools.
ServiceNow Studio and Build Agent tutorial -- Use Build Agent in ServiceNow Studio to develop reusable server‑side logic and create an application on the ServiceNow AI Platform, taking it from initial data modeling through testing and validation.
Use App Engine instead of customizations -- Use App Engine development tools to extend the ServiceNow AI Platform without customizing existing applications. Building a new app preserves upgrade compatibility and keeps your changes isolated and easier to maintain.
Customization vs configuration with ServiceNow Studio -- There are important differences between customizing and configuring ServiceNow applications. The ServiceNow platform is built to embrace customization and configuration, but how you do so can have significant impacts on ServiceNow support, upgrading to future ServiceNow platform versions, and the functionality of the ServiceNow platform.
Access ServiceNow Studio -- Open ServiceNow Studio from the ServiceNow AI Platform All menu or directly from App Engine Studio.
ServiceNow Studio quick start -- Complete these tasks to learn the core workflows in ServiceNow Studio — from finding apps and files to packaging and deploying changes.
Find an app using Search -- Use Search in ServiceNow Studio to find and open any app or app file. You can also activate code search to find snippets of code within specific metadata types on your instance.
Find an app using the Navigator panel -- Use the Navigator panel in ServiceNow Studio to browse apps and app files by metadata type and open them directly.
Bookmark apps and files -- Bookmark apps and app files in ServiceNow Studio so you can access them quickly from the Bookmarks tab in the Navigator panel.
Bookmark lists -- Bookmark lists in ServiceNow Studio so you can return to them quickly from the Bookmarks tab in the Navigator panel.
Create a collection of files -- Create a collection of files for personal organization in ServiceNow Studio. Create and organize folders, and group apps and files your way.
Add files to a collection -- Group your apps, files and lists into folders and organize your work by stories, epics, or related use cases.
Access recently opened apps and files -- Reopen recently accessed apps and app files in ServiceNow Studio from the home page or the Navigator panel.
Find info about an app -- Use the App details page in ServiceNow Studio to view metadata about an existing application and take action directly from the page.
Navigate directly to a table -- Open any table view directly in ServiceNow Studio using the Open list feature in the Navigator panel or search shortcuts in the Search bar.
Open apps and app files across scopes -- Open and edit apps and app files in any scope — global or custom — in ServiceNow Studio. The current scope displays at the bottom of the screen and updates automatically when you switch to an app in a different scope.
Focus the Navigator panel on an app file -- Focus the Navigator panel on any open app or app file in ServiceNow Studio so the Navigator panel reflects your current work context.
Access development tools and builders -- Access development tools and builders directly in ServiceNow Studio so you can build apps without switching between interfaces. Open any file type to launch the correct tool or builder automatically.
Create an update set -- Create an update set in ServiceNow Studio to package your app changes for deployment.
Publish changes to the Application Repository -- Publish app changes from ServiceNow Studio to the Application Repository (App Repo) so your updates are available to all instances of your application.
ServiceNow Studio user interface -- Use the ServiceNow Studio interface to build, manage, and deploy applications — and customize the interface to match your workflow.
ServiceNow Studio for AES developers -- If you currently develop in App Engine Studio, use ServiceNow Studio to access advanced development capabilities while retaining the core features you already use.
Builders in ServiceNow Studio -- Builders are specialized tools in ServiceNow Studio for editing metadata records associated with tables that extend sys_metadata. Use builders to create and edit file types such as decision tables, flows, and forms as part of your app development.
Integrated dev tools in ServiceNow Studio -- Use the development tools in ServiceNow Studio to build apps, flows, tables, forms, and more — all without leaving the platform.
ServiceNow Studio and legacy products -- If you previously used Guided Application Creator or the legacy Studio product to develop apps, use ServiceNow Studio to continue your app development. ServiceNow Studio replaces both products with a unified development environment on the ServiceNow AI Platform.
Configure -- ServiceNow Studio is available by default on the ServiceNow AI Platform and requires no additional configuration. It uses the platform's existing development tools, so you can start building immediately.
Domain separation -- Domain separation is not supported for ServiceNow Studio. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Installing ServiceNow Studio -- ServiceNow Studio is available for you to use on the ServiceNow AI Platform. You can also access premium features with an App Engine Enterprise license.
Instance strategy -- Install ServiceNow Studio on every ServiceNow instance where you develop applications, then define your company's access and deployment strategy.
Managing access to ServiceNow Studio -- Manage access to ServiceNow Studio by assigning delegated development permissions. Admins, delegated developers, and users with Guided Application Creator (GAC) roles can develop apps and app files in ServiceNow Studio.
Roles and access in app development tools -- Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE is controlled by the roles and permissions your admin assigns. Update role assignments when you need to change which tools a user can access.
Personas and roles -- Admins, delegated developers, and users with Guided Application Creator roles can access and develop in ServiceNow Studio. Each role has different capabilities and permissions.
Elevate your role -- Elevate your role to security_admin in ServiceNow Studio to configure roles and access control lists (ACLs).
Managing access to the experience switcher -- The experience switcher can provide access to Creator Studio, ServiceNow Studio, ServiceNow IDE. However, whether you can see and select all of those depends on your role or access level.
Source control integration -- Link your application to a Git source control repository in ServiceNow Studio to save, manage, and share multiple versions of a global or scoped application from a non-production instance.
Link an app to source control -- Link an application or application customization to a Git repository in ServiceNow Studio so application developers can manage changes directly from the platform.
Edit a Git repository configuration -- Edit a Git repository configuration in ServiceNow Studio to update the network protocol, credentials, or other connection details.
Collaborating on apps -- Collaborate with other developers on app development in ServiceNow Studio by inviting them to co-create and develop apps with you.
View collaborators on an app -- View the collaborators on an app in ServiceNow Studio to see who has access and what role each person has.
Add collaborators to an app -- Add collaborators to an app in ServiceNow Studio so other developers can co-develop the app with you.
Remove collaborators from an app -- Remove a user or group as a collaborator in ServiceNow Studio to revoke their access to an app.
Use -- Use ServiceNow Studio to build and deploy apps using integrated ServiceNow AI Platform features, development tools, and builders — all in a single environment.
Build Agent in ServiceNow Studio -- Use Build Agent, an autonomous AI agent, to create and update applications in ServiceNow Studio through conversational interaction.
Applications in ServiceNow Studio -- Create, update, manage, publish, and delete applications in ServiceNow Studio — all from a single environment, based on your permissions.
Create an application -- Create a custom application in ServiceNow Studio, then add data, automation, or other app files using integrated development tools and builders.
Add a file to your app -- Create a custom application in ServiceNow Studio, then add data, automation, or other app files using integrated development tools and builders.
Create an app file -- Create an app file in ServiceNow Studio to define how an aspect of an application functions — such as which users can access it or how it processes data.
App details page -- The App details page in ServiceNow Studio shows metadata about your app and provides access to common development actions — including creating files, updating app settings, and publishing your app for deployment.
Modify an app's settings -- Modify an app's settings in ServiceNow Studio to update the name, description, scoping, or other metadata. Use the Related Links section to publish the app, manage collaborators, and more.
Bookmark application files -- Bookmark apps and app files in ServiceNow Studio so you can access them quickly from the Bookmarks tab in the Navigator panel.
Source control in ServiceNow Studio -- Use source control in ServiceNow Studio to manage app versions, commit changes, and collaborate with other developers through a linked Git repository.
Source control operations -- Most source control operations in ServiceNow Studio run from within the platform. Some operations — such as creating branches and tags — can also be performed directly from the Git repository.
Import an app from source control -- Import an application from a Git repository into ServiceNow Studio to create a local copy of the app on your non-production instance. The repository must contain a valid ServiceNow application, and your credentials must have read access.
Work with changes in Git -- Pull and commit changes in a Git repository directly from ServiceNow Studio to keep app development in sync across your team.
Pull changes -- Pull changes from a linked Git repository in ServiceNow Studio to apply remote updates to the local instance.
Commit changes -- Commit changes made in ServiceNow Studio to a linked Git repository by selecting individual file changes or committing all changes on the instance at once.
Stash local changes -- Stash local application file changes in ServiceNow Studio to save them temporarily, pull the latest version from the repository, and recover the stashed changes at a later time.
Manage stashed changes -- Apply or delete stashed changes in ServiceNow Studio to restore saved work or remove stashes that are no longer needed.
Resolve conflicts -- Resolve conflicts in ServiceNow Studio when applying remote or stashed changes that conflict with the local version of the same application file.
Create versions and branches in Git -- Create tags and branches in a Git repository from ServiceNow Studio to version application releases and manage parallel development streams.
Switch repository branches -- Create tags and branches in a Git repository from ServiceNow Studio to version application releases and manage parallel development streams.
Create a repository branch -- Create tags and branches in a Git repository from ServiceNow Studio to version application releases and manage parallel development streams.
Set a default branch -- Create tags and branches in a Git repository from ServiceNow Studio to version application releases and manage parallel development streams.
View commit history -- View the commit history of apps linked to a source control repository in ServiceNow Studio to review what changes were committed, by whom, and when.
Move app files in a Git repository -- Move application files linked to source control to any folder in the repository from ServiceNow Studio to store supporting content, such as automated tests, alongside the applications they support.
Preview an app file -- Preview app files in ServiceNow Studio before publishing to confirm that the file looks and functions as expected. Only files with a user interface support preview.
Find an app file using code search -- Use code search in ServiceNow Studio to search through all applications and tables on an instance to locate a specific app, app file, or code snippet.
Delete an app -- Delete apps that are no longer needed from ServiceNow Studio to remove them permanently from the instance.
Now Assist tools and AI files -- Use Now Assist tools in ServiceNow Studio to create and summarize apps using AI, and add AI files to applications to enhance user productivity through conversation and proactive experiences.
Change your development experience -- Switch between development environments in ServiceNow Studio using the experience switcher to use the best tool for each stage of your app development.
Viewing app origination information -- View app origination information on the App details page in ServiceNow Studio to determine where an app was created and which environment to use for editing and deployment.
Debug a script -- Use the Script Debugger in ServiceNow Studio to debug business rules and other synchronous server-side scripts during app development.
Metadata app file categories -- Use ServiceNow Studio to access and work with all metadata types that the ServiceNow AI Platform supports, from automations and integrations to user interface files.
App deployment in ServiceNow Studio -- Deploy applications from ServiceNow Studio using several methods, including using deployment requests to move application and global file changes across instances. Deployment options depend on organizational preference and standards.
Update sets -- Use update sets in ServiceNow Studio to group configuration changes and move them as a unit to other instances for testing or deployment.
Create an update set -- Create an update set in ServiceNow Studio to package app changes for deployment to other instances.
Mark an update set complete -- Mark an update set as Complete in ServiceNow Studio to make the changes available for retrieval by other instances.
Application Repository in ServiceNow Studio -- Publish custom applications from ServiceNow Studio to the ServiceNow Application Repository to distribute them to other instances in the organization.
Pipelines in ServiceNow Studio -- Use pipelines in ServiceNow Studio to automate the propagation and installation of applications from one instance to another. Admins manage deployment requests in the App Engine Management Center (AEMC).
Reference -- Use these reference topics to find details about the Navigator panel taxonomy, supported file types, properties, and collaboration permissions in 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.
ServiceNow Studio properties -- Configure system properties to control ServiceNow Studio application behavior and delegated development deployment. Access ServiceNow Studio system properties by navigating to All sys_properties.list .
Supported code search file types -- Reference the file types that ServiceNow Studio supports when using code search to locate scripts and metadata across an instance.
Collaboration permissions for ServiceNow Studio -- Collaboration permissions determine what delegated developers can do when working on an app in ServiceNow Studio. Admins or app owners set these permissions.
Custom Application record form -- The Custom Application form enables you to add or modify information about a custom application to define its behavior.
ServiceNow Fluent -- Define application metadata in source code using the ServiceNow Fluent domain-specific programming language.
JavaScript modules and third-party libraries -- Optimize your code base using JavaScript modules to group related code or add third-party libraries and reuse their code within applications.
Third-party library support -- Review which common third-party libraries are supported, partially supported, or unsupported by the ServiceNow IDE and ServiceNow SDK.
UI development with React -- Develop a user interface (UI) with the React library to build a full-stack application in source code.
Application configuration -- Configure a custom application [sys_app] in the now.config.json file for an application in source code.
ServiceNow IDE -- Create and develop applications in source code in an integrated development environment (IDE) on the ServiceNow AI Platform to improve collaboration across development teams and accelerate application development.
Explore -- Learn about developing applications in source code in the ServiceNow IDE.
ServiceNow IDE user interface -- The ServiceNow IDE user interface contains many of the same features as Visual Studio Code for the Web and some unique functionality for creating ServiceNow applications.
Features in the ServiceNow IDE -- The ServiceNow IDE user interface contains many of the same features as Visual Studio Code for the Web and some unique functionality for creating ServiceNow applications.
1. Create an application -- Create an application that you can develop in source code in the ServiceNow IDE.
2. Initialize a repository -- Initialize a local Git repository for an application in the ServiceNow IDE and push it to a remote Git repository in GitHub to manage the application in source control.
Initialize a Git repository -- Initialize a local Git repository for an application and push it to a remote Git repository to manage an application in source control.
Using source control -- Use Git commands and other source control features in the ServiceNow IDE to manage changes to an application across a development team.
Develop applications -- Create and develop applications in source code with the ServiceNow IDE. Build applications to make your changes available across an instance and collaborate with users of any skill set.
Synchronizing applications -- Synchronizing an application in the ServiceNow IDE downloads and transforms application metadata into ServiceNow Fluent code.
Create and use JavaScript modules -- Optimize your codebase by defining reusable code blocks with JavaScript modules in the ServiceNow IDE.
Use third-party libraries -- Call third-party libraries in your application to use existing open-source functionality with the ServiceNow IDE.
Install an npm package from a private registry -- Install Node Package Manager (npm) packages from a private registry as dependencies in your application to use them as third-party libraries.
Create an application file -- Create an application file in an embedded ServiceNow AI Platform user interface from the ServiceNow IDE.
Build and install an application -- Build an application to compile its source code and install application changes across an instance from the ServiceNow IDE.
Reference -- Reference topics include information about ServiceNow Fluent APIs and ServiceNow IDE properties, roles, and more.
ServiceNow IDE commands -- Use commands from the command palette to perform many actions in the ServiceNow IDE.
ServiceNow IDE properties -- Manage how the ServiceNow IDE functions on an instance using the following system properties.
ServiceNow IDE roles -- The following roles are installed for use with ServiceNow IDE.
ServiceNow SDK -- Create and develop applications in source code locally in Visual Studio Code Desktop and upload changes to an instance using the ServiceNow software development kit (SDK).
Explore -- Learn about developing applications in source code locally and installing changes on an instance with the ServiceNow SDK.
Configure -- Install or upgrade the ServiceNow SDK locally and get language processing and validation for ServiceNow Fluent in Visual Studio Code.
Install the ServiceNow SDK -- Install the ServiceNow software development kit (SDK) in a local application using Node Package Manager (npm).
Upgrade the ServiceNow SDK -- Upgrade to the latest version of the ServiceNow SDK for use with instances beginning with the Washington DC release.
Authenticate using OAuth 2.0 -- Use OAuth 2.0 authentication to connect to a ServiceNow instance with the ServiceNow SDK.
Add applications -- Add applications to your local system to get started with development in source code with the ServiceNow SDK.
Create an application -- Create an application to develop in source code with the ServiceNow SDK.
Convert an application -- Convert an existing application to support development in source code with the ServiceNow SDK.
Develop applications -- Create and develop applications in source code locally in Visual Studio Code Desktop with the ServiceNow SDK. Build and install applications to make your changes available on an instance.
Use third-party libraries -- Call third-party libraries in your application to use existing open-source functionality with the ServiceNow SDK.
Download dependencies -- Download application dependencies and TypeScript definitions from an instance for IntelliSense and validation of scripts and ServiceNow Fluent code.
Download module and script dependencies -- Download application dependencies and TypeScript definitions from an instance for IntelliSense and validation of scripts and ServiceNow Fluent code.
Build and install an application -- Build and install a local application developed with the ServiceNow SDK on a ServiceNow instance.
Reference -- Reference topics provide additional information about ServiceNow SDK CLI commands and ServiceNow Fluent APIs.
ServiceNow SDK CLI -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
auth -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
init -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
build -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
install -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
dependencies -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
transform -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
move -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
download -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
clean -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
pack -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
explain -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
query -- Use the ServiceNow SDK command-line interface (CLI) to manage changes between a local application and the application on an instance.
ServiceNow Fluent API reference -- Use ServiceNow Fluent APIs to define the metadata that makes up scoped applications in source code with the ServiceNow IDE or ServiceNow SDK.
ServiceNow Fluent language constructs -- ServiceNow Fluent language constructs provide additional functionality for development in source code with ServiceNow Fluent APIs.
ACL API -- The Access Control List API defines access control lists [sys_security_acl] that secure parts of an application.
ACL object -- The Access Control List API defines access control lists [sys_security_acl] that secure parts of an application.
Application Menu API -- The Application Menu API defines menus in the application navigator [sys_app_application].
ApplicationMenu object -- The Application Menu API defines menus in the application navigator [sys_app_application].
ATF Test API -- The Automated Test Framework Test API defines automated tests [sys_atf_test] that you can run to confirm that your instance works after making a change.
Test object -- The Automated Test Framework Test API defines automated tests [sys_atf_test] that you can run to confirm that your instance works after making a change.
Business Rule API -- The Business Rule API defines server-sides scripts [sys_script] that run when a record is displayed, inserted, updated, or deleted, or when a table is queried.
BusinessRule object -- The Business Rule API defines server-sides scripts [sys_script] that run when a record is displayed, inserted, updated, or deleted, or when a table is queried.
Client Script API -- The Client Script API defines client-side scripts [sys_script_client] that run JavaScript on the client (web browser) when client-based events occur, such as when a form loads, after form submission, or when a field changes value.
ClientScript object -- The Client Script API defines client-side scripts [sys_script_client] that run JavaScript on the client (web browser) when client-based events occur, such as when a form loads, after form submission, or when a field changes value.
Cross-Scope Privilege API -- The Cross-Scope Privilege API defines cross-scope privileges [sys_scope_privilege] for runtime access tracking.
CrossScopePrivilege object -- The Cross-Scope Privilege API defines cross-scope privileges [sys_scope_privilege] for runtime access tracking.
Dashboard API -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
Dashboard object -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
tabs array -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
widgets array -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
componentProps object -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
permissions array -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
visibilities array -- The Dashboard API defines dashboards [par_dashboard] for organizing and sharing data visually.
Email Notification API -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
EmailNotification object -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
triggerConditions object -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
emailContent object -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
digest object -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
recipientDetails object -- The Email Notification API defines notifications [sysevent_email_action] that send automated emails based on database operations, custom events, or manual triggers.
Flow API -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
Flow object -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
Subflow object -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
wfa.trigger function -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
wfa.action function -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
wfa.flow_logic function -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
wfa.dataPill function -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
wfa.subflow function -- The Flow API defines flows and subflows [sys_hub_flow], which automate business processes with reusable multiple-step components.
Import Sets API -- The Import Sets API defines transform maps [sys_transform_map] that specify how to transform and map data from the import set staging table to target tables.
ImportSet object -- The Import Sets API defines transform maps [sys_transform_map] that specify how to transform and map data from the import set staging table to target tables.
fields object -- The Import Sets API defines transform maps [sys_transform_map] that specify how to transform and map data from the import set staging table to target tables.
scripts array -- The Import Sets API defines transform maps [sys_transform_map] that specify how to transform and map data from the import set staging table to target tables.
List API -- The List API defines list views [sys_ui_list] for tables.
List object -- The List API defines list views [sys_ui_list] for tables.
Property API -- The Property API defines system properties [sys_properties] that control instance behavior.
Property object -- The Property API defines system properties [sys_properties] that control instance behavior.
Record API -- The Record API defines records in any table. Use the Record API to define application metadata that doesn't have a dedicated ServiceNow Fluent API.
Record object -- The Record API defines records in any table. Use the Record API to define application metadata that doesn't have a dedicated ServiceNow Fluent API.
Role API -- The Role API defines roles [sys_user_role] that grant specific permissions to users of an application.
Role object -- The Role API defines roles [sys_user_role] that grant specific permissions to users of an application.
Script Action API -- The Script Action API defines script actions [sysevent_script_action] that run when an event occurs.
ScriptAction object -- The Script Action API defines script actions [sysevent_script_action] that run when an event occurs.
Script Include API -- The Script Include API defines script includes [sys_script_include] that store JavaScript functions and classes for use by server-side scripts.
ScriptInclude object -- The Script Include API defines script includes [sys_script_include] that store JavaScript functions and classes for use by server-side scripts.
Scripted REST API -- The Scripted REST API defines the endpoints, query parameters, and headers for a scripted REST service [sys_ws_definition].
RestApi object -- The Scripted REST API defines the endpoints, query parameters, and headers for a scripted REST service [sys_ws_definition].
routes object -- The Scripted REST API defines the endpoints, query parameters, and headers for a scripted REST service [sys_ws_definition].
parameters and headers objects -- The Scripted REST API defines the endpoints, query parameters, and headers for a scripted REST service [sys_ws_definition].
versions object -- The Scripted REST API defines the endpoints, query parameters, and headers for a scripted REST service [sys_ws_definition].
Service Catalog API -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
CatalogItem object -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
CatalogItemRecordProducer object -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
CatalogUiPolicy object -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
actions array -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
CatalogClientScript object -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
VariableSet object -- The Service Catalog API defines catalog items [sc_cat_item], record producers [sc_cat_item_producer], and related aspects of service catalogs.
SLA API -- The Service Level Agreement API defines service level agreements [contract_sla] that set the amount of time for a task to reach a specified condition, ensuring that tasks are resolved according to the service levels agreed between a service provider and customer.
Sla object -- The Service Level Agreement API defines service level agreements [contract_sla] that set the amount of time for a task to reach a specified condition, ensuring that tasks are resolved according to the service levels agreed between a service provider and customer.
Service Portal API -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
SPWidget object -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
SPAngularProvider object -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
SPWidgetDependency object -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
CssInclude object -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
JsInclude object -- The Service Portal API defines custom widgets [sp_widget] for portal pages.
Table API -- The Table API defines tables [sys_db_object] to store data in an application.
Table object -- The Table API defines tables [sys_db_object] to store data in an application.
Column object -- The Table API defines tables [sys_db_object] to store data in an application.
choices object -- The Table API defines tables [sys_db_object] to store data in an application.
label object -- The Table API defines tables [sys_db_object] to store data in an application.
licensingConfig object -- The Table API defines tables [sys_db_object] to store data in an application.
autoNumber object -- The Table API defines tables [sys_db_object] to store data in an application.
UI Action API -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
UiAction object -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
form object -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
list object -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
client object -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
workspace object -- The UI Action API defines custom user interface (UI) actions [sys_ui_action], such as buttons, links, and context menu items on forms and lists.
UI Page API -- The UI Page API defines custom user interface (UI) pages [sys_ui_page] that display forms, dialogs, lists, and other UI components.
UiPage object -- The UI Page API defines custom user interface (UI) pages [sys_ui_page] that display forms, dialogs, lists, and other UI components.
UI Policy API -- The UI Policy API defines user interface (UI) policies [sys_ui_policy] that dynamically change the behavior of information on a form and control custom process flows for tasks.
UiPolicy object -- The UI Policy API defines user interface (UI) policies [sys_ui_policy] that dynamically change the behavior of information on a form and control custom process flows for tasks.
actions array -- The UI Policy API defines user interface (UI) policies [sys_ui_policy] that dynamically change the behavior of information on a form and control custom process flows for tasks.
relatedListActions array -- The UI Policy API defines user interface (UI) policies [sys_ui_policy] that dynamically change the behavior of information on a form and control custom process flows for tasks.
Workspace API -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
Workspace object -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
UxListMenuConfig object -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
categories array -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
lists array -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
Applicability object -- The Workspace API defines configurable workspace experiences for organizing and sharing data visually.
Guided Application Creator -- Guided Application Creator is a legacy development interface for building applications.
Service Creator -- Service creator enables a department to offer custom services through the service catalog, such as the HR department offering tuition reimbursement for further education.
Service creator process -- The service creator process involves requesting and publishing a service category, designating editors and service fulfillers, creating and publishing services, and submitting and fulfilling service requests.
Activate Service Creator -- If the Service Creator plugin is not already activated, an administrator can activate it to access the application.
Components created with new service categories -- When you publish a new service category using the Service Creator application, the ServiceNow system creates components for the services in that category.
Manage a service -- Using the Service Creator, department managers can request a new service category, designate editors and service fulfillers for that category, and create and publish services.
Designing services -- Service creator includes an interface for designing services.
Notification configurations -- All service categories start with a set of associated notifications, such as the notification when a task to fulfill a service request is assigned.
Create the category and table -- After the request has been submitted, a catalog administrator can approve or reject the request.
Delete a template notification -- Deleting a template notification prevents new service categories from using the notification, but does not delete notifications for service categories that have already been created.
Designate an editor -- Editors can create and modify services within a service category.
Publish a service -- A service must be published to appear in the service catalog. When first created, new services appear in the Draft Services related list for the service category. Published services appear in the Services related list for the service category. The manager of a service category can publish draft services.
Set up a workspace in VS Code -- Using the ServiceNow Extensions for VS Code, create a project work folder to use as a workspace for ServiceNow applications.
Create a project in VS Code -- ServiceNow applications are contained within a project in the VS Code IDE. Import an application from your ServiceNow instance with the help of ServiceNow Extensions for VS Code.
Clear instance credentials in Visual Studio Code -- Clear the stored credentials of the current project from the system. User credentials (instance URL, user name, password) of a project are stored in the operating system credentials vault so that the user does not need to log in each time.
Reset a project in Visual Studio Code -- Reset the project to the state on the server by discarding all the local changes if you encounter any serious sync issues.
Add custom file types in Visual Studio Code -- If you have work with file types other than the default types provided, you can add additional file types to your instance and edit them in ServiceNow extension for Visual Studio Code.
Create a file in VS Code -- Use the ServiceNow extension to create a new file for your application with your project.
IntelliSense in VS Code -- The IntelliSense code editing feature in the ServiceNow Extensions for VS Code extension provides intelligent code completions which provide auto-completion options to make writing code faster and more efficient.
Telemetry in ServiceNow Extensions for VS Code -- ServiceNow Extensions for VS Code collects information on its various usage patterns such as the commands run with the help of Now Telemetry.
Exploring professional development -- ServiceNow provides a single mobile and web application development platform to quickly build business applications to power digital transformation. Learn how anyone can automate, extend, and build digital workflow apps across the enterprise with the ServiceNow AI Platform.
Plan your application development -- The planning process is the most important step in building an application. Thinking through design and configuration before building has both immediate and long-term benefits for the application.
Plan before you build -- Essentially, an application is a digital program that supports user tasks. Some actions you take when building an application might be irreversible. Be aware of these actions and plan for them in advance.
Build your application -- Build and define the data, design elements, and logic that make up your application.
Define and build the data model -- After planning is complete, define and build the data model. Create one or more tables with fields, load the table with demo data, and verify access controls to the data.
Build the data model -- Create tables and fields on the tables to support the application’s data model.
Secure data -- Data security is one of the most important and overlooked aspects of creating an application. ServiceNow automatically configures access control for a new or selected role during the table creation process. Only users with the role can access the table to read, create, write, and delete.
Manage data -- With the data model (tables and fields) created and security set up, add data into the application’s table(s).
Create design elements -- After the application’s data model is created, secured, and populated with data, create the design elements to access that data.
Primary interfaces -- The primary way for users to interact with a data model is through forms and lists or through mobile.
Self service -- Your application may need a way for end users to be able to access your data model, so there are self-service options available.
Virtual Agent -- Consider Virtual Agent, ServiceNow’s conversational bot platform. Use ServiceNow Virtual Agent (VA) to build and design bot conversations to help users quickly obtain information, make decisions, and perform common work tasks.
Notifications -- After the data model is defined and users are able to interact with the application, determine how the application should communicate with users. Configure notifications to alert users to important application related events, share application information in the knowledge base, and add translations to allow users to interact with the application in their native language.
Translations -- When using one of the Internationalization plugins, most of the fields in the instance are automatically translated. However, customizations are not translated automatically, and need to be translated by hand. In this case, it is best to locate the individual untranslated strings, and insert those translations manually.
Build form and business logic -- The next step in designing an application is to build logic. Logic includes form logic (what people can and cannot see/use on a form) and business logic (rules that govern what happens to data when it is entered).
Form logic -- Controlling what users see when they visit a form can increase productivity and responsiveness. For example, users should only see fields that are useful to them. Users may only need to see certain fields based on what is configured on the form. Apply form logic to control what is visible, read-only, and mandatory on a form.
Business rules and script includes -- Business rules are server-side actions that can be run during CRUD (Create, Read, Update, Delete) operations on instance records.
Flow Designer -- Flow Designer is a ServiceNow AI Platform feature that enables rich process automation capabilities in a consolidated design environment. Flow Designer enables process owners to use natural language to automate approvals, tasks, notifications, and record operations without having to code.
Deploy your app -- Once the application is built and validated, the application needs to be moved to the production environment. Applications can be moved through an application repository or by using Update Sets. Applications should be deployed to test environments prior to moving to production.
Developer Sandboxes -- Developer Sandboxes provide admins and delegated developers the ability to request, access, and manage individual sandboxes on top of the same underlying development instance. Delegated developers can write and merge code and configuration changes without the risk of their changes getting overwritten on the instance mid-development.
Explore -- Developer Sandboxes provide isolated development environments that enable parallel building and testing on top of a shared development instance. Use sandboxes to reduce code conflicts, accelerate delivery, and safely test configurations without affecting other team members' work.
Source control integration -- Use source control with Developer Sandboxes to enable parallel development and prevent merge conflicts.
Metadata, tables, and records -- Each sandbox provisioned with Developer Sandboxes is an isolated environment within an instance. Developers can build and test in parallel without affecting other work.
Guidelines and use cases -- Follow some general guidelines to ensure you're optimizing your use of sandboxes.
Get help with Developer Sandboxes -- To get help with Developer Sandboxes, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company. You can also check some helpful resources.
Installing -- Developer Sandboxes is installed on your instance with assistance from your ServiceNow account team.
Entitlements -- Your company's entitlements determine whether you have access to Developer Sandboxes.
Clone and upgrade impact -- You should understand how plugins and sandboxes work before you clone or upgrade an instance with Developer Sandboxes. Always back up your work in a sandbox before any clone or upgrade, either by exporting the update sets or committing to source control.
Developer Sandboxes domain separation -- If any conkeyrefs are broken, re-add them from the doc/source/reuse/domain-separation/domain-separation-overview.dita file.In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conkeyref at the end that describes domain separation.Domain separation is supported for Developer Sandboxes. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Roles and tables -- Several types of components are installed with activation of Developer Sandboxes, including tables and user roles.
Properties -- The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.
Administering -- If you have permission, you can allocate and retire the sandboxes you've created in your instance.
Allocate a sandbox -- Allocate sandboxes to your development teams so they can start using them for development.
Using sandbox templates -- Developer Sandboxes templates are being deprecated, and should no longer be used.
Requesting a sandbox -- Developers generally have admin rights on the non-production instance where Developer Sandboxes are allocated, and can thus allocate a sandbox to themselves.
Retire a sandbox -- Retire sandboxes that are outdated or no longer needed to make room for new Developer Sandboxes in your instance.
Builder library -- The ServiceNow AI Platform provides a robust set of builder tools that enable you to quickly develop applications for your organization.
Develop a component for Virtual Agent -- Create a custom Virtual Agent component to gather input or display information in the Virtual Agent client interface.
Add properties to communicate with Virtual Agent -- To develop a component for Virtual Agent, add specific properties and actions to interact with the Virtual Agent client interface. The properties required depend on the type of component you are creating.
Add a component to Agent Workspace -- Use custom components to create a custom Workspace interface to fulfill the specific need of your company's agents.
Decision Tables -- Use decision tables to decouple decision logic from your code by creating and maintaining decision rules.
Decision tables in the classic environment -- In the classic environment, you can develop a table to use for your decision answer records. You then associate an answer record to each decision on your decision table. This answer record is returned when the decision is reached based on your inputs.
Table Builder -- Table Builder enables you to create, design, and administer tables and forms visually from a single user interface.
Exploring Table Builder -- Learn about Table Builder features that enable you to design tables, forms, and flows visually using a single user interface.
Accessing Form Builder -- Form Builder is an application that is accessed most often through Table Builder on the Forms tab. You can also access Form Builder through the ServiceNow AI Platform and the Related Links section of any table.
Table Builder workflow and navigation -- You can start using Table Builder to manage your data tables, forms, or flows by reviewing this high-level workflow.
Domain separation and Table Builder -- Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Using an application scope with Table Builder -- Selecting an application from the application scope list in Table Builder enables you to customize form views for the users of the selected application in the ServiceNow AI Platform.
Using Table Builder -- Use Table Builder, to design and customize tables, forms, and form elements for users from a single interface without needing to navigate between existing ServiceNow AI Platform tools.
Data in Table Builder -- With Table Builder, you can modify the table properties and manage the fields that are available for a selected data table.
Spreadsheet view in Table Builder -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Add a new data record -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Edit individual data records -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Sort your data records -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Show matching data records -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Filter your data records -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Edit column field properties -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Add new columns -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Duplicate an existing column -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Reorder columns -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Set column visibility -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Pin columns -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Delete columns -- Use Spreadsheet view in Table Builder to work with your application data records and data structure in a spreadsheet format.
Fields view in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Add a table column in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Delete a table column in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Change a column label in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Change a column type in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Edit field properties in Table Builder -- Modify the table properties and manage the table fields by using the default Fields view on the Data tab in Table Builder.
Edit table properties in Table Builder -- Change table properties such as the table label or other settings so that you can make a table extensible or add record numbers by using Table Builder.
Forms in Table Builder -- On the Forms tab in Table Builder, you can visually create, configure, and customize the different form views for your users using the form editor. The views that you define contain the elements that appear when a user opens that form or list.
Choose a form view in Table Builder -- Choose existing views, duplicate views, or create entirely new views for form users in Table Builder.
Add formatters in Table Builder -- You can add form elements that display non-field information to users by adding a formatter in Table Builder. For example, you may want to display a Comments field where users can add comments to a displayed form.
Add embedded lists in Table Builder -- Add an embedded list using Table Builder to display data for a selected related list on your form. A related list shows the records in the tables that have relationships to the current record. For example, for a form view that references a Problem table, you might want to display a list of locations that are impacted by a selected problem.
Preview your form -- Previewing and saving your form in Table Builder.
Policies and rules in Table Builder -- Policies and rules define how information appears to users based on role and entries, as well as who can access tables and forms built in Table Builder.
Create a UI policy in Table Builder -- Policies and rules define how information appears to users based on role and entries, as well as who can access tables and forms built in Table Builder.
Modify a UI policy in Table Builder -- Policies and rules define how information appears to users based on role and entries, as well as who can access tables and forms built in Table Builder.
Flows in Table Builder -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Find a record-based flow -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Add a record-based flow -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Modify a record-based flow -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Delete a record-based flow -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Copy a record-based flow -- You can use the Workflow Studio functionality that is integrated within Table Builder to manage your table's record-based flows. You can manage these flows by using the Flows tab.
Table Builder reference -- Reference topics provide additional information about the form and table elements you can configure using Table Builder.
Formulas for column values in Table Builder -- You can use a predefined function and create a formula to calculate the value of a column without writing a script. Use a predefined function or create a nested formula by using the existing predefined functions to calculate the column value type.
Simple math functions -- You can use a predefined function and create a formula to calculate the value of a column without writing a script. Use a predefined function or create a nested formula by using the existing predefined functions to calculate the column value type.
String functions -- You can use a predefined function and create a formula to calculate the value of a column without writing a script. Use a predefined function or create a nested formula by using the existing predefined functions to calculate the column value type.
Date and time functions -- You can use a predefined function and create a formula to calculate the value of a column without writing a script. Use a predefined function or create a nested formula by using the existing predefined functions to calculate the column value type.
Logical functions -- You can use a predefined function and create a formula to calculate the value of a column without writing a script. Use a predefined function or create a nested formula by using the existing predefined functions to calculate the column value type.
Add a formula to a column in Table Builder -- Use a predefined function or create a formula to calculate a value for a column without writing a script in Table Builder. You can use two or more functions to create a formula according to your requirements.
Workspace Builder -- Workspace Builder enables you to quickly create and tailor custom workspaces where agents work on open records.
Explore -- Workspace Builder for App Engine is a streamlined, no-code environment that enables you to create a custom workspace from within App Engine Studio (AES) quickly and efficiently.
Accessing Workspace Builder -- You can access Workspace Builder in both ServiceNow Studio or App Engine Studio (AES).
Sample workspaces -- Workspace Builder provides a basic workspace that includes a home page, record pages, lists, an Analytics Overview, and other functions.
Parts of a workspace -- Every workspace has parts that enable workspace users to complete their tasks.
Layout -- Workspace Builder has a navigation panel, header, preview pane, and configuration panel to enable bulding custom workspaces.
Configure -- Install and configure Workspace Builder to enable users to build custom workspaces.
Use -- Create a workspace in Workspace Builder before customizing its settings, home page, record pages, lists, and analytics.
Add a workspace -- Create a workspace using Workspace Builder in ServiceNow Studio or App Engine Studio (AES). Workspaces provide agents, case managers, help desk professionals, and managers with tools to help answer customer questions and resolve customer problems.
Configure workspace settings -- Define workspace settings in Workspace Builder to control the basic functionality of the workspace, such as name and record page navigation.
Customize a home page -- Edit the home page for a workspace in Workspace Builder. Adjust what users see when first accessing the workspace, which is a dashboard.
Add a record page -- Configure a record page for a workspace in Workspace Builder. Use containers and components to guide a user through an experience. Each record page is linked to only one data table.
Create lists for a workspace -- Create list categories in Workspace Builder to add pages that list table records. You can add filter conditions and change columns to create variations on the list.
Enable analytics -- Enable the Analytics Overview for a workspace in Workspace Builder. The Analytics Overview enables users to track and analyze records and usage with dashboards, data visualizations, and insights on the instance.
Edit a workspace -- Edit a workspace in Workspace Builder to make customizations.
Reference -- Reference topics provide additional information about the lists and forms that you use to configure and administer Workspace Builder.
Components for home pages -- Several UI Builder components are available as elements to build home pages and contextual side panels in Workspace Builder. Workspace Builder helps you quickly create workspaces.
UI Builder -- UI Builder is a web user interface builder. Use UI Builder to build pages for App Engine Studio generated workspaces or custom web experiences using Next Experience Components and custom web components.
Exploring UI Builder -- Explore facets of UI Builder to set you up for creating pages quickly.
UI Builder quick start -- This quick start guides you through the process of creating your first page in UI Builder. Creating your first page is the first step in understanding how to build user interface pages for your workspace or custom portal experiences.
UI Builder tutorial -- Learn how to use the basics of UI Builder to create a page called My Tutorial.
UI Builder Learning Center -- Explore the UI Builder Learning Center for articles, videos, courses, and guided tours to help you get started and build knowledge. The Learning Center is a one-stop shop for learning fundamental features and basic guidelines in UI Builder.
Guided tours in UI Builder -- Learn about UI Builder guided tours, including how to use them to build your knowledge and practice using UI Builder.
Learn UI Builder by example -- Exploring common use cases can be a great way to learn how to use UI Builder. Consider performing each of the tasks in this section in the order presented.
Create a demo experience to explore UI Builder -- An experience in UI Builder is a collection of web pages for users to interact with an application. The experience includes routes, page variants, and the audience and conditions required for each variant, as well as experience settings.
Create a blank page -- After creating a demo experience, you can create a blank page that you can then build on to define what the experience provides to your users.
Create a record page using a template -- After you've created your demo experience, you can create a record page from a template. A record page shows data from a table.
Create a button that opens a modal -- After you've created your demo experience and added a blank page, you can edit the page variant as needed. For the sake of this demo, you can create a button and a modal, and configure the button to open the modal.
Define an audience for your variant -- An audience represents a group of users in your organization. You can define who can access this page variant by adding one or more predefined audiences.
Define conditions for your variant -- You can define conditions to determine when a page variant is shown. The conditions are based on setting an order, and declaring the criteria that must be met for the page variant to display.
Learn about domain separation -- Domain separation is supported for UI Builder . Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Working in UI Builder -- Get a full understanding of everything that you can do when creating a page for your workspace or custom portal experience in UI Builder.
Change the general settings in your workspace experience -- Change the general settings for your workspace experience in UI Builder to fit the needs of your organization. For example, you can modify the title, description, and path for your workspace experience.
Set up notifications in workspace utility settings -- Set up the advanced notification and search settings in your workspace experience so that you can control how your users see notifications and search options.
Configure UI Builder portal experiences -- You can change your UI Builder custom portal experience settings to affect how your users interact with your portal experience.
Change the general settings in your portal experience -- Change the general settings for your custom portal experience in UI Builder. For example, you can modify the title, description, and path for your portal experience.
View the brand and theme setting in your portal experience -- View the theme setting for your portal experience in UI Builder. The theme sets the visual style of the experience and provides a consistent look and feel across all pages.
Define UI experiences using app shells -- Understand what app shells are, what app shells are available for UI Builder, and why you would pick one over another.
Manage UI Builder pages and page variants -- Learn what a page is in UI Builder. Understand the building blocks of a UI Builder page, such as column layouts and components.
Create a page in UI Builder -- Create a page in UI Builder for a portal, workspace, or custom application so that you can build a web experience for your users.
Create a page from a template -- Use a template to create a page based on a pre-defined page template. A page template can help you create pages faster and keep pages consistent within an experience. Page templates may include components, data resources, and a layout.
Create a page from a legacy template -- Use legacy page templates to reuse a page definition, such as record or list page, for pages in your workspace or portal.
Edit a page -- Edit a page to change the page name, path, type, and parameters.
Enable the user criteria property -- Enable the user criteria property to configure access for users based on role, department, group, location, or company in UI Builder.
Test values in a page -- Add test values to your URL as a way to bring test data into a page.
Create a page variant -- A page variant in UI Builder is a variation of a page that exists at the same path that targets different audiences using user criteria.
Edit page variant settings -- Edit page variant settings to add additional criteria to determine when the page variant displays to users.
Control the conditions for a page variant -- Set the conditions and manage the criteria that determine when a page variant is displayed. UI Builder page variants enable you to create different versions of a page to tailor content for a specific audience.
Use pages across experiences -- Use pages created in one in experience in another without needing to rebuild the page.
Add shared pages to an experience -- Add a page from another experience so that users can access shared content without duplicating pages.
Responsive authoring -- Use responsive authoring to create UI Builder pages that adjust smoothly to different form factors (sizes), such as desktop, tablet, and mobile.
Adjusting component visibility in responsive authoring -- When creating pages with responsive authoring for different form factors, learn how to show or hide components by completing steps to hide an image at mobile size.
Configuring components for responsive authoring -- When creating pages with responsive authoring for different form factors, learn how adjusting some component configuration options can make pages look and work better at smaller sizes.
Adjust styles for responsive authoring -- When creating pages with responsive authoring for different form factors, learn how to change style options to increase the usability of the page at smaller sizes.
Adjust layout for responsive authoring -- When creating pages with responsive authoring for different form factors, learn how to adjust the layout to improve the look and feel of the page at smaller sizes.
Create a breakpoint for responsive authoring -- Learn how to create custom breakpoints for responsive authoring to control the look and feel of a page at different form factors.
Learn how to view and test your UI Builder experience -- Preview your experience in UI Builder to see how it looks and functions while building an experience. Previewing helps ensure that your experience works as expected, that the data resources are available, and that the layouts are set up correctly.
Using Flexbox layouts in UI Builder -- Create a Flexbox layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Create a Flexbox layout with the new layout system -- Create a Flexbox layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Create a Flexbox layout with the old layout system -- Create a Flexbox layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Using CSS Grid layouts to build a page -- Create a CSS Grid layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Create a CSS Grid layout with the new layout system -- Create a CSS Grid layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Create a CSS Grid layout with the old layout system -- Create a CSS Grid layout in UI Builder to build powerful pages so that you can customize with cascading style sheets (CSS) and can improve your performance.
Change the layout of a page created in Quebec or Rome -- Add and modify your layout design to change the way your page looks. Choose how components are displayed on a page through Cascading Style Sheets (CSS) web layout technologies, such as Flexbox and CSS Grid.
Learn components by example -- Follow these procedures to learn how components create the functionality you need in your UI Builder pages.
Add carousel badge item count -- How to create a dynamic carousel item count (displayed in the badge) where the items in the carousel are controlled by a repeater pulling its data from a data resource.
Create dynamic filtered card displays -- Create an interactive card layout to display records, add a dropdown to filter visible cards by name, and configure each card to open the full record in another UI Builder page when selected.
Create alert messages in UI Builder -- Learn how alert messages help you communicate feedback and status updates using both default and scripted approaches.
Create modals in UI Builder -- Use modals in UI Builder with components to provide alerts or calls to action for a user. UI Builder comes with modals to save time and effort.
Add modal to component -- Learn how to add a modal in UI Builder. A modal is a window that appears when you click a component. For example, a modal might display when a delete button component is clicked, prompting the user to confirm deleting a record.
Extend your UI experience with viewport components -- Viewports are specialized components that enable you to extend your experience without needing to own the parent page in UI Builder. You can work with viewports in three ways. You can add a viewport component or a viewport-enabled tab to a page, or add a viewport to the Contextual sidebar component.
Replace a tab with a viewport-enabled tab -- Convert a tab on a page to a viewport-enabled tab. Use viewport-enabled tabs to display third-party custom data, assign audiences, and create variants.
Create popovers in UI Builder -- Use popovers on a UI Builder page to overlay contextual information or functionality to help users complete tasks.
Add popover to a UI Builder page -- Use popovers on a UI Builder page to overlay contextual information or functionality to help users complete tasks.
Create modeless dialogs in UI Builder -- Use modeless dialogs on a UI Builder page to add a floating window that enables you to interact with both the window content and the page content below.
Add modeless dialog to a UI Builder page -- Learn how to add a modeless dialog in UI Builder. A modeless dialog is a floating window containing content above a page.
Add modeless dialog event to a UI Builder page -- Learn how to add and configure a modeless dialog event, such as open, close, or minimize in UI Builder. A modeless dialog is a floating window containing content above a page.
Manage actions in UI Builder pages -- Learn how to work with events so that you can add actions to components, pages, data resources, and declarative actions in UI Builder.
Define map events -- An event mapping in UI Builder is the process that enables you to map an event's payload or contextual values to the object or handler that acts on that event. The four event types are: component, page, data resource, and declarative action.
Configure an event handler manually -- Add an event handler to a page, component, data resource, or declarative action within UI Builder so that your user can trigger an action.
Bind events to add actions -- After you have created events, you can bind them to actions on your components, pages, data resources, and declarative actions.
Bind an event to a component -- Bind data elements within UI Builder so that you can add event actions to your components.
Bind an event to a page -- Use page event mappings to bind data elements within UI Builder so that you can add event actions to your page.
Bind an event to a data resource -- Assign event handlers within UI Builder to individual data resources on your page. When a data resource successfully fetches new data, it executes an event handler to take a user to the next step in a flow.
Link an event to another page -- Add a link to the destination event handler within UI Builder so that an event action can open another page. You can also configure the event handler to follow the App Route to the desired page.
UI interactions -- Trigger UI interactions directly from events in UI Builder, allowing you to link event-driven behavior to reusable interaction logic.
Create a UI interaction -- Create a UI interaction and attach it to a component event in UI Builder. UI interactions are reusable flows that combine UI, logic, and scripts into a single unit, including custom UI built with Component Builder, and can be triggered from any component event on a page.
Edit an existing UI interaction -- Edit or modify an existing UI interaction by inserting new steps, swapping or deleting events, removing steps, or updating step configurations in the diagram editor.
Duplicate a UI interaction -- Create an independent copy of an existing UI interaction to use as a starting point for a new interaction or to safely experiment with changes.
Delete a UI interaction -- Delete a UI interaction when it’s no longer needed or when you must replace it with a new version. Although UI interactions can be edited after creation, some foundational properties are intentionally locked to avoid data and runtime errors. In those cases, deletion might be required.
UI interaction toolbox steps -- Find details about UI interaction toolbox steps, organized by interaction type, with step descriptions and any available outgoing events. Steps are added to a UI interaction using the toolbox in the UI interaction editor. The available steps depend on the type you selected when you created the UI interaction, whether Generic, Form, or List.
Working with UI interaction demo data -- Demo UI interactions give you simple, ready‑made examples that demonstrate common UI interaction patterns. You can duplicate these samples to explore how interactions work, experiment safely, and use them as starting points when building your own experiences.
Duplicate a demo UI interaction -- Create a duplicate of a demo UI interaction example to work with a separate, editable copy.
View experience theme -- View the theme applied to your experience. The theme sets the visual style of the experience and provides a consistent look and feel across all pages.
Create custom style classes and rules -- Use style classes rules in UI Builder to apply custom visual styling to UI elements by referencing CSS classes.
Find and compare page changes -- UI Builder provides real-time collaboration tools and user presence indicators for more efficient and intuitive UI development.
How to use the Now Assist panel in UI Builder -- Use the Now Assist panel in UI Builder to request guidance, streamline page building, and better understand the content on your pages.
Advanced UI Builder -- UI Builder can be used by application developers with a variety of skill levels. We recommend developers with a high level of experience, sometimes referred to as pro-coders, perform the procedures in this section.
Configure components and repeaters (advanced feature) -- You can add and configure components as you build pages in UI Builder. You can also use repeaters to repeat components or multiple components with results from a data resource.
Add and configure components -- Learn how to add components to your page in UI Builder. A page is built by adding components.
Add repeaters to components -- In UI Builder, use repeaters to repeat one or more components with results from a data resource.
Optimize page loading performance (Advanced Feature) -- Performance settings enhances leading speeds and user engagement by displaying high-priority content first, making key components interactive sooner for a faster perceived performance.
Create custom controllers (Advanced feature) -- Build custom controllers to use across experiences. Easily connect reusable data, scripts, and events to your page and set up inputs, outputs, and events.
Connect data components -- Use the data binding modal to associate data exposed by local data resources to components on your UI Builder page.
Client state parameters -- Use client state parameters to bind values to component configurations. When the client state parameter's value changes, the component updates to use the new value.
Using client state parameters in UI Builder -- Create a simple counter by adding the stylized text component and two buttons to an experience page. Use a client state parameter to implement the functionality so that when the buttons are selected the count increases or decreases.
Update a component’s state using client state parameters -- Create and bind a client state parameter value to a component in UI Builder. By adding custom values to your components, these components can then be automatically updated through a script.
Define and bind client scripts to components -- Add and edit client scripts in UI Builder so that you can update the client state through events. You can bind these scripts to any component by using an event handler.
Multi-table data configuration -- Present data from multiple tables using components and control the layout and styling.
Work with the Entity View Action Mapper for UI Builder -- With UI Builder, you can use the Entity View Action Mapper (EVAM) application to standardize how the data sources in your components are displayed in your cards and lists.
Add an Entity View Action Mapper data resource to a page -- Add an Entity View Action Mapper (EVAM) data resource to your page in UI Builder so that you can standardize how the data sources in your components are displayed in your cards and lists.
Edit code with the Now Code Editor (advanced feature) -- Now Code Editor is a rich-text editor like interface that supports Cascading Style Sheets (CSS), Hypertext Markup Language (HTML), JavaScript, Extensible Markup Language (XML), and JavaScript Object Notation (JSON). Use Now Code Editor to modify UI configuration, data resource configuration, styles, events, client-side and server-side scripts in Next Experience UI Builder components.
Component Builder -- Learn how to use Component Builder to assemble reusable components for your UI Builder pages.
Testing and debugging applications -- Verify the application meets your business requirements. Your testing should cover record operations (such as create, read, update, and delete), user interface elements (such as views and UI policies), runtime operations (such as business rules), and event script actions.
Automated Test Framework (ATF) -- The Automated Test Framework (ATF) enables you to create and run automated tests to confirm that your instance works after making a change. For example, after an upgrade, during application development, or when deploying instance configurations with update sets. Review failed test results to identify the changes that caused the failure and the changes that you should review.
Exploring Automated Test Framework -- The Automated Test Framework helps you ensure the integrity of your instance by enabling the creation and execution of automated tests following any changes.
Getting started with the Automated Test Framework -- If you are new to the Automated Test Framework, read this overview to learn what the framework can do. Next, follow the tutorial to create and run a test that uses the most basic of ATF features. After you feel comfortable with the basics, explore more advanced features provided by the ATF.
Build and run your first automated test -- Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record.
Create new test -- Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record.
Add the first step to the new test -- Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record.
Add the third step to your test -- Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record.
Run your test -- Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record.
Next steps with the Automated Test Framework -- After you feel comfortable creating and running simple tests, explore the more advanced features of the Automated Test Framework.
Domain separation and Automated Test Framework -- Domain separation is supported in the Automated Test Framework. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Headless Browser for Automated Test Framework -- Improve your UI testing by automating the creation of browsers to process Automated Test Framework (ATF) User Interface (UI) tests. This feature is known as a headless browser, and helps you test UI functionality without having to manually open a browser to the Client Test Runner, which is what processes the UI tests in your local browser.
Headless Browser setup for Linux -- The ServiceNow Headless Browser for Automated Test Framework provides automation so you can skip having to manually open a browser during testing. The Headless Browser setup is available in both Linux and Microsoft Windows. This topic covers the setup for Linux.
Add secrets to Docker for Headless Browser setup in Linux -- Create a Docker secret, which stores the password of the ServiceNow user who will log into the instance to execute the tests. Docker Secrets is a feature of ServiceNow for securely storing the passwords that will be used in containers.
Set up instance for Headless Browser in Linux -- Step 5 in the Linux setup for the ServiceNow Headless Browser for ATF: Set up your instance so it can support the Headless Browser.
Verify Headless Browser procedures in Linux -- Step 7, the final step in the Linux setup for the ServiceNow Headless Browser for ATF: Verify that your Headless Browser setup procedures are successful.
Headless Browser setup for Microsoft Windows -- The ServiceNow Headless Browser for Automated Test Framework (ATF) provides automation so you can skip having to manually open a browser during testing. The Headless Browser setup is available in both Linux and Microsoft Windows. This topic covers the setup for Windows.
Add secrets to Docker for Headless Browser setup in Microsoft Windows -- Create a Docker secret that stores the password of the ServiceNow user who will log into the instance to execute the tests. Docker Secrets is a feature of ServiceNow for securely storing the passwords that will be used in containers.
Headless Browser system properties -- Below is a table of the properties you must have as you set up the ServiceNow Headless Browser for Automated Test Framework.
Headless Browser troubleshooting -- These tips can help you troubleshoot your Linux or Microsoft Windows setup of the ServiceNow Headless Browser for Automated Test Framework.
Add a template to an automated test -- With test templates you can add a predefined list of steps to a test. Any list of steps that follows a set pattern makes a good candidate for a template.
Edit automated test step order -- By default, steps execute in the order in which you created them. You can change this order by editing the Execution Order field.
Copy automated test -- Copy an existing test, which you can then re-name and modify.
Run an automated test -- After creating an automated test, run it on a non-production instance.
Implementing breakpoints -- Breakpoints allow you to pause your test at any step of a test run in order to troubleshoot and test authoring.
View test results and automated test results -- View test results from completed test and test suite runs. Carefully consider the results of automated test runs and perform any corrective actions required to resolve any revealed issues.
Example client errors -- Identify client errors and resolve them in client-side scripts.
UI test steps -- Test user interfaces by mimicking user actions and interacting with the visible components of a page.
Custom UI test steps -- Test customized user interfaces such as UI pages and UI macros by retrieving their HTML and JavaScript page components and identifying the test actions they support.
Page Inspector -- Identify the HTML and JavaScript page components in your user interfaces that are available for custom UI testing. Enable automated testing by ensuring that your user interfaces only contain testable page components.
Inspect different page types -- Inspect and troubleshoot the functionality of different page types like UI Pages, Service Portal, Standard UI, and Custom URL using the Page Inspector.
Enable and use the page inspector -- Enable a developer setting to inspect UI pages that open within the platform. Use the Manual Page Inspector to inspect pages that open in a new tab, such as Service Portal pages.
Override component test actions -- Change the testing properties of a particular page component using HTML attributes that are specific to Automated Test Framework.
Using sn-atf-class attribute -- Change the testing properties of a particular page component using HTML attributes that are specific to Automated Test Framework.
Reference and record picker -- Change the testing properties of a particular page component using HTML attributes that are specific to Automated Test Framework.
Override component data type -- Use the sn-atf-data-type and sn-atf-data-type-params attributes to override the type of field displayed in a Set Component Value test step.
Select2 functionalities in ATF -- Use the Select2 component to search and select your option from a drop-down menu easily.
Working with client test runners -- If an automated test includes steps that involve a form or any other user-interface (UI) element, it runs those steps in a browser tab or window called a test runner or client test runner.
Pick a browser -- If the test or test suite you are running contains steps that work with a form (any step involving a UI), or any other UI test step element (such as Automated Service Catalog test steps), work with the Pick a Browser dialog.
Cloud Runner browser -- If you are running a test or a test suite, select the Cloud Runner browser option to run your tests in a cloud browser.
Server test steps -- Test business logic and background processes by performing operations on the server.
REST test steps -- Test custom inbound web services and backwards compatibility by making REST calls.
Attachment test steps -- Test an attachment-dependent business rule by uploading an attachment either from a form or from a server-side API call. For example, you can have a business rule that doesn't let you close an incident without an attachment such as a screenshot.
List UI actions test steps -- Select a UI action from a list to perform different actions on a list or a related list.
Parameterized tests -- Run a test multiple times with different test data for each run. Create parameters to store test data for each test run.
Allowed client errors -- Add known client errors to the allowed client errors list to allow tests and steps to continue running when a specific error occurs. Set the report level to specify what the Automated Test Framework does when the error occurs in future tests.
Copy an automated test suite -- Reduce time when creating tests by copying an entire test suite. Rename and modify the test suite after copying. The Copy Test Suite button on the Test Suite form copies all the nested tests and child test suites within the text suite.
Add tests to a suite with a filter -- Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites.
Run a scheduled test suite using a script -- Execute a scheduled UI test suite immediately using a script without having to wait for the scheduled time. You can use this method while trying to automate the process of running a test.
Auto-generate ATF tests -- Auto-generate ATF tests by selecting the auto-generate option either from the Auto-generate Tests module or Tests/Suites modules.
Reusable tests -- Leverage reusable tests to simplify test maintenance and streamline the management of large tests and test suites. Reusable tests reduce redundancy, ensuring consistent and reliable test execution across your system.
Create a reusable test -- Create a reusable test to avoid redundancy, ensuring better test maintenance and reliable test execution across the instance.
Mutually exclusive tests -- Prevent conflicting tests from running in parallel by marking them as mutually exclusive. For example, when the system identifies tests that modify the same record, the system makes these tests mutually exclusive. You can also manually mark tests as mutually exclusive.
Quick start tests -- Copy and customize quick start tests provided by the ServiceNow AI Platform to validate that your instance works after you make any configuration changes. For example, if you apply an upgrade or develop an application.
Available quick start tests by application or feature -- Validate that your instance still works after you make any configuration change such as apply an upgrade or develop an application. Copy and customize the ServiceNow -provided quick start tests to pass when using your instance-specific data.
Parallel testing -- Reduce test design time by running multiple tests and test suites in parallel. Design tests to run in parallel by avoiding resource conflicts and data dependencies.
Accelerate ATF tests failure resolution -- Resolve ATF test failures faster using the actionable support provided by the new ATF failure insights feature. You can achieve it by accessing the Find changes since last successful run related link.
Metadata exception list -- The following list of tables are not supported by the ATF tests failure resolution feature.
Performance profiling -- Performance profiling allows you to do performance testing on your instances.
Administering the Automated Test Framework (ATF) -- Enable or disable the Automated Test Framework, modify retention policies, move tests between instances, control user access to the Automated Test Framework, and create custom test step configurations and step environments.
Creating custom test step configurations -- Step configuration records (or step configs) define how each step type behaves. You can create new step configurations that define custom steps that run on the server.
Create custom step configuration -- Create a custom step configuration that can form the basis of new steps that run on the server.
Testing Configurable Workspace components -- Simplify test creation by directly interacting with components on most Configurable Workspace pages via the Page Inspector.
Modify data retention policy for ATF test results -- Modify the Auto Flush data retention policy, which designates how long the system retains data, and referencing data, for test and test suite results. You can change the frequency of flushing for the sys_atf_test_result or sys_atf_test_suite_result base tables. This setting controls how far back in time test result data is available.
Manage test client runners policies -- Modify how often active client test runners report in to the system and how long the system retains records for inactive client test runners.
Create an auth profile -- Create basic auth profiles to specify basic authentication credentials for Send Request - Inbound test steps.
Filter REST request and response headers -- You can add a list of REST request and response headers that are not to be saved in step-result records. You can filter headers that might contain authentication credentials or other sensitive information. The phrase "Header redacted for security" is saved instead.
Optimizing automatic test performance -- You can troubleshoot automatic test performance by inspecting system transaction log records and potentially shorten execution time by adjusting how often automatic tests capture screenshots.
Managing automatic test screenshot settings -- Capturing many screenshots can impair test performance. You can control which types of screenshots the system captures to minimize this effect.
Configure system property screenshot capture -- Capturing many screenshots can impair test performance. You can control which types of screenshots the system captures to minimize this effect.
Configure test-runner screenshot capture -- Capturing many screenshots can impair test performance. You can control which types of screenshots the system captures to minimize this effect.
View transaction data for automated test results -- To help troubleshoot performance issues with automatic tests, you can inspect related records from the transactions log entry [syslog_transaction] table.
Reusable Tests category -- Create reusable test components that can be incorporated into various other tests (regular or reusable test), minimizing redundant test code and enhancing test maintainability.
Generate Inbound Email -- Use Automated Test Framework (ATF) to test email notifications, outbound email flows, and inbound email responses.
Generate Inbound Reply email -- Use Automated Test Framework (ATF) to test email notifications, outbound email flows, and inbound email responses.
Generate Random String -- Use Automated Test Framework (ATF) to test email notifications, outbound email flows, and inbound email responses.
Server category -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Create a User -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Impersonate -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Search for a Catalog Item -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Record Query -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Record Insert -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Record Update -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Record Delete -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Record Validation -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Run Server Side Script -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Replay Request Item -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Log -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Add Attachments to Existing Record -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Checkout Shopping Cart -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
Custom Scripted StepConfig -- Perform server-side operations. For example, query and update a record, impersonate a user, or run a server-side script.
UI category -- Validate the functionality of the UI actions.
Tables excluded from rollback -- The Automated Test Framework tracks data created by running tests and rolls back changes after testing. The system excludes certain tables from being tracked during testing.
Tests -- The Tests module opens the Test table. From here, you can add, edit, and run tests. By opening an individual test record, you can view and edit the steps comprising that test.
Test record form -- In the Test record form, you view and edit values of fields for the test record.
Suites -- The Suites module opens the Test Suites table. You can create, edit, and run test suites from this table.
Test suite form -- The Test Suite form contains information about one test suite.
Test results -- Each time you run a test, the automated test framework creates a record of the test results. Use the Test Results module to view details about the results of individual tests and individual steps within a test. If the test generated screenshots, they appear as attachments on the test results record.
Test results record -- A Test Results record contains detailed results information about one test execution. Client Error Details and Failure Details sections appear when a test fails due to error conditions, and include detailed error information you can use for troubleshooting purposes.
Step results record -- The Step Results record contains information about one step in a test result. You access specific step results from the Step Results related list in the Test Results record.
Test logs record -- The Test Results Item (test log) record contains console logging and test execution information.
Suite results -- The Suites Results module opens the Suites Results table.
Test suite results record -- The Test Suite Results record displays information about the results of one execution of one test suite.
Test suite results examples -- Examples of relationship terms and how aggregated results roll up for test suites.
Suite schedules -- Open the Suites Schedules table. You can drill down to see details about the results of individual schedules or create a new schedule.
Suite schedule record -- The Suite Results record displays information about one test suite schedule.
Scheduled suite run record -- A Scheduled Suite Run record associates a Suite Schedule record with a Test Suite.
Run -- Start a client test runner and view information about test runners and test runs.
Client test runner -- The Client Test Runner opens a browser window or tab for running manually-started client automated tests.
Scheduled client test runner -- The Scheduled Client Test Run opens a browser window for running scheduled client automated tests.
Active manual test runners -- View the client test runners table filtered to show only those runners available to run manually-started tests.
Active scheduled test runners -- View the client test runners table filtered to show only those runners available to run tests to be started by a schedule.
Waiting/running test runs -- The Waiting/Running Test Run module opens a list of records showing the tests waiting to be run.
Waiting/running suite runs -- The Waiting/Running Suite Runs module opens a list of records showing the test suites waiting to be run.
Allowed client error records -- Review the list of existing Allowed Client Error [sys_atf_whitelist] records to see which client errors produce warnings and which are ignored. Modify existing Allowed Client Error records as needed or create new ones.
Reported client errors -- The Reported Client Error module lists test logs across all tests that are client errors and have failed. You can review individual test log records, and allowed client errors as needed to prevent them from adversely impacting future test executions.
Retrieve an incident using REST-Inbound -- The Get Newly Created Resource via REST API Test test is provided with the Automated Test Framework, and uses the REST - Inbound and assert steps.
Step execution scripts -- In a step configuration record, the step execution script field determines what a step with this configuration does when it runs.
Step description generation script -- In a step configuration record, the step description generation script field determines the step description that the system generates when a step of this type is added to a test.
Add output variables to scripted steps -- Execute the following steps to add additional outputs in Run Server Side Script and Custom Scripted StepConfig test steps.
Step configuration categories -- The Step Configuration Categories module opens a list of records specifying the step categories on the Add Step dialog. From this module, you can add, delete, and edit these categories.
Test step config category form -- On the Test Step Config Category form, you specify a retention policy for a set of records on a given test results table.
Table cleanup -- The Table Cleanup module opens a list of records specifying the retention policies for test result and test suite result tables and the records within them. From this module, you can view and modify these policies.
Autoflush form -- On the Auto Flush form, you specify a retention policy for a set of records on a given test results table.
Step environments -- A test step environment specifies where the step executes (for example, server versus browser). In this release, custom step configs can use only the Server-Independent environment.
Performance Analyzer -- The ServiceNow Performance Analyzer application enables you to access page load time data, trends, and waterfall visualizations directly from your instance. It also helps you to identify page performance issues and bottlenecks in UX framework pages independently.
Explore -- Learn about Performance Analyzer concepts and features.
Configure -- Configure Performance Analyzer environment and access.
Test applications -- Get information on how to test applications with Performance Analyzer.
Get metrics by duration -- Filter metrics in the Performance Analyzer by duration from the last fifteen minutes to the last seven days.
Get page route metrics -- Filter metrics for an application by page route in the Performance Analyzer.
Get interaction metrics -- Filter metrics for an application's page route by interaction in the Performance Analyzer.
Reference -- Get additional information about Performance Analyzer.
Get help with Performance Analyzer -- To get help with Performance Analyzer, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company.
Deploying applications -- Deliver your application to users by publishing it to a live production environment.
ReleaseOps -- ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production.
Explore -- ServiceNow ReleaseOps is a solution to problem of deploying changes, customizations, and custom apps on the ServiceNow AI Platform. By automating the deployment process, ReleaseOps helps to increase the predictability and reliability of deployments, while also reducing the risk of releasing unwanted changes to production.
Pipelines -- A pipeline is the flow of a deployment in ReleaseOps. A pipeline's flow is defined within playbooks, which enables you to customize as needed.
Releases -- Scheduled and on-demand releases are how changes are deployed to target instances with ReleaseOps. Releases can contain one or more deployment requests.
Deployment requests -- Deployment requests contain one or more update sets, and are contained in a release.
Deployment analyzer -- The deployment analyzer reviews the update set in your release against rules to verify compliance with customizable rules.
Runbook tasks -- Learn about how runbook tasks enable flexibility in ReleaseOps deployments, without needing to customize playbooks each time.
Configure -- Configure ReleaseOps to move changes from development to testing to production.
Install ReleaseOps -- Install ReleaseOps from the ServiceNow Store for the first time.
Guided setup -- Guided setup helps to make the initial configuration of ReleaseOps easier. Follow the steps in guided setup to begin using ReleaseOps quickly.
Manual setup -- Complete ReleaseOps manual setup to configure a new ReleaseOps ecosystem using the sample pipelines and playbooks.
Configure multi-instance management -- Manage the multi-instance configurations to enable access across instances in your ReleaseOps ecosystem.
Create a custom pipeline -- Create a custom pipeline to move changes from your development environment to production (or your target instance) by duplicating one of the ReleaseOps sample playbooks.
Example: Create an assessment playbook -- Create a custom pipeline to move changes from your development environment to production (or your target instance) by duplicating one of the ReleaseOps sample playbooks.
Attach an update set to an existing deployment request -- If you want to attach multiple update sets to a deployment request, you can attach an update set to an existing deployment request on the Deploy an update set form.
Create a release -- Specify the details for your release, including the target instance that the changes will be deployed to and when the release should occur.
Create a runbook task -- Create a runbook task to pause deployment and define the steps required to proceed.
Reconcile a deployment task -- Reconcile a deployment task to enable a deployment request to move to the next stage in deployment.
Reference -- Review information about deployment and release states.
Glossary -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
deployment analyzer -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
deployment request -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
deployment request update set -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
deployment task -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
pipeline -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
release -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
update set -- Before getting started with ReleaseOps, it's important to understand some key concepts used in the application.
Deployment request states -- A deployment request might be in one of several different states during the release process.
Release states -- A release might be in one of several different states during the release process.
Release form -- Create a release for the deployment requests to be deployed to target instances.
Deployment Request form -- Create a deployment request for the update sets to be deployed to target instances.
Deployment analyzer rules -- The deployment analyzer contains five rules that are included by default with ReleaseOps.
System update sets -- An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.
Explore -- An update set is a group of configuration changes that can be moved from one instance to another. Update sets enable developers to create functionality on a non-production instance, and promote the changes to another instance for testing or deployment.
Configure -- Configure your instance with tracked app installations or merge update sets into a single update set.
Application installation tracking -- You can add specific applications or versions as an app installation and configure to track them in an update set.
Overwrite customizations during an upgrade -- Specify which customized objects you want to replace during the next upgrade. By default, the upgrade process skips changes to customized objects.
Merge update sets -- Merge multiple update sets into a single update set.
Save an update set as a local XML file -- Administrators can export an update set as an XML file to save a specific version of an application or set of changes.
Transfers -- When an update set is completed, you can transfer it between instances to move customizations from development, through testing, and into production.
Navigation between records -- Navigate between a customer update record and the customized object or the application file for the object.
Compare local update sets -- Administrators can preview local and remote (retrieved) update sets and compare the sets with one another to resolve conflicting changes.
Preview a remote update set -- Previewing checks a retrieved update set against the local instance to find issues. Resolve all problems before committing the update set.
Review a preview record for an update set -- Previewing checks a retrieved update set against the local instance to find issues. Resolve all problems before committing the update set.
Resolve a preview problem in an update set -- Previewing checks a retrieved update set against the local instance to find issues. Resolve all problems before committing the update set.
Commit an update set -- After resolving any issues from previewing, commit the update set to apply all changes and generate a local copy with records of each update.
Back out an update set -- You can back out changes to existing records for any committed update set.
Mark an update set complete -- When you have completed the customizations and compared local update sets to resolve conflicts, mark the update set as Complete.
Working with batched update sets -- Batched update sets enable you to group update sets together so you can preview and commit them in bulk.
Create a batch update set -- You include an update set in a batch by specifying another update set as its parent.
Administer your apps -- The system offers several ways to manage applications. You must have the admin role to perform these procedures.
Application sharing -- Administrators can share applications that are complete and are ready for use on other instances.
ServiceNow application repository -- After you develop and test a custom application, you can make the application available to company instances by publishing it to the ServiceNow application repository.
Manage applications -- Learn how to manage the applications you publish to the ServiceNow application repository.
Manage customizations to applications -- You can manage your company's customizations for applications that belong to other organizations or a scoped ServiceNow plug-in.
Publish customizations to an application repository -- After you have designed, developed, and successfully tested your customizations to a store application or a scoped plugin, you can publish it to the ServiceNow application repository to share it to other instances in your company.
Convert custom applications to upgrade from the application repository -- When your applications are placed in the Custom Applications table [sys_app], you can't upgrade them directly through the Application Repository. This procedure helps you do a one-time conversion when you want to migrate deploying your applications using the Application Repository.
Convert your installed applications to development mode -- Convert the installed applications that your company owns to development mode after you install an application onto a non-production instance to use for development or clone a production instance into a non-production instance for development. With this conversion, you enable newer versions of the application to be created, committed, and published.
Results post cloning for application customizations -- The results to expect post cloning for application customization display the expected behaviors based on the state of the application, and the actions to recover your application customizations.
Application Repository for self-hosted, air-gapped customers -- This application feature enables self-hosted customers to use their own internal application repository just as cloud customers do. These customers don’t install the Application Repository via the ServiceNow Store; they use an alternative method.
Installing the Application Repository store app on an air-gapped instance -- Because self-hosted, air-gapped customers don't allow their instances to communicate with external networks, they don’t install the Application Repository directly from the ServiceNow Store. These customers should use the following procedure instead.
Publish an application to an Update Set -- Publishing an application creates an update set containing the current version of all application configuration records.
Queued Application Operations -- CICD APIs that must obtain the update instance wide lock / mutex to perform the requested operations are queued instead of being rejected when the update instance wide lock / mutex is occupied by the other operations.
Custom licensing for ISV applications -- Monitor the usage of ISV applications with Subscription Management. Create a definition for your store application with the metadata you want collected. After publishing the application with the definition to the store, Usage Analytics runs and aggregates your defined metrics.
Domain separation and Creator Workflow apps -- Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Maintaining your application -- Use your app builder tool to update and modify your application. Use your testing tool to verify that your application still functions properly.