Flow Designer Question - Flow is in Global, sub flow is in scoped app

MS12
Kilo Sage

Hi,

 

I have a flow that creates cases when a catalog item is submitted. Nothing special there.

When the case is created, it also has to create tasks which I'm doing using sub flows. One of the task type is in a scoped application. I couldn't create this task from global scope, so I created the sub flow in the scoped app.

Now in Dev, everything looks good and works correctly. But anytime I make a change and publish the app and install in Test, it stops working in Test. I'm still not sure what's happening.

One time I noticed, my sub flows were in draft state in Test and I had to publish again.

This time I'm seeing my main flow gives an error that it doesn't exist when I try to access it in Test.

 

Wondering if anyone has experience with flows and sub flows in different scopes. Can you please give me ideas on what I'm doing wrong.

Thank you!

2 REPLIES 2

shloke04
Kilo Patron

Hi @MS12 ,

 

When you have done the above changes in Dev, there must be some cross scope privileges which got created in Dev with status as approved allowing cross scope access to work. 

While moving your changes to test, those cross scope privileges might not have been moved and hence it might not be working.

 

Navigate to the module Application Cross Scope Access or use the link below to check for entries against your scoped app providing access to global and then manually move them to Test if those are not moved via XML:

 

https://instance.service-now.com/sys_scope_privilege_list.do?sysparm_userpref_module=ab8a63b35b00120... 

 

https://instance.service-now.com/sys_restricted_caller_access_list.do?sysparm_userpref_module=87476f... 

 

Replace "instance" with your instance name

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

Thanks for your reply. The cross scope and everything is fine. I found this article that addresses my issue. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0823104

 

Sounds like what they are recommending is publish main and sub flows with each change. Doesn't sound like a good solution to me. But that's working for me right now.