Why use Studio versus Just Create a Table

[Joshua Cassity]

So being a rather new developer, what are the pros / cons of using Studio to create applications in a Scope versus simply just creating a new table in the Global arena?

And if we have tables / processes that were created outside of Studio, is it worthwhile to try to convert those things into scoped applications?

[Harsh Vardhan]

Hi Joshua,

Please check the link below

Community Code Snippets: Studio Ins-and-Outs

Custom Applications. What is the benefit?

ServiceNow Studio

[Chuck Tomasi · Accepted solution]

Hi Joshua,

Studio is a great way to keep track of all the artifacts (files) in your scoped application. I have been building applications for many years and I'll be the first to admit that   keeping track of ever client script, business ruie, and ACL is kind of a pain without Studio.

Yes, you can create a table (global or scoped) outside of Studio. If scoped, it will automatically be tracked in Studio so you can manage it later.

Global apps, while they may seem nice at first, offer no app-to-app permission control. Imagine installing a new app on your phone that automatically had access to your address book, camera, and wallet? OUCH! That's what scoping offers (among other things.)

Studio also allows you to use source control (Git) on your scoped app - which is pretty sweet when you have to go back and make changes or want to explore something new on a branch.

Scoped apps also allow for the publish/install feature to move between instances instead of the legacy update sets.

As a best practice, start creating new apps in scope and use Studio to help manage and control them. I don't just say this as a ServiceNow employee, I say it as an experienced developer.

Let me know if you have any questions.

[Joshua Cassity]

All that sounds like definite pros; however, I saw this and wondered if this is still true:

As a general rule of thumb (depending on your license agreement), all roles that give access to custom application require a CreateNow license.

So would we be charged an additional licensing fee per user that used a custom application built using Studio?

Ex. I build a cool little application that can be used to track Build Books for Servers from Initiation, Approvals, Life Cycle Support to Closure. And I can't publish this to the store or anywhere else but within my employer's instances since anything I build they own.

If I deploy this application and they have 100 Architects use it, does our enterprise now have to pay an additional fee per month for those 100 users in addition to all their ITIL licenses that they already are consuming? If so, that may be a big deal if we end up with many custom applications.

Just trying to figure this out before

[Chuck Tomasi]

Hi Joshua,

I am reluctant to get in to a discussion about licensing on the community because it changes and someone might consider this "gospel" for an argument later. What I can say is that licenses for custom applications, at this point, are not based on role or scope, but rather the defined process. If you create a book tracking app, then you are likely going to need a license or two.

Please discuss licensing with your account team before venturing in to custom apps to understand financial impact.

And FWIW, "CreateNow" term has been changed to "Now Platform" (also formerly known as Platform Runtime.)