setWorkflow() cross-scope access issue

[Robbie Lacivita]

I am unable to call setWorkflow() from a scoped application.

I've attached the code that I'm running, as well as an image of the cross-scope access policy and an excerpt from the log.

The ServiceNow documentation clearly states that setWorkflow should be callable from other application scopes. the cross-scope access was granted, however the logs still say that access to the api 'setWorkflow' from my application scope was refused due to the api's cross-scope access policy.

I am at a loss on how to solve this. Has anyone else experienced and solved this?

I had an idea to create a global script include to call setWorkflow, and call that function from my app scope, but it appears that it simply sets setWorkflow for any calls from the Global scope, and everything I'm doing from my app scope still triggers business rules to run.

Thanks,

Robbie

[CJB]

No joy. Still getting error. 😞