For my master thesis i am exploring how i can use the process engine for discrete event simulation. Thanks to its well designed interfaces this has thus far been gone without any major problems.
My intention now being to override all relevant timestamps as generated when the process is being executed in real time with simulated times. This will give the impression of a long running process.
The goal here being to be compliant with camunda optimize such that i can use this for analysis.
However, navigating the database has been a bit tricky and was hoping i could get some input on this…
Where and what data does optimize pull from the database? Would be very useful if i could get insight into what queries it executes.
I initially hoped that it would perform a clean import of the history tables after forcing the reimport script, but there is seemingly much more logic happening in the background.
I first imported all history and created a single report.
Then deleted a single row (process instance) from ACT_HI_PROCINST
(original process had 8 instances. After deleting it should have 7)
Then forced a refresh via the reimport script in camunda optimize.
To my surprise i am now told that this same process has 1 instances as opposed to the expected 7?
Would be great if i (and the community) could get some input as to how this is pieced together