Creator Studio

Admins have special privileges to approve and update tasks in Creator Studio that regular users can't.

Admins and App Engine admin can review and approve (or reject) people's requests to join an app's development in Creator Studio.

By now, your admin has set up Creator Studio, given you permission to build an app, and you've got a great idea for a request-fulfillment app! How should you think about using Creator Studio to create your app?

So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.

Admins need to install Creator Studio before it can be configured for users to start building apps.

Get started creating an app by specifying basic info for the app that you're building in Creator Studio.

Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production.

Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes.

Add as many forms as you need to create catalog items for your app. For example, you could have an office booking app with three different forms: one for requesting parking spaces, one for requesting a desk, and one for reserving conference rooms.

Create an automated playbook, which is a process that runs whenever a record is created or updated by the app's specified form.

You must add custom activities to the Creator Studio Activities table [sn_creatorstudio_activity] before users can add them to playbooks when building apps.

Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio.

Create custom filtered lists in the app submission workspace to view records that meet specific conditions. For example, if your app has multiple forms, you can create a list for each form by filtering on the record type.

Add a form to the app you just created. Forms contain questions that people respond to when submitting a service desk request.

Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running.

Admins can change the associated table for an app built in Creator Studio. That is, you can change the table that the app saves its requests to.

Admins can change the default table that apps built in Creator Studio save their requests to.

In Creator Studio, as an administrator or App Engine admin, you have the power to manage how people work together on projects.

As an admin, you can define custom activities, make them available in Creator Studio, and hide existing activities to help guide users when they add automation to apps.

As an admin, you can create custom templates and pre-configured questions to help streamline and guide users when they build apps in Creator Studio.

After users build apps in Creator Studio and you deploy them to production, as an admin, you are responsible for granting access to those apps to users.

Each deployed version of an app must have a version number and release notes, which helps administrators track app usage and changes.

Provide your organization's fulfillers with guidance when addressing records generated from the app by adding automated playbooks to it.

Think of your app as an online store that contains a catalog of items. To request something, a person needs to fill out a form. It’s your job to create and customize forms for every item in your catalog using Creator Studio.

Change the table associated with an app if you want one that differs from the default.

The records that your app creates when a form is completed are not automatically closed, and some notifications are not automatic and must be configured.

When you customize collaboration permissions, you can choose more granular actions and parts of the app that users can work with in Creator Studio.

Sometimes you need help with building out your app, and that’s OK! And sometimes other people need your help building their apps, which is great! This point is where collaboration comes into play.

When you activate the Creator Studio plugin, various components like tables and user roles are automatically installed.

App Engine development tools, such as Creator Studio, offer an excellent alternative to customizing existing applications on the ServiceNow AI Platform.

Install and configure ServiceNow Otto for Creator in Creator Studio.

You can install Pipelines and Deployments and configure a controller instance to deploy apps built in Creator Studio to production instances.

Have you ever dreamed of creating your own app? With Creator Studio, you might be closer than you think! The following links will send you to the sections in this guide that will walk you through the steps.

As a ServiceNow admin, you can create customized catalog templates in Service Catalog to guide users through adding forms in Creator Studio.

Admins can create pre-configured question sets that can be reused across multiple forms without being changed in Creator Studio.

Creator Studio helps you create your app by dividing it into smaller parts. Each does something special, and you work on them sequentially.

There are multiple steps to add custom activities for use in Creator Studio automations.

There are important differences between customizing and configuring ServiceNow applications. The ServiceNow platform is built to embrace customization and configuration but how you do so can have significant impacts on ServiceNow support, upgrading to future ServiceNow platform versions, and the functionality of the ServiceNow platform.

Hiding a catalog item for your app's form effectively makes the form inactive. Hidden forms are unavailable in both the app and the catalog it belongs to.

Create parallel processes in Creator Studio to make things happen in your app at the same time.

Delete an app to remove it from Creator Studio.

Delete a playbook to remove it from the app completely.

Deleting unpublished forms and questions from Creator Studio removes them completely from the ServiceNow AI Platform.

After you've tested your app's forms, playbooks, and workspace category on a non-production instance, for example a development instance, deploy it to a production instance so users can access it.

Domain separation is not supported in Creator Studio. This means that you can't separate data, processes, and administrative tasks into distinct groups, called domains, within the ServiceNow AI Platform.

Duplicate an existing playbook and make small changes to it, which may be faster than creating an entirely new automated playbook.

Make a form update based on how users answer a question using dynamic behavior. For example, if a user says they want a T-shirt for an event they're attending, you can make a T-shirt size field required.

Maybe you want to jazz up your app a bit, for example by giving it a new name, tweaking the description, or swapping in a new image. All it takes is just a few clicks in the settings! Let's dive into how you can do it, even if you're not a tech whiz.

Update a playbook to change its settings, or rearrange or remove tasks, to make it work for your app.

Edit form settings if you need to change its basic attributes, such as its associated image or attachments are allowed.

Forms help people ask for things they need, such as a new keyboard or permission to take time off. The default form that's added when you create an app in Creator Studio needs some changes to fit your needs. For example, you must add question labels to gather information about the request.

Make changes to the app's workspace category where fulfillers review submitted requests from apps built in Creator Studio to adjust how it appears. For example, you can rearrange columns in its lists and customize how the record generated by the request app looks.

Build apps using different types of questions on a form in Creator Studio.

