Book Image

Bonita Open Solution 5.x Essentials

By : Rohit Bhat
Book Image

Bonita Open Solution 5.x Essentials

By: Rohit Bhat

Overview of this book

Creating delightful web-based applications backed by complex business logic and intricate workflows is just one of the many things you can easily achieve by leveraging Bonita Open Solution. It is a highly customizable and efficient tool for business process modeling. Bonita Open Solution is a one-stop solution for developing scalable applications with a nifty user management system and easy deployment. This pragmatic, hands-on guide to developing complex applications is packed with succinct tips and demonstrations of the various aspects of Bonita Open Solution. This book will show you how to make the best use of the Bonita BPM tool, leverage its powerful backend engine, and design business application workflows with ease. By the end of this book, you will be able to develop a complete business process application. Right from designing web forms to integrating business logic to finally deploying the application on a server, this book takes you through the entire development cycle of an application created using Bonita Open Solution. You will learn about modeling business processes in Bonita, creating customizable web forms, and using connectors, contingencies, and transitions to move forward in the workflow. It also highlights the various page flows available, as well as the ease of use of the drag-and-drop, widget-based modular design of Bonita Studio. After developing the application, you will also learn about the various options for deployment, and the different environments on which it can be deployed.
Table of Contents (15 chapters)
Bonita Open Solution 5.x Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

The call activity


A call activity step in Bonita is like a function call in programming languages. Here a pool is called by a call activity, unlike a function. After the called pool completes, the control is passed back to the calling step. A mapping is defined from the parent pool to the subpool and a reverse mapping is also possible.

Let us illustrate the call activity in our TicketingWorkflow. One thing we notice is that we can separate out the report submission tasks into a separate pool. This is due to the fact that this task doesn't use the pool variables that we use for booking a ticket, nor are the variables used in this task useful in booking a ticket. Hence, it makes sense to separate out this activity.

  1. Make a new pool called Report and add all the variables necessary for the report submission in this new pool, namely, report, reportSubmitter, and comments. Delete the two variables, except reportSubmitter, from the TicketPurchase pool.

  2. Next, copy the two steps from the TicketPurchase...