Creator Studio apps and tables

  • Release version: Yokohama
  • Updated June 16, 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 streamlines app creation using catalog templates and manages requests through tables that extend the Request Task table by default. This structure supports automated workflows and task tracking within the ServiceNow AI Platform, providing flexibility for admins to customize underlying tables while maintaining core functionality.

    Show full answer Show less

    Parts of building an app

    • Form: Used to create records that initiate tasks or workflows on the ServiceNow AI Platform.
    • Automation: Includes playbooks that automate updates and task completions across multiple activities with limited actions.
    • Workspace list configurations and record details: Workspace setups display requests with customizable filtered lists; selecting a record allows interaction and preview within Creator Studio.

    Admins can create catalog templates to guide form building, enhancing consistency and efficiency.

    Where requests from the apps go

    Each Creator Studio app automatically generates a table where submitted requests are stored as records. By default, these tables extend the Request Task table, which in turn extends the Task table. This inheritance ensures that records include necessary columns and business logic for workflow automation.

    Changing an app's underlying table is possible but should retain extension of the Task table to preserve automation functionality. If the base table does not extend Request Task, automations will not function.

    For administrators, each app creates a record in the Request App Config table that specifies the table in use. Table names follow a standardized format indicating the app scope.

    Key outcomes

    • Apps built in Creator Studio efficiently manage requests via standardized tables supporting automation and workflow integration.
    • Forms and automations within apps enable streamlined task creation and completion across the ServiceNow AI Platform.
    • Customizable workspace lists and record interactions allow users to view and manage requests effectively.
    • Admins maintain control over app configurations and underlying tables to tailor functionality while preserving core system capabilities.

    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.