- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 07:17 AM
Hello,
As per below link:
https://community.servicenow.com/community?id=community_blog&sys_id=09becbf3db589b403882fb651f961986
it says 'Before you begin creating a flow, create a custom, or scoped, application for the content to reside in.'
Can any say what is the necessary for a scope here?
Also,
1. Say I want to implement some automation on incident module. should I create a scope to build a flow?
2. When creating catalog items, should I create catalog items in global scope and flow designer in non-global scope.
Am I missing anything?
Thanks for your inputs!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 08:29 AM
Hello Shanks,
If there are major changes to be modified then the best practice is to create a new scoped application and capture all the changes within that application scope. All the SN app artifacts can be inherited by creating a dependency with in your custom scoped app. This way you get the option to publish an app on multiple instances via "make the app available to other instances". On the other hand, if the changes are minor then you can create an update set in the same SN app scope/global and move the changes through the update set.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 07:25 AM
Hi Shanks,
You can capture changes in the global or scoped app. Depending on your requirement you should decide whether to create a global or scoped app. Details below.
Global app: A global application provides no boundaries compared to the scoped application. It can be used to create legacy application or to merge multiple global update sets in one application.
Scoped app: Scoped application provides strong application boundaries and run-time isolation. This allows for installing a new application without breaking existing applications.
- Pradeep Sharma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 08:03 AM
Hi Pradeep,
Thanks for your response, but its a generic definition you have given which I know 🙂
I am looking for an explicit answer wrt Flow designer, as to why a scope is needed for it..
As per the Best practices for FD by ServiceNow
("Always build an action or flow within a scope – but not the Global scope")
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 08:13 AM
Hi Shanks,
Consider you want to have a flow designer for HR Application on HR Case Table (sn_hr_core_case); it is best practice to use HR Core Scope to create the Flow using flow designer. It makes more sense to keep related component in same scope. I hope this helped.
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 08:20 AM
Hi Ankur,
Back to my original question, considering below 2 scenarios, can you provide your inputs.
1. Say I want to implement some automation on incident module. should I create a scope to build a flow?
2. When creating catalog items, should I create catalog items in global scope and flow designer in non-global scope.