-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
Feature Description:
- * given:
- I have created some process instance data, e.g. a bunch of process instances started, suspended, activated and completed
- when:
- I request the historic instance data sorted by modification date
- then:
- I get the historic process instances
- each entry contains the date of its last modification
- such that:
- Optimize is able to import the historic process instance data in a way that can catch changes in the process instance state (e.g. a suspension of the process instance).
AT's:
- the historic process instance table stores the last modification date
- whenever there's a change of the process instance change, it's persisted to the database (e.g. suspension, activation)
- the modification date feature works for batch operations as well
- the historic process instance endpoint adds the modification date to the response
- there is an index on the modification date that allows fast sorting and retrieval of the historic process instances
- Backported to all maintained versions
This is the controller panel for Smart Panels app
[CAM-11898] Historic process instances contain modification date
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2339. Please use this link for any future references and continue any discussion there.
andre.bappert: It would be great for Optimize if we could add this ticket to the 7.14 roadmap. Some context: In Optimize, we have a feature that allows the user to filter the process instances by their suspension state. We use the user operations log to extract the information if a suspension state of a process instance has been changed. However, for batch operations, this is not possible and I created
CAM-11785to fix this problem. After talking to thorben.lindhauer, we decided to not go forCAM-11785since it would be too complicated and do this ticket instead. Right now, we work around the problem by starting the import of the running process instances from scratch whenever there is a bulk operation on the suspension state of process instances. While this should work for now it's far from being optimal because we import the same data several times. If you have any further questions regarding this issue feel free to reach out to me at any time