Flow designer and scopes

[Tony Croft]

Hi All,

The recommendation is to create a custom or scoped application for flow designer content and not use the global scope.

I am currently following the CAD course and from what I gather so far when creating a new application you have to define to use either an existing table or create a custom table.

Apologies if this is a stupid question....

What if the flow you have been asked to create doesnt use a table?

i.e 

The requested flow is to

1) Run at a schedule time

2) Run an API query/ SQL query / powershell command etc etc

3) Depending on output send an email

That is is it.... No tickets, No lookups etc

Would you just keep this in Global or do you still create a custom app? If you create a custom app how do you handle the requirement to have a table?

Thanks

[Sandeep Rajput · Accepted solution]

@Tony Croft I would just keep the flow in the Global scope. Creating a custom application just to create a flow is too much to ask for. I have created many flows in Global scope and never faced any issues so far.

In your case, I recommend creating the flow in the Global scope.

[Sandeep Rajput]

@Tony Croft Does my response address your question, if yes then please mark it as an accepted solution.

[Tony Croft]

Thanks Sandeep,

I have created flows before and had just used the global scope, but after seeing this on the course was wondering if I had been doing things wrong