Creator Studio apps and tables

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 streamlines app creation by using catalog templates and automatically generating tables to store requests. Each app created in Creator Studio typically uses the Request Task table by default, where each submitted request creates a new record. Administrators have the flexibility to change the associated table for an app, provided it extends from the Task table to maintain functionality.

    Show full answer Show less

    Parts of building an app

    • Form: Enables users to create records by filling out forms that trigger associated tasks or workflows on the ServiceNow AI Platform.
    • Automation: Contains playbooks—automated processes with limited actions—to update records and complete tasks across multiple activities.
    • Workspace list configurations and record details: Provides a workspace to view and interact with requests using standard or customizable filtered lists, allowing visualization of how records will appear.

    Administrators can create catalog templates to guide form building, simplifying the app development process.

    Handling requests and tables

    Every Creator Studio app automatically creates a table that stores all opened request records. By default, these tables extend the Request Task table, which itself extends the Task table, inheriting their columns and business logic. This inheritance is essential for automations to function correctly. If an admin changes the associated table of an app to one that does not extend Request Task, automations will not work.

    The Request type field on the Request Task table (or its extensions) defines the form associated with each request. Modifying this field requires administrative roles (sncreatorstudio.configurationadmin or sncreatorstudio.taskadmin).

    Administrative details

    Each app built in Creator Studio adds a record in the Request App Config table, specifying the table the app uses. The naming convention for the tables follows the format scoperequest (e.g., xsnc0203request). Admins can change the associated table for an app through this configuration.

    Key terminology

    Record: A record represents one request submitted through an app, corresponding to a row in the app's Request Task or associated table.

    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.

    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 associated app for a table, but it should still extend the Task table.
    Note:
    • If an app's associated table is changed to one that doesn't extend the Request Task table, automations won't work.
    • You can change the Request type field, which specifies the form, on the Request Task table or a table that extends Request Task. To do so, you must be an admin or have the sn_creatorstudio.configuration_admin or sn_creatorstudio.task_admin role.

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