Details
-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
Description
In order to support Camunda events in Optimize, we need to write activity instances to a dedicated index rather than as a nested property of a process instance. Considering we already page through these engine events for this purpose, we might be able to modify the existing importer to add this additional behaviour. We need to store as much information as we will need to be able to create instance events from.
AT:
- A new index exists to store all activity instances imported from the engine
- We page through completed activities from the engine and store them in the new index
- We only store events that can be mapped:
- start events
- end events
- intermediate events
- tasks (send, receive, user, manual, service, script, call activity, sub process)
- task activities we split-up into two events being *Start and *End