Welcome to Creator Studio! With our release on May 9th, 2024, we're excited to bring a new application development experience meant to be a new entry point for business users to truly use their process expertise to automate, streamline and own their own work.
Over the next few weeks, We'll be posting every week to give you an overview of What Creator Studio is, how to use it, how to integrate it into your existing development infrastructure, and how it can help make big differences in your organization in a very short amount of time.
Today, let's get introduced to Creator Studio.
What is Creator Studio?
ServiceNow's Creator Studio is a game-changer for non-developers, offering a user-friendly, guided environment to build request-based applications. By breaking down traditional barriers, it empowers business process experts to transform their automation ideas into tangible solutions without extensive coding knowledge.
While not intended to replace existing development tools like App Engine Studio, Creator Studio complements them by providing a fresh entry point for app creation.
This innovative approach represents a paradigm shift in how we perceive application development on the ServiceNow platform, opening it up to a broader audience and enabling more users to contribute their process expertise into real life applications.
This innovative approach represents a paradigm shift in how we perceive application development on the ServiceNow platform, opening it up to a broader audience and enabling more users to contribute their process expertise into real life applications.
When a user logs into the Creator Studio application, depending on which level of access they have (Full, or limited), they'll be presented with a view of all the applications they're entitled to, and may request access to those they do not.
If they've got full Creator Studio access, they'll be able to create a new application by clicking the "Create Application" button on the top left.
In further articles, we'll talk about Creator Studio apps, their structure, similarities to other apps, and their differences. but for now, the key thing to remember is - each NEW Creator Studio app is created in it's own Scope, which protects the integrity of that apps data.
Each scoped app in Creator Studio, can contain multiple forms, which is a great new way of developing apps, allowing single departments to have many input forms, but keeping the licensing, data management, and maintenance simplified and streamlined.
Let's get to the ways and tools used for building an App in Creator Studio -
When building an app with Creator Studio, there are 3 major areas that you'll be using to build your application, those three areas are - Form Creation, Automation, and Workspace.
Form Creation
The form builder provides a curated set of configurable form components , allowing the user to change labels, provide explanation text, add necessary field types, reference data, and simply build out their catalog item as the first component of their app.
Playbook Automation
Under the hood of Creator Studio Automations are Playbooks, one of the most powerful pieces of Creator Studio, allowing process owners to translate their process expertise into powerful automations with a curated, simplified set of process automation designer components.
Users add triggers to determine when tasks run, and can add and modify process steps using the visual diagram, or Kanban view.
Workspace
The unified Creator studio workspace provides app fulfillers a single area in which they can access their own curated, pre-filtered lists of submitted app requests.
Every creator studio app resides within this same Creator studio Workspace.
Providing a convenient fulfillment experience, without the overhead of creating and maintaining multiple workspaces.
Every creator studio app resides within this same Creator studio Workspace.
Providing a convenient fulfillment experience, without the overhead of creating and maintaining multiple workspaces.
Because each created app has it’s own agent role automatically created, when an individual logs into the Creator studio workspace, they're going to only see the Creator studio apps that they have permission to see via that role.
Deployment
After building an intake form, creating the single-step automation, and configuring the workspace,
the final step is to submit the app for deployment,
Creator Studio integrates natively with App Engine Management Center, and uses pipelines to deploy apps, providing a configurable method to deployment to instances.
Using Pipelines simplifies the governance process, and eliminates the need for Creator Studio developers to concern themselves with deployment configurations.
When you create your Creator Studio app, You get your own app scope (and associated roles), which helps to encapsulate all developed components into an easily deployable package.
Pipeline deployments give admins full control to decide which apps can be promoted to their production instances through the App Engine management center.
Once an app has been approved by admins, the app can then be used across the organization.
Next
Keep an eye on the Creator Studio product page, there will be more content over the next weeks and months covering the how's, why's, when's on using and growing your application development with Creator Studio.
Thanks, and Cheers!
Kiernan
5 Comments
