Last week, I was at the JUG Summer Camp [1], a French conference about Java and fun technologies like BOS for a talk with Sébastien Prunier, a member of BOS community.
After a night at the speaker’s B&B, we started a nice day with a lot of java/javascript/noSQL/arduino geeks and had our session…
So, let’s imagine a really nice call for paper application. A few weeks in the past, I submitted my paper, I was happy, one thing done !
A bit later, I checked my emails and could not find if I had submitted something so I posted my talk again. And 3 days before the closing date, I started getting organized to leave and still didn’t know: did I submit my talk or not ? In doubt, I posted it again.
This lack of notification shows there was no real process to handle submissions, and no way to handle duplicate submissions, so integrating a BPMS could be a nice solution.
Here we go, let’s design a nice process. When someone submits a paper, confirm the paper was submitted, then validate it’s not a spam, pass it to the jury to vote to accept it or not, compute the results and notify the submitter of the result.
At each step, we have to interact with the business web application as it handles all business data (including the votes) and data state.
Now, as the process seems right, we map its start with a submission: upgrade the service layer of the webapp and start the process. This has been done with the engine REST API.
In an hour, the web application is ready to go. And next year, I won’t submit so many copies of my talk 
As always, the source code of the project can be downloaded on github [2]. Feel free to fork it, contribute or open some issues to expand it. You’re also welcome to discuss it on the forum [3]
