We are happy to share the fourth alpha release of Camunda BPM 7.13 with you!
This release features the following improvements:
- Read Permission for Historic Process Instances
- Query for Definitions by Deployment Time
- 14 Bug Fixes
You can Download Camunda for free (click on Preview Release) 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.
Read Permission for Historic Process Instances
Previously, it was only possible to grant a user read permission on historical data in a very
coarse-grained manner for all instances related to a particular process definition key at once
and not fine-grained only for certain process instances. Alpha 4 introduces the feature to grant
read permission on specific Historic Process Instances.
You can enable the feature with the help of a process engine configuration flag:
<property name="enableHistoricInstancePermissions">true</property>Read more about the feature in the User Guide.
Query for Definitions by Deployment Time
All Process and Decision Definitions receive a timestamp when deployed to the engine. Sometimes it
would be useful to be able to query for only those definitions that were deployed after or at a
given moment (e.g. to only fetch the definitions that were added after your last query).
With this release we expanded the capabilities of the ProcessDefinitionQuery and the
DecisionDefinitionQuery so you can do just that. Both queries now have filter and sort options
for deployment time.
query.deployedAfter(Date deployedAfter);
query.deployedAt(Date deployedAt);
query.orderByDeploymentTime().desc();The same functionality was added to the equivalent REST endpoints. You can find the details
described in the REST documentation for
Share Your Thoughts with Us!
Your feedback is really important to us, so please download Camunda BPM 7.13.0-alpha4, 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 ticket system.
