Creator Studio uses catalog templates to streamline the app creation process. Apps use the Task table, generating a new row for each submitted request.

Summary: After reading this section, you'll understand:
  • The parts that go into building an app
  • Where requests from the apps go
  • How tables are used to store requests

Parts of building an app

Apps contain one or all of the following parts.
Table 1. Parts of an app
Functionality Description
Form When filled out, forms create a record with an associated task or workflow on the ServiceNow AI Platform.
Automation Automation contains playbooks, or automated processes with limited actions that enable users to update records and complete tasks across multiple activities.
Form submission workspace Workspace that shows requests for the app built in Creator Studio, with standard and customizable filtered lists.

Your admin can create catalog templates to guide the process of building forms. For more information, see Working with forms in Creator Studio.

Where requests from the apps go

Every app in Creator Studio automatically creates a task table where all opened records go when people use the app. The tables that Creator Studio apps generate extend the Request Task table that comes with Creator Studio, which extends the Task table.

Extending a table means the new table inherits the parent (extended) table's columns, as well as its business logic. For more information on Task tables, see Working with the Task table.

For sys admin eyes only: Every app built in Creator Studio adds a record in the Request App Config table. The name of the table follows the format of scope_request, for example, x_snc_02_03_request.

Key term:
Record
A record is what the ServiceNow AI Platform generates for each request submitted through your app. Each record corresponds to a row in the app's Request Task table.