Unable to access Global application when creating new flow, action, etc. in Workflow Studio

[Wm Hadley]

Hello,

We just upgraded to Washington D.C. and have the latest update to Workflow Studio. When attempting to create a new flow, subflow, action, etc., I am unable to choose Global as the application for which I want to create the new flow. Global was always an option, and I am in the Global application scope. It appears all other applications are available in the dropdown list.

I am able to copy a flow with Global already set as its application, and it will create the copied flow in the Global application, but this only works for copying. Is there a property or ACL that is causing this issue? It is a bit burdensome to not be able to just create new items in Workflow Studio if I need them to be in the Global application.

[Wm Hadley]

No one else that upgraded to Washington DC has experienced an issue with accessing Global or other specific app scopes?

[Josh Barbour · Accepted solution]

I found a KB article from ServiceNow. KB0993570

It references having the delegated_developer role. Delegated developers don't have access to create flows in the Global scope. 

I removed the delegated_developer role from my account, logged out and back in, I now have access to the global scope.

Note: I also have the admin role in our dev instance. Admin did not override having the delegated_developer role. 

[Rich Currie]

this was it, fixed us up perfectly.

[Wm Hadley]

I was late getting back, but this was it (in a weird way). When we upgraded to Washington D.C., it added a bunch of previously non-assigned roles to my account (instance admin but also assigned as developer on scoped apps). Apparently this led to my account being restricted from creating flows in Global scope as mentioned by @Josh Barbour . Once I removed the newly added roles, I was able to access Global scope again!