In this chapter, we introduced the concept of the <scope> activity and described the advantages of it. Then, we realized how to add the <scope> activities to hierarchically organize the book warehousing sample. Some of the differences of the <scope> activity and other activities such as <process>, <sequence>, and <flow> were explained. Then, we realized how to add a fault handler and a termination handler to a <scope> activity. Finally, we introduced the concept of isolated scopes. By the end of this chapter, the reader is capable of declaring a <scope> activity to organize a WS-BPEL 2.0 process hierarchically.

In the next chapter, we will learn about activities that facilitate to model parallel and repetitive tasks such as sending an invoice to 100 clients. These activities facilitate users to inherently model parallel tasks without much of a hassle while improving the execution performance of the BPEL runtime.