Creator Studio apps and tables
Summarize
Summary of Creator Studio apps and tables
Creator Studio simplifies the app creation process through catalog templates, allowing ServiceNow users to streamline app development. Each app defaults to using the Request Task table to manage requests, but admins can customize the associated tables as needed.
Show less
Key Features
- Parts of an App: Apps can include forms, automation, and workspace configurations.
- Forms: When filled, forms create records tied to tasks or workflows on the ServiceNow platform.
- Automation: Contains playbooks for automated processes to update records and complete tasks.
- Workspace Configurations: Allows viewing and interacting with requests in customizable filtered lists.
Key Outcomes
Every app automatically generates a corresponding table for all opened records, which typically extends from the Request Task table. Admins can modify the associated table, but it must extend from the Task table for automations to function correctly. Records are generated for each request and are stored as rows in the app's designated table. Admins are responsible for managing these configurations, ensuring seamless operation within the ServiceNow environment.
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.
- 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
| 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
- 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.
- 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.