Test Your Processes With JUnit 5
If you’re a fan of JUnit5 for testing on the JVM, we have good news — there’s a brand-new library available: camunda-bpm-junit5, published as a community extension for Camunda BPM. The project is now available on Maven central, so you can start testing your processes with the latest technology. Getting started To add the extension to your project, just add the Maven dependency to your pom file: <dependency> <groupId>org.camunda.bpm.extension</groupId> <artifactId>camunda-bpm-junit5</artifactId> <version>1.0.0</version> <scope>test</scope> </dependency> Add the dependencies to JUnit 5 if you don’t already have them (they are included in the spring-boot-starter-test artifact): <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter</artifactId> <version>5.6.2</version> <scope>test</scope> </dependency> To start testing you can extend your test class with the ProcessEngineExtension: This injects the ProcessEngine configured in the camunda.cfg.xml file into...
How to Anonymize Task Worker Data
I recently got into a discussion about saving user ids of task workers in the database. During the last releases the Camunda Engine got very good in capturing all actions that are done in the Cockpit and in the Tasklist. This is nice for revisions, but some companies, especially in Germany, don’t want to track down every activity to an individual. There is a need to anonymize the work done by task workers: The group manager should not easily analyze who is the best of his team as all team members should be judged equally. In the lifecycle of a user task, you create the task with a candidate group and then a user claims the task and he becomes...
Job Executor Improvements in Camunda BPM 7.4
If you’ve used Camunda BPM you might have noticed our engines briefest feature – it’s really really fast. Might be an idea to have a look at this whitepaper or read about our scalability if you haven’t experienced it for yourself. With the new job prioritization feature and the exponential backoff included in the new Camunda BPM 7.4.0- release you will now be able to improve the speed further by tuning the efficiency of your custom jobs among others. Imagine you have a lot of jobs (maybe 50,000) on a cluster environment which wait to be executed all at the same time. The current behavior of the engine (Camunda BPM 7.3.0) is to acquire all these jobs in parallel and...
How to clean up/purge the camunda history tables
We get this question very often from customers: How can we get rid of old history data that we don’t need anymore? First it’s important to ask: “What do you mean by ‘old data’?”. This is completely business focused and depends on the use of cockpit, who is working with the history data, how reports are generated and maybe even constraints due to legislation. One of our customers – Hamburger Sparkasse (Haspa) – built a solution that is flexible enough to address the issues raised by the questions above: They created a bunch of SQL scripts Created a parameter for the number of days that completed process instances should remain in the database which then moved the old data into a set of archive...
Build your own Camunda task explorer with CDI and JSF
There’s a lot of interest in how to write a task list with CDI and JSF, and not a lot of up-to-date examples available. Until now! – In this blog post I’m going to show you how you can build your own task list with Camunda BPM Build a process application with JSF and CDI To get tasks into your task list, you need to build a process application that includes at least one process definition, as well as some user tasks. A recipe to build a JSF based process application can be found in our getting started guide. After completing the tutorial you’ll have a pizza order process like this: It contains a simple start form to start process instances and...
Cockpit and Deployments
The last days before I traveled to Hong Kong I built a cockpit plugin toshow and delete deployments. On my firstengagement, I thought about how to clean up my database from all thefailing process diagrams that I don’t need any more. I asked Bernd how toget rid of the old stuff. He deleted the H2 files from his computer.That’s a very fresh start. And he is now very fast in finding andinstalling the enterprise license key again. This could be done better in myopinion. On the next customer engagement Isaw a test system with version 168 of the process definition to test.Someone should clean up here. But how? Whatabout deleting the deployment with cascade=true? Who calls...