Update notes (3.8.x to 3.9.x)
Heads Up!
To update Optimize to version 3.9.x please perform the following steps: Migration & Update Instructions.
The update to 3.9.x can be performed from any 3.8.x release.
Here you will find information about:
- Limitations
- Known issues
- Changes in the supported environments
- Any unexpected behavior of Optimize (for example, due to a new feature)
- Changes in translation resources
Known issues
If there are processes in Optimize that currently do not have a process owner assigned and a new process is deployed via Web Modeler, a new process owner may be assigned to one of the previous processes without an owner. This is not critical as this does not incur any changes in permissions, but is important to understand regarding who gets email notifications for processes. If an owner is set incorrectly, you can change it manually in the processes page. This issue is resolved with the 3.9.1 version.
Changes in supported environments
Camunda 7
Optimize now requires at least Camunda 7 7.16.0
and supports up to 7.18.0+
. Camunda 7 7.15.x
is not supported anymore.
See the supported environments section for the full range of supported versions.
Elasticsearch
Optimize now requires at least Elasticsearch 7.13.0
.
See the supported environments section for the full range of supported versions.
If you need to update your Elasticsearch cluster, refer to the general Elasticsearch update guide. Usually, the only thing you need to do is perform a rolling update.
Changes in translation files
In case you manage your own translations into different languages, you can find a diff below with all the changes that need to be translated for this release.
Localization file
The following terms have been added to or removed from the localization file en.json
since the last release:
- Lines with a
+
in the beginning mark the addition/update of a term; lines with a-
mark the removal of a term.