App Engine Studio

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.

Replace manual work by adding logic and automation to your app in App Engine Studio (AES).

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 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 automation for decisions in App Engine Studio (AES). The automation decouples decision logic from code by enabling you to create and manage decision rules.

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.

Add a mobile experience, or interface, to enable users to access your application from a ServiceNow native mobile app.

Build notifications in App Engine Studio (AES) to create automated emails for events using templates or custom messages.

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.

Control who is permitted to use or edit your application by configuring roles in App Engine Studio (AES).

Add a standard catalog item to your application in App Engine Studio (AES) so users can submit requests for services and offerings.

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.

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.

Meet the business needs of your organization by building custom applications in App Engine Studio (AES).

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).

In App Engine Studio (AES), you can add or remove users and groups to be collaborators on an application.

As you work through the App Engine Studio (AES) guided setup, you must perform different configuration tasks.

App Engine development tools, such as App Engine Studio, offer an excellent alternative to customizing existing applications on the ServiceNow AI Platform.

Create a custom role for your application in App Engine Studio (AES).

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.

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.

Use a previously created role for your application in App Engine Studio (AES).

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.

ServiceNow provides citizen developers with several quick training modules for getting started building low-code apps in App Engine Studio (AES).

Use the following guidelines to help you transition from using App Engine Studio to Build Agent.

Learn about terms and concepts that are unique to App Engine Studio (AES).

Install the App Engine Studio (AES) product to ensure you get all the dependencies, integrations, and tools, such as templates and builders.

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.

You should install App Engine Studio (AES) on all ServiceNow instances where users will develop applications.

App Engine Studio (AES) provides instant access to several tools available in the ServiceNow AI Platform development suite.

Build Agent is the agentic development experience on the ServiceNow AI Platform. Migrate your applications from App Engine Studio to Build Agent to expand your app's capabilities and take advantage of the agentic developer experience.

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.

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.

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 .

Reference topics provide additional information about the lists and forms that you use to configure and administer App Engine Studio (AES).

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.

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.

App developers working in App Engine Studio (AES) can manage their data repository in numerous ways.

Learn about the App Engine Studio (AES) user interface.

App Engine Studio (AES) and Build Agent differ across interface, artifact scope, scripting access, application scope, and governance. Use this feature comparison to understand what changes when you migrate to Build Agent.

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.

Learn about the differences between App Engine and App Engine Studio.

Specify which users and groups have access to predefined and custom templates in App Engine Studio (AES).

Create a record producer to start building user experiences for the employee travel request application.

Configure the record producer so that it contains the necessary questions for employee travel requests.

Configure a table to capture the necessary data for your application.

Automate the workflow for the employee travel request application by creating a flow.

When you're ready to start building your application, begin creating your application in App Engine Studio.

Build a decision table for the employee travel request application that determines which regional head to route travel requests to.

Create a table to store the data for your application.

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 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.

Plan out your application before building it in App Engine Studio to streamline the development process.

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.

Share data between tables to avoid data duplication.

Verify that your application works as intended before publishing by testing the application experience and flow.

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).

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.

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.

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 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.

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.

App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance.

Build an application in App Engine Studio (AES) using the Expense Pre-Approval template to create, track, and manage planned expenses in your organization.

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.

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.

If an existing automation template doesn't fit your application goal, define custom automation in App Engine Studio (AES) by building a new flow.

App developers using App Engine Studio (AES) can create versions and branches in their Git repositories.

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.

If you have the appropriate permissions, you can remove an application from App Engine Studio (AES).

Delete an experience, such as a portal or record producer form, that you no longer need within App Engine Studio (AES).

Delete a role that you no longer need in App Engine Studio (AES).

Build an application in App Engine Studio (AES) using the Document Approval template to manage the approval of documents in your organization.

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.

Use Table Builder to modify data tables used in your application.

To update or change an existing decision for an app built in App Engine Studio (AES), edit it in Workflow Studio.

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.

To update or change an existing flow for an app you built in App Engine Studio (AES), edit it.

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.

To update or change an existing process for an app built in App Engine Studio (AES), edit it in Playbooks.

Control the application permissions for a role in App Engine Studio (AES).

Build an application in App Engine Studio (AES) using the Emergency Alert template to manage communications and track essential resources during an emergency.

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.

Build an application in App Engine Studio (AES) using the Event Registration template to manage scheduling, booking, and registration for company events.

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.

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.

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.

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.

Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles.

Build an application in App Engine Studio (AES) using the Inventory Tracker template to track the status of inventory and assets.

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.

Improve the effectiveness of your custom template by updating its contents or properties in App Engine Studio (AES).

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.

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.

A mobile experience enables users to access your application from a ServiceNow native mobile app.

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.

Create tables from a PDF form using the PDF extractor tool in App Engine Studio.

Build an application in App Engine Studio (AES) using the Performance Review template to automate scheduling, notifications, and feedback for performance reviews.

A portal is a site where users inside of your organization can find information, submit requests, and complete business tasks.

See what an application experience built in App Engine Studio (AES) looks like to your users by previewing it in a browser.

You can publish a custom application from App Engine Studio (AES) when linked to source control.

You can publish a custom template that is built from scratch or from an existing application using App Engine Studio (AES).

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.

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.

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.

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.

Build an application in App Engine Studio (AES) using the Service Request Management template to create, track, and manage service requests in your organization.

Customize the set of development collaborators you list in App Engine Studio (AES) using Guided Setup.

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 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.

You can edit a Git repository's integration with App Engine Studio (AES) to change the network protocol selection, credentials or other field entries.

Import an app or app customization from a source control repository into App Engine Studio (AES) to continue developing it on this instance.

Linking an application or application-customization to source control allows application developers to manage changes in App Engine Studio (AES) from a Git repository.

App developers can apply or delete stashed changes from App Engine Studio (AES).

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.

The source control integration primarily supports operations from App Engine Studio (AES), but can also support some operations directly from the Git repository.

App developers can select the app file version to use when applying remote or stashed changes in App Engine Studio (AES).

App developers can remove and save changes locally to apply them later in App Engine Studio (AES).

App developers can view the commit history of apps linked to a source control repository in App Engine Studio (AES).

Create a new table by extending an existing table, and then using a Microsoft Excel spreadsheet import to update or customize it.

Create new tables directly from a Microsoft Excel spreadsheet import.

Use a Microsoft Excel spreadsheet import to update an existing application table.

Upload a Microsoft Excel spreadsheet and use it to create your application data model.

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.

Developers can remove and save changes locally to apply them later, and manage stashed changes from App Engine Studio (AES).

Start the process of getting the application you built in App Engine Studio (AES) published by submitting it for administrator review.

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.

Build an application in App Engine Studio (AES) using the Team Contacts template to manage contact information for the people in your organization.

Use an application template to create an application in App Engine Studio (AES) with preconfigured data, experience, logic and automation, and security.

Build an application in App Engine Studio (AES) using the Time Off Requests template to schedule employee vacations and time-off.

Learn how to identify and fix your app when unsupported features or metadata stop the template creation process in App Engine Studio (AES).

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.

If you are currently running a family release (Brazil, 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.

Add data tables and records to your application by uploading a Microsoft Excel spreadsheet.

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.

Add a data table to your application from an existing table that you or someone else previously created or from scratch.

Use a pre-built flow to quickly automate manual work in the app you're building in App Engine Studio (AES).

Developers using App Engine Studio (AES) can pull and commit changes in their Git repository.