Scope for a Flow Designer?

[shank1]

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!

[Pradeep Sharma · Accepted solution]

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.

[Pradeep Sharma]

I am assuming you are familiar with the advantages between the global vs scoped app. That said, the best practice or recommendation is to always package Flow designer or IHub spokes in a scoped app. This enables you to easily distribute the content via the Scoped app. 

Also, creating your Flow Designer content within a custom application allows you to publish it to the application repository, making it available to all other instances in your organization, or you can publish it to the ServiceNow Store, making it available to everyone.

- Pradeep Sharma

[Pradeep Sharma]

Hello Shanks,

Let me know if that answered your question. If so, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list

- Pradeep Sharma