Summary

In this chapter, we learned the <forEach> activity in detail. It lets us define repetitive tasks in a sequential or in a parallel manner. First, we learned a practical use case of the <forEach> activity by try outing an example. We then discussed how to configure a <forEach> activity systematically. During this exercise, we also learned about dynamic partner links as a requirement to invoke different endpoints within the <forEach> activity in parallel. After that exercise, we explained each configuration within the <forEach> activity that determines the repetitive and parallel behavior. Therefore, at the end of this chapter, the reader is capable of declaring the <forEach> activity to define repetitive tasks in a sequential or in a parallel manner.

In the next chapter, we will introduce the concept of human interactions in WS-BPEL 2.0 processes. We will learn how the BPEL4People extension is based on the WS-HumanTask specification to implement...