Global modules/tables vs Scoped Applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 06:57 PM
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?
- Labels:
-
Best Practices
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 07:34 PM
Pavan, due to the fact that I'm going to extend the Task table, would you suggest staying Global then and not doing it in a Scoped Application?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 07:37 PM
Yes you are correct but keep in mind when you are using the global scope fields extended from task and don't try to change any choice values or default values of the task extended it gone effect all other tables as well . Other than that everything is fine and you can create n number of custom fields as per your requirement .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2019 07:55 PM
Thanks Pavan, yes I'm fully aware of that as we have a few tables extending Task already.