Creator Studio glossary

Learn about the terms and concepts used in Creator Studio.

activity

Activities in a playbook complete automated tasks, such as obtaining approvals and assigning records.

automation

Tasks or requests moving through a workflow without manual intervention.

board view

A traditional layout of viewing a playbook, which shows each activity as a card in the navigation panel. When you select an activity, for example a task, its editable details appear in the canvas for you to work with them.

catalog

A collection of items that represent all the items a requestor can ask for.

collaboration descriptor

Level of collaborative access assigned to a developer. The collaboration descriptor that someone is assigned determines if they can assign, manage, and monitor delegated development permissions. For example, people who are Owners of an app can do more than people with the Editor collaboration type.

delegated development

A collaborative process that enables developers to invite other people into apps so they can co-create and develop the app together.

deployment

The process of an app moving from a non-production instance like development or QA through to production. Production is the instance that your customers see, or your “live” instance.

diagram view

A visually intuitive diagram that shows you the order that activities occur in the playbook. When you select an activity, such as the trigger or a decision, a modal pops up where you can edit its details.

extend a table

When you create a table based off an existing table. Extending a table means the new table inherits the parent (extended) table's columns, as well as its business logic. Apps built in Creator Studio extend the Request Task table.

field

A field in Creator Studio is a column on the related Task table. Ii you're using condition builder, a field is either a column on the table or a question from the form.

form

A content page that displays fields and values for a single record from a database table.

form template

A pre-defined set of questions arranged on a form provided by Creator Studio.

fulfiller

Someone who works on requests. Fulfillers may also approve or deny requests, depending on any approval automation for the app.

item

Something a requestor can ask for, such as new computer equipment or time off work. Each item requires its own form in Creator Studio.

playbook

A set of automated activities that occur based on a trigger, for example, automatically assigning a request to a manager for approval. Think of playbooks as pre-programmed workflows that kick in after a form is submitted. They are like if/then statements: If this happens, then that will happen.

record

A task or request that needs to be acted on. All rows in your app's tables are individual records. Records have different states depending on what actions have been taken.

reference-based question

Question on a form that retrieves its possible answers from the table you define.

release notes

Information about what's included in each new version of the deployed app, which helps admins track what the changes are between app versions.

requestor

Someone requesting something, like a piece of equipment or permission to do something, such as take time off work.

target table

The table where apps created in Creator Studio store their requests.

trigger

The event that makes an automated playbook begin running. For example, submitting a request automatically assigns it to a manager.

version number

A number assigned to the app that increases with each subsequent time it's deployed.

workflow

A sequence of activities to automate processes in applications.