-
Type:
Feature Request
-
Resolution: Won't Do
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: engine
-
None
Context:
Optimize has a suspension filter feature that allows the user to include only those process instances in the report that have been suspended. In Optimize we use the user operations log to find out if a process instance has been suspended or not. We've already adjusted the operations log for the suspension of a process definition with CAM-11769. However, we realized that it's also possible to suspend process instances via a batch operation. While we found a workaround to cope with that problem we would still like to have a clean solution in the future.
The problem right now: when I suspend/activate process instances via the batch operation I only get the information on how many process instances were affected by this operation but not which process instances. It would be beneficial if the latter information is provided as well.
AT:
- The user operations log shows which process instances have been suspended/activated by a batch operation