Currently the /optimize/variable-update endpoints returns primtive as well as object variable updates along with their value. Variables of the object type can have a big overhead as they require separate byte array fetches as well as may increase response sizes significantly. However Optimize by default discards object variables on import. The goal of this task is to extend the API to allow reducing the overhead of object variable updates in cases where they are not needed by Optimize.
- To reduce overhead during the import of variable updates to Optimize, the Optimize REST API should offer means to control whether variable updates of the type object are fetched at all or alternatively whether their value is fetched and included in the response
- Ideally the change is backported to Camunda Platform 7.13.x & 7.14.x