Camunda 7.10.0-alpha5 Released

By
  • Blog
  • >
  • Camunda 7.10.0-alpha5 Released
TOPICS

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

TRENDING CONTENT

Camunda BPM 7.10.0-alpha5 is here and the highlights are:

  • Configure Business Key in Delegation Code
  • Fetch and Lock Based on Process Definition and Tenant
  • WildFly support
  • 8 Bug Fixes

You can Download Camunda for free (click on Preview Release) or Run it with Docker.

If you are interested, you can see the complete release notes
and the list of known issues.

If you want to dig in deeper, you can find the source code on GitHub.

Configure Business Key in Delegation Code

Within this alpha we introduce new option to configure the business key. The setting can be done inside delegation code (Execution listener, Task listener or Java delegate implementation). In other words you can configure the business key of already running process instance. Here is an example:

public class SetNewBusinessKeyDelegate implements JavaDelegate {
   public void execute(DelegateExecution execution) throws Exception {
    execution.setProcessBusinessKey("businessKey");
  }
 }

You can find more information about the delegation code in our User guide.
What is a business key? – you can check this How to Use Business Keys? blog post.

Fetch and Lock Based on Process Definition and Tenant

The “fetch and lock” mechanism is popular among the users implementing External tasks. Now you can filter tasks based on two new options – process definition and tenant id. You can find
java example below:

externalTasks = externalTaskService.fetchAndLock(2, "aWorkerId")
      .topic("createOrder", 10000)
      .processDefinitionId("aProcessDefinitionId")
      .withoutTenantId()
      .execute();

and here is Rest API example:

POST /external-task/fetchAndLock

 {
      "workerId":"aWorkerId",
      "maxTasks":2,
      "usePriority":true,
      "topics":
          [{"topicName": "createOrder",
            "lockDuration": 10000,
            "processDefinitionId": "aProcessDefinitionId",
            "tenantIdIn": "tenantOne"
          }]
  }

For more information please check the Rest documentation.

A Single WildFly distro

It’s one small step for the Camunda distros, but a pretty giant leap for the Camunda engineering teams. From Camunda BPM 7.10-alpha5, Camunda will only provide a single WildFly distro, always with the latest version of WildFly (currently WildFly 14).

Don’t worry, WildFly 8 continues to be supported through a separate camunda-wildfly8-subsystem (included with this archive), while version 10 and above work with the latest camunda-wildfly-subsystem. New Camunda BPM users, that wish to use it with WildFly 8 or WildFly 10-13, will need to do a full manual installation on the appropriate vanilla WildFly application server.

What’s Next?

The minor release of Camunda BPM 7.10 is coming this November (November 30, 2018). Our team is already working on it, finalizing larger features and clearing the backlog are the clear focus.

You can find out more details if you check out our roadmap.

Your Feedback Matters!

With every release we constantly strive to improve Camunda BPM. To make this possible, we are reliant on your feedback. Feel free to share your ideas and suggestions with us.

You can contact us by writing a post in the forum.

Try All Features of Camunda

Related Content

We're streamlining Camunda product APIs, working towards a single REST API for many components, simplifying the learning curve and making installation easier.
Learn about our approach to migration from Camunda 7 to Camunda 8, and how we can help you achieve it as quickly and effectively as possible.
We've been working hard to reduce the job activation latency in Zeebe. Read on to take a peek under the hood at how we went about it and then verified success.