Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
M
Description
Context:
This is an optimization follow-up to https://github.com/camunda/camunda-optimize/pull/1643 where definition xml's are parsed on demand to derive flow nodes along with their type, id and name.
To make this more efficient we could instead of just storing the flowNode id's on the processDefintionDto also store the type and name.
AT:
- on process definition import the available flow node id, name and type are extracted from the xml and stored as a property of the processDefintionDto
- the `CamundaEventService` makes use of these properties instead of parsing the xml on demand to extract this information
- add ProcessDefinitionImportIT, which makes sure all data is valid