The sample application should show how "easy" you can do something. The purpose of this sample application is to show, how difficult is to solve problems caused by misleading samples. I do not have a name for this kind of sample. Let's name it fix-sample application.
Even my 15+ years in BPM and 10+ years with jBPM, Activiti and Flowable, is not enough to find and cover everything. I would like to encourage anybody, who has a problem to write an issue to the project, or even better to contribute
The first step is dedicated to an ordinary sample application.
No problem till now, just follow the doc. (flowable, spring boot...)
How to test model with assertions?
Automate model downloading in maven build.
Flowable allows us to create any variable of almost any type. The projects use variables to store application data. The cost of creating a variable is almost none, the cost of maintenance is tremendous.
To demonstrate cost of maintenance, I created a project to support tests between versions crp-sample-upgrade.
Each module depends on the different crp-flowable-springboot-sample version. The test usually works in the following steps:
- Generate data on the "current" application version and store the status in the DB,
- Start the new application version and run the tests.
Detailed description: HowTo.
I do not expect somebody uses java serialization for variables. Why not example
Json variables are commonly used. The variable structure and operations on the variable instance are tighten together in the process model. If the operation on structure is outside the process model, the problem is similar.
JPA variables do not store data directly in the process. The process stores only a reference to jpa entity. Where is the problem now?
Flowable allows to create variables easily. The problems described above are only small sample. The rules to follow.