Adjust how your form, which creates a catalog item, appears in Creator Studio using layout options.

You can edit the settings for an app's form in Creator Studio at any time. For example, to change who can access it.

So, you’ve built your app, and people are submitting requests through it, that’s great! However, you might be wondering where those requests go after they’re submitted. They live in lists in a workspace where fulfillers can work on submitted forms, which you can customize in Creator Studio to suit your needs.

To get help with Creator Studio, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company. You can also check some helpful resources.

Learn about the terms and concepts used in Creator Studio.

Deactivate an activity to stop users from adding it to playbooks in Creator Studio.

Install the ServiceNow Otto for Creator application from the ServiceNow Store to get AI in Creator Studio.

When a user creates an app in Creator Studio, the ServiceNow AI Platform creates several metadata artifacts, such as tables.

Make sure to install Creator Studio on all ServiceNow instances where users will be building applications, including the production instance.

Creator Studio is a no-code application builder on the ServiceNow AI Platform that lets non-developers create request-fulfillment apps without writing code. Use Creator Studio to build apps that manage employee requests, approvals, and fulfillments, such as equipment requests or travel approvals, directly on the ServiceNow AI Platform.

You've added forms and automation to your app, and customized the workspace list configurations. Now what?

Add or remove people who can work on an app, or change their permissions for the app using the Manage collaborators option.

Creator Studio is replacing the older Service Creator tool, which will be retired in the Australia release.

You can open apps built in Creator Studio in other ServiceNow products, but only apps built in Creator Studio can be opened in Creator Studio.

You can preview and interact with the submitted records generated by your app directly in Creator Studio, which mimics what the fullfiller sees in the workspace category for the app.

Publishing forms once they're ready makes them available as catalog items in the production instance for published apps.

Congrats, you’ve built your app and are ready to share the first version of it with the world. That’s great! Deployment is the next step in the process.

This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment.

Find details on the parts of building apps in Creator Studio, such as descriptions of all possible types of questions or layout options for forms.

Change the order that activities appear in the activity picker in Creator Studio to present them in the order you want.

Don't have permission to build an app? Ask your admin to get you started by creating a basic app for you. Just give them a name and tell them what you want the app to do. Once they start it, you’ll take over and modify it.

After users submit a request through an app built in Creator Studio, fulfillers work on the request's submitted record in the Request App Workspace.

Want to work on an app but don't have access to it? No problem. We'll show you how to ask for access.

Creator Studio enables you to build apps where people can make requests.

Service desk apps enable users to request things, such as IT equipment or travel bookings, and track their fulfillment.

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.

Before you request deployment for your app, you can test out submitting a form and interact with any associated automation results on the record it creates.

Learn how ServiceNow Otto for Creator helps you to create forms for you in Creator Studio.

Use the Try it button on the Request forms tab to submit a request, which triggers any associated playbooks and creates a record that you can work with in Creator Studio.

Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team.

You can make the App Engine Studio (AES) template, which is hidden by default, appear for users when they create an app in Creator Studio.

To add items or services to your catalog, you must create a different form for each thing being requested.

Adjust how the submitted records that your app generates will look, such as the order in which fields appear.

When you build an app in Creator Studio, you must create forms and automation. You can also customize the workspace list configurations and records that fulfillers use before everything is deployed to production.

How do you simplify and streamline tasks for fulfillers? Use automation! For example, you can have a task assigned automatically to someone based on what type of request it is. We’ll use playbooks to accomplish adding this automation to your app.

Admins can customize existing email notifications and create templates for new email notifications that Creator Studio apps send. For example, you can add branding to notification emails that a request was opened.

Hide the App type page that appears when users select to create an app by adding a system property to streamline the app creation process.

Choose a different development experience if you want a more robust environment using the experience switcher in Creator Studio.

If you want to develop apps in a more robust environment than Creator Studio, which was designed for no-code developers, you can select a different experience directly from within Creator Studio.

Delete an unpublished form from a Creator Studio app to remove it completely from the ServiceNow AI Platform.

Add more roles to the Experience Visibility Controls table [sn_udc_experience_visibility_control] to give them access to other products in the experience switcher, such as ServiceNow Studio.

Creator Studio is available in light and dark mode.

The experience switcher can provide access to Creator Studio, ServiceNow Studio, ServiceNow IDE. However, whether you can see and select all of those depends on your role or access level.

Bookmark an app to quickly find it in Creator Studio, as well as ServiceNow Studio.

After a form has been published, you can update it, undo changes, and hide it from being visible.

Respond to app creation requests made by users who can't create apps themselves, ensuring that your organization doesn't have too many or redundant apps.

Creator Studio makes creating apps easier by dividing their creation into simple steps. In this section, we'll explain each one.

Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.

In Creator Studio, you can control how people work together on apps by setting up permissions called collaboration descriptors. These descriptors define what users can and cannot do.

After users create apps, they submit them for you, the admin, to review and deploy. How you deploy them depends on whether you have App Engine Management Center (AEMC) installed on the instance.

Roles control what everyone you work with can do in Creator Studio. Administrators assign roles to give team members permission to configure or use Creator Studio.

Perhaps you’ve been given permission to work on an app someone else created, or you want to add new items to the catalog in your app. The Creator Studio home page acts as your central hub, listing all the apps people in your company have built using Creator Studio.