Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Workflow scope restrictions

Log in to subscribe to topics and get notified when content changes.

Workflow scope restrictions

There are some restrictions to public and private application scopes.

During runtime, publicly scoped workflows can access other application resources, as long as these resources are set to be accessible to all application scopes. Privately scoped workflows in a private application scope can only access resources private to its scope. Due to scope access boundaries, any privately scoped workflows that make calls out to other scoped resources fail with either an exception or a hung activity while waiting for returned results. This occurs when making calls to these common global resources:
  • ECC queues
  • Tasks
  • Approvals
  • Events
  • SLA timers
  • Timers
  • Script includes
  • Business rules
  • Workflow APIs

As you design workflows, validate the visibility and accessibility of all resources prior to deployment. See

For information on how to configure the scope for a workflow, see Workflow properties.