L3 - Default When Zeebe variables are created, a record is exported to Elasticsearch, if configured correctly. Optimize should read, flatten and store these variables as properties of process instances. For consistency with engine data and to avoid a larger reconsideration of how Optimize handles variables, it is fine to treat all of these variable creations in the same way as variables from the engine, i.e. we can ignore their scope.
ATs:
- Variable creation records, regardless of scope, are converted to variables and stored as part of Optimize process instances
- These variables can be used for report filtering and evaluation
Hint:
- Complex variables might need to be skipped, in the same way that they are for the engine
- The types might need to be manually derived from the value