Are you still developing in the global scope?

[Chuck Tomasi]

I'm hearing more and more that a lot of people are still developing their solutions in the global scope despite all the great development advancements we've built in to the platform (e.g. Git integration, Studio, delegated development, publish/install, etc.). Our platform business unit has the vision that we should all be building using scoped apps. This includes new apps as well as extensions to existing applications (even in the global scope.) I'd like to know what's keeping you from realizing that vision. Examples may include:

• There is a scripting API that is not available to scoped apps
• Our requirements force us to use synchronous Ajax
• We are still on Eureka
• I love update sets!
• I just don't know enough about creating scoped apps (and that's OK.)

Specifics are always appreciated. Thanks!

[Jace Benson]

I agree with what others have said. Additionally, wanting to access global tables and no easy way to allow that with the install is a huge issue for me. If you want to use the locations from cmn_location you can't modify that data. I get why but then you effectively have to manage this apps locations as a copy of what you really want.  

[greg54]

I second this. I ran into an issue recently where I had to add a "supporting" field to the sys_user and core_company table as part of my custom app and there is no easy way to do this to my knowledge outside of switching to the global scope and capturing it in a completely different update set.

I can understand where ServiceNow is coming from doing this as they don't want apps installed from the store affecting core tables, but there also needs to be the understanding that this is typically necessary in most custom applications.

Maybe just giving the user a warning that core tables x, y, and z will be updated as part of this install.

[Chuck Tomasi]

Hi Greg,

I'd be curious to know more specifics. I've created custom fields on OOB tables (cmdb_ci) to be specific. The field name is prefixed with the scope. For example, if you have an app scope x_snc_chuck and add the field "alternate" to cmdb_ci, it will be called "x_snc_chuck_alternate" and exist in your scope. This worked fine for Geneva and Helsinki in my tests.

[The SN Nerd]

I'm having trouble getting other developers to write re-usable components in scoped applications because of the fear that once something is in a scoped app, it becomes a red-marker for being charged for a platform run-time license (formally CreateNow). There is no formalized documentation (that I know of) that explains licensing around scoped applications.

I would love to see this addressed and feel more people would take it up if there was more clarity.

[yundlu316]

Hi Chuck,

I stumbled across this post when doing a search to find out more information regarding the benefits of developing a scoped app versus global.   Would love to hear your thoughts as I'm trying to learn more about the differences.

thanks!