[filiphr]

The variables of the process instance, historic process instance, task, historic task, case instance, historic case instance, plan item instance and historic plan item instance queries that include variables did not have the process or case definition id, so code that needed it for such a variable had to fetch the instance again.

• The queryVariables collections of these queries now map the process definition id (BPMN) or the scope definition id (CMMN) of the instance to the variables, and use VAR_ID_ as notNullColumn, so an instance without variables gets an empty collection.
• HistoricVariableInstance exposes getProcessDefinitionId() and getScopeDefinitionId(), like VariableInstance. They are not persisted and are also copied from the runtime variable when the historic variable is created or updated.
• The task and historic task queries without included variables use a result map with only the identity links.
• The CMMN task sets the scope definition id on its local variables, like the process definition id for BPMN tasks.

Check List:

• Unit tests: YES
• Documentation: NA