FXApps

Here's one interesting thing: everything gets better with jBPM. Even a CRUD (which does not exactly represent a business process) can be quickly created and you can have a much better overview of what's going on without having to read any line of code. In this post, I am going to show you a CRUD I created using the JPA Work Item Handler from my last post . The CRUD business process The CRUD actions are based on an Object of type Person created using the Data Modeller tool: The object used in our CRUD. It was created using the data modeller  The business process to create the CRUD make use of human tasks to get users input. A human task is responsible for creating an application menu for the user, the other tasks read users provided data. See the process diagram: A jBPM CRUD Diagram The box with text "Select Contact" is a reusable subprocess which goal is let users select one of the existing contacts (Person): User can select a contact fr...

When we work with jBPM, we can already invoke REST and SOAP Web Services, send email without the need of writing a single line of Java code. You can simply drag and drop a component and configure it to perform the action. Using the REST Task from jBPM 6 Behind a component (tasks), we have a Work Item Handler(WIH): Creating custom Work Item Handler in BPM Suite/jBPM 6 A Parser work item handler for jbpm 6 In this post I will briefly talk about a work item handler I recently created to perform JPA(Java Persistence API) operations. Persistence and jBPM The jBPM process runs on a transaction. Once it reaches a safe point (start a subprocess, human task, timer and others), the transaction is commited. If we do operations that requires a transaction, it is important to these operations to be part of the running jBPM transaction. To persist process variables, we can use a  JPAPlaceholderResolverStrategy  and the process variables will be also persisted as part of the ...