-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
None
-
Camunda 7.9.x
Optimize 2.2.0
-
3
-
Not defined
As of https://docs.camunda.org/optimize/2.2/introduction/supported-environments/ supported environments for Optimize 2.2.0 are:
- Camunda Engine from version 7.8.7, 7.9.1 and 7.10+ with REST API and history with level full enabled
In production I would never recommend to activate the history level "full". Typically this is for development purposes only. Sometimes you want to see additional information (like descision table history) - in that case I used to enhance the standard level audit with additional information by implementing a custom history level. The goal is always to not produce lots of garbage in the process history you won't need. This is critical for performance. And process variables consume a lot of space.
Hence Camunda Optimize has restricted usage when it comes to mass data:
- When using the history level audit optimize doesn't show any process variables.
- Process variables are very important for analyzing the business context
After this preface, the goal of this feature request is very easily formulated:
- Please import process variables as well when using history level audit.
- Thus we get the last status of the variables - which is sufficient in most cases.