Extending the JpaWorkingMemoryDbLogger to record the order when events are triggered I receive a illogical order of events, where afterProcessStart is the last event in the event sequence when afterProcessCompleted would be the logical order.
Additional information: I'm trying to use the JpaWorkingMemoryDbLogger to keep track of my current process tree state to be able to show my users exactly where in the process/sub-process structure the processes is (process name/node name). The current BAM tables do not reflect this information as no hierarchy information between process/sub-process is kept in the tables. While trying to determine in which state of the event sequence I could access the relation between process and entering a sub-process or leaving a sub-process and returning to the superior process I came across the unorderly invocation of events.