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
- Drag a Scope 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 scopes. This provides a more sophisticated way of organizing or separating the activities into a subsection of the flow.
- Drag a Scope 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!