We are pleased to announce the next alpha release of Camunda Platform Runtime 7.18. This release features the following improvements:
- Log level configuration for BPMN stack trace
- Exception error codes
- 2 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.
Log Level Configuration for BPMN Stack Trace
We’ve added a new configuration property called
logLevelBpmnStackTrace to change the default
DEBUG level of the BPMN stack trace.
The default behavior remains the same as before, so you don’t have to do anything.
However, if you want to see the BPMN stack traces in the log, but don’t want to turn on debug logging, then you can change their log level with this parameter.
<property name="logLevelBpmnStackTrace" value="INFO" />
Possible values are:
ERROR, WARN, INFO, DEBUG, TRACE.
Exception Error Codes
Sometimes, an error occurs when you call the Camunda 7 Java or REST API.
Reading the error message might help a human being to understand the root cause of the problem. However, evaluating error messages in an automated way is not a good idea since:
- The message might change with newer versions.
- Relying on fragments of the message can be error-prone.
This is why we introduced static exception codes your business logic can rely on to determine specific problems and react accordingly. Look up our built-in error codes in our glossary.
You can also define your custom error codes by registering a custom code provider or assigning them to your exceptions thrown from the delegation code.
Read more about this feature in the User Guide and learn how to access error codes via Java, REST, or Open API.
Share Your Thoughts with us!
Your feedback is really important to us, so please download Camunda Platform Runtime 7.18.0-alpha3, 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.