Camunda Automation Platform 7.22.0-alpha1 Released

Announcements Camunda 7 Updates
1

Camunda Automation Platform 7.22.0-alpha1 Released

We are pleased to announce the next alpha release of Camunda Automation Runtime 7.22. This release features the following improvements:

  • Camunda Docker image JDBC driver versions can be overridden
  • Query Historic Task Instances by root process instance ID
  • Upgraded MySQL Connector to version 8.3.0
  • 7 Bug Fixes

You can Download Camunda for free or Run it with Docker.

For a complete list of all improvements, take a look at the release notes. Please also see the list of known issues.

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

Camunda Docker image JDBC driver versions can be overridden

Users can now build their own docker images and use custom MySQL and PostgreSQL JDBC driver versions thanks to the newly introduced build arguments POSTGRESQL_VERSION and MYSQL_VERSION:

docker build -t camunda-bpm-platform \
--build-arg DISTRO=${DISTRO} \
--build-arg VERSION=${VERSION} \
--build-arg POSTGRESQL_VERSION=${POSTGRESQL_VERSION} \
--build-arg MYSQL_VERSION=${MYSQL_VERSION} \
.

By default, Camunda docker images use the platform defined driver versions but with this feature they can be overridden. This is a great feature if users want to use a newer driver version. For more information see the repository’s readme.

This is a community contribution. Thanks to punitdarira!

Query Historic Task Instances by root process instance ID

Developers can now query historic task instances while filtering on root process instance ID, which means they can now retrieve all task instances triggered by one particular process with a single API call. This applies to both to the Java API and Rest API, and it can be used as shown below:

Java API: The method name is rootProcessInstanceId and can be used like this:

HistoricTaskInstanceQuery query = processEngine.getHistoryService().createHistoricTaskInstanceQuery();

query.rootProcessInstanceId("aRootProcessInstanceId").list();
query.rootProcessInstanceId("aRootProcessInstanceId").count();

Rest API: The parameter name is rootProcessInstanceId and can be used like this:

GET {rest-url}/history/task?rootProcessInstanceId=aRootProcessInstanceId
GET {rest-url}/history/task/count?rootProcessInstanceId=aRootProcessInstanceId

The POST version of these two endpoints is also impacted.

You can also check the complete Java and REST API.

Consolidating Camunda Spin library into the camunda-bpm-platform repository

We’ve moved the camunda-spin project from its previous location into the mono repository. We’re no longer versioning it independently. Instead, we’ve integrated it into the 7.X.Y versioning scheme, so you can conveniently declare Camunda Automation Platform 7.22.0-alpha1 to use the latest release of spin.

Consolidating Camunda Commons library into the camunda-bpm-platform repository

We’ve moved the camunda-commons project from its previous location into the mono repository. We’re no longer versioning it independently. Instead, we’ve integrated it into the 7.X.Y versioning scheme, so you can conveniently declare Camunda Automation Platform 7.22.0-alpha1 to use the latest release of commons.

Share Your Thoughts with Us!

Your feedback is really important to us, so please download Camunda Automation Platform 7.22.0-alpha1, try it out, and let us know what you think about it.

You can contact us in the forum, send a tweet to @Camunda, or file a bug in our issue tracker.

4 Likes