Global modules/tables vs Scoped Applications

[Dedrei L_]

Hi

From what I can find on the community there doesn't seem to be a clear answer as to when to use custom tables and when to use a Scoped Application.  We are in the situation now where we have to make a choice of which one to use for a project and any input, advice or guidance would be greatly appreciated.

We are bringing a large team, that consists of smaller groups, on board to use ServiceNow as their case management system. (We already use SN for IT and a few other business teams). As far as my understanding goes I have two ways of implementing this. Globally or Scoped Application. 

If I take the Global route I will create an Application Menu for the large team with modules for each group as they will have unique requirements/forms.  So a few custom tables/modules under the team's application menu.  All groups will have access to all the modules/tables under the application menu. Or the other option is I can create a scoped application that functions in a similar way.

I don't have much experience with scoped applications, I've mainly just worked with global OOB and custom tables which I've never had any issues with, easy to create, maintain and works well for us. We have one team using a scoped application (created before I joined) and from what I've seen it just creates issues and problems...there's always some issue with their application and cross scope privileges (although they've all been granted) etc. and I find it more complex to implement any changes or updates for them.

I don't want to continue on the global application route if there is a clear defined reason why a scoped application is better practice and I would really prefer to go the global custom table way if there is no definitive reason as to why I shouldn't.

I am aware of the fact that scoped applications protects everything else in global or other scoped apps from being affected by the scoped app and that there are some ACL features if the app needs to be locked down but other than that is there a clear answer to this or is it either or?  What are your views?

[pavan9885]

Hi,

To function accurately and to add few fields in the form and if you plan to extend the tables and scope of the application global scoped applications is the best practice for long run applications without any conflicts but global applications  we can't able to retire if we don't want to use for scoped applications if the customer wants to retire the application we can retire the application without effecting other applications or other modules in the servicenow.

This below links will give you clear picture what I am taking about 

https://community.servicenow.com/community?id=community_blog&sys_id=addca665dbd0dbc01dcaf3231f96192e

http://blog.staveapps.com/application-scope-in-servicenow

https://community.servicenow.com/community?id=community_article&sys_id=d2dce665dbd0dbc01dcaf3231f961...

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

https://community.servicenow.com/community?id=community_article&sys_id=1f03015adbddaf40b1b102d5ca961...

Note : please mark my answer correct / helpful so this question will not be wipped out from the community .

[Dedrei L_]

Pavan thank you, the articles you shared are very insightful.

[SanjivMeher]

I would use custom tables, to store some configuration or data, which is related to the Global scope, or if i want to use it only for on of the ITSM modules.

I would go for a Scoped Application, when I am actually building a functionality, which can be leveraged in multiple places, such as incident, problem, change or even by another scoped application.

Now scoped applications doesn't mean, it is restricted. Only if you want it to be restricted, you need Application Administration checked. Otherwise this application will be accessible in global scope as well.

[The SN Nerd]

You also need to take into consideration the new Madrid Licensing structure which is based on tables.

Where possible you may wish to re-use and extended existing tables rather than create custom ones.