Skip to main content
Version: Next

Update notes (3.7.x to 3.8.x)

Heads up!

To update Optimize to version 3.8.x, perform the following steps: Migration & Update Instructions.

The update to 3.8.x can be performed from any 3.7.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​

No known issues at the moment.

Changes in supported environments​

Elasticsearch​

While OpenSearch was never officially supported by Optimize, up until Optimize 3.7, the version of the Elasticsearch client used was also compatible with OpenSearch. With this release, the client has been updated to a version no longer compatible with OpenSearch, meaning that Optimize will also no longer work with OpenSearch.

New behavior​

Due to a general overhaul in the public API, the authentication to all API requests must now be performed via a Bearer Token in the request header. In previous versions, you had two possible ways to authenticate your API requests: by providing the secret as the query parameter accessToken, or by providing it in the request header as a Bearer Token. If you were using the latter method, no change is necessary and your requests will keep working as usual. If you were using the query parameter method, you will need to change your requests. For more information, see authentication.

Changes in translation files​

In case you manage your own translations into different languages, you can find a list below with all the changes that need to be translated for this release.

Localization file​

The following terms have been added/removed to/from the localization file (en.json) since the last release:

en.json.diff

  • lines with a + in the beginning mark the addition/update of a term, lines with a - mark the removal of a term

Text from "What's new" dialogue​

For the purposes of translation, find the text for the What's new dialog below:

## Set and Track Time-Based Goals

Set data-driven service level agreements (SLAs) on how long all your processes should take so you can quickly identify which processes are underperforming.

## KPI Reports

Create reports and alerts tracking percentages like fully automated instances or incident rate (%), plus SLA statistics on durations like P99 or P95 duration in addition to minimum, median, and maximum.

## Improved UX

Rename variables in plain language, filter out noisy outlier analysis heatmaps, and apply rolling date filters to your dashboards to focus on the most important data.

For more details, review the [blog post](https://camunda.com/blog/2022/04/camunda-optimize-3-8-0-released/).