Creator Studio apps and tables

  • Release version: Yokohama
  • Updated August 11, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Creator Studio apps and tables

    Creator Studio simplifies app creation in ServiceNow by using catalog templates and a default data structure centered around the Request Task table. Each app automatically generates a table to store request records, enabling streamlined tracking and management of submitted requests within the ServiceNow AI Platform.

    Show full answer Show less

    Parts of building an app

    • Form: User interfaces that, when submitted, create records linked to tasks or workflows.
    • Automation: Playbooks that automate updates and task completions across multiple activities with limited actions.
    • Workspace list configurations and record details: Configurable views displaying requests, allowing interaction and previewing of records within Creator Studio.

    Admins can create catalog templates to guide form development, enhancing consistency and ease of use.

    Where requests from the apps go

    Each app generates a dedicated table to store request records. By default, these tables extend the Request Task table, which itself extends the Task table. This extension ensures that the new tables inherit essential columns and business logic, enabling automations to function properly.

    Admins can change the underlying table for an app, but it must extend Request Task to maintain automation capabilities. If changed to a table that does not extend Request Task, automations will not work.

    Every app also creates a record in the Request App Config table, which tracks the table associated with that app. Table names follow a standardized format such as scoperequest (e.g., xsnc0203request).

    Key concepts

    • Record: A row generated in the app’s Request Task or underlying table for each submitted request, representing a discrete task or workflow instance.

    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 underlying table for an app.

    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.
    Workspace list configurations and record details Workspace configuration that shows requests for the app built in Creator Studio, with standard and customizable filtered lists. Selecting a record in the List configurations section displays the record, which you can interact with in Creator Studio, enabling you to see how it will look.

    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 table where all opened records go when people use the app. By default, the tables that Creator Studio apps generate extend the Request Task table that comes with Creator Studio, which extends the Task table. Your admin may change the underlying app for a table, but it should still extend the Task table.
    Note:
    If an app's underlying table is changed to one that doesn't extend the Request Task table, automations won't work.

    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, which contains the table that the app uses. Your admin can change the table for an app, see Administering an app's underlying table for more information. 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 or underlying table.