The Integration blog covers the latest in product updates, best practices, customer stories, and more.

A simple guide to use nested scope in orchestration

Arif Rafique
Director, Software Development

Wish you cloud have nested scopes in orchestration? Now, you can use nested scope in OIC integration!  In this short blog, I will show you how to use nested Scope in your orchestration.

Scope activities allow users to group other child activities which have their own Variables, Fault and Event Handlers.

  • Create or Edit an integration
  • DragScope activity onto the canvas or use the inline menu.

  • Upon dropping the Scope you will be prompted to enter Name and Description (optional)

  • Upon clicking Create the scope will be added to the canvas.

  • Scope activities can also contain other scope activities, this is referred to as nested scopesThis provides a more sophisticated way of organizing or separating the activities into a subsection of the flow.
  • DragScope activity Inside the other Scope activity

  • Upon dropping the Scope you will again be prompted to enter a Name and Description (optional)
  • Upon clicking Create the scope will be added to the canvas inside the other scope

  • A nested scope behaves the same way as a basic scope, it provides its own container of child activities and fault handlers
  • There is no limitation to the levels of nesting.  Even scope’s fault handlers can have nested scopes

Hope you enjoyed the nested scope feature!



Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.