Update from 7.7 to 7.8
This document guides you through the update from Camunda BPM
7.8.0. It covers these use cases:
REST API Date Format
This section is applicable if you use the Camunda engine REST API.
The default date format used in the REST API requests and responses has changed from
yyyy-MM-dd'T'HH:mm:ss.SSSZ (now includes second fractions and timezone).
The Camunda webapps support the new format by default.
In case some custom REST clients rely on the old date format, choose one of the two following options:
- Update REST clients to use the new format.
- Configure custom date format for Camunda REST API (explained in detail in the Custom Date Format) section.
Failed Jobs Retry Configuration
There is no need any more of enabling the retry time cycle configuration for failed jobs. This is the default behaviour from now on.
You should clean up the following lines from the process engine configuration file in order to be consistent with this behaviour.
<bean id="processEngineConfiguration" class="org.camunda.bpm.engine.impl.cfg.StandaloneInMemProcessEngineConfiguration"> ... <!-- remove this property --> <property name="failedJobCommandFactory" ref="foxFailedJobCommandFactory" /> ... </bean> <!-- remove this bean --> <bean id="foxFailedJobCommandFactory" class="org.camunda.bpm.engine.impl.jobexecutor.FoxFailedJobCommandFactory" />
This section concerns Java API and the interface
org.camunda.bpm.engine.impl.incident.IncidentHandler that is part of internal API.
The return type of
IncidentHandler#handleIncident has changed from
Incident. The API expects that an incident is created and returned.
In case there are custom incident handlers implementing that interface, the method
handleIncident(...) should be adjusted. The method can return