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!

[Peter de Bock1]

hi Chuck,

Thanks for your quick feedback!

I had issues with the "Form" (widget-form) widget. So far as I can remember I bounced into issues such as "$sp.save" which was not supported. Removing this solved it. Same widget in Global scope solved it too, which I choose as the way to go forward due to time constraints. So our app was partly (a couple of Portal widgets) developed in global. We are on Kingston by the way.

I noticed while Googling that other developers had similar issues with other $sp functions:

$sp.translateTemplate{}  

https://community.servicenow.com/community?id=community_question&sys_id=e55f32a9db58dbc01dcaf3231f9619f9


$sp.getRecord()

https://stackoverflow.com/questions/46368703/servicenow-substitute-for-sp-getrecord-in-scoped-app?rq=1

 

regards, Peter

[John Caruso]

[Inactive_Us1705]

I've only just com across this thread, but 2 years ago was the last comment! What has become of this extremely important post! I was going to add a few reasons why I still find scoped apps a pain but looks like there is no activity in it - shame!