-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
AT:
- provide a default implementation of a composite history event handler such that users can more easily add multiple history event handler implementations to the engine
This is the controller panel for Smart Panels app
[CAM-2716] Composite History Event Handler
Labels | Original: EasyPick | New: AD EasyPick |
Fix Version/s | New: 7.3.0 [ 13391 ] | |
Fix Version/s | Original: 7.2.0 [ 12997 ] |
Fix Version/s | Original: 7.3.0 [ 13391 ] |
Fix Version/s | New: 7.4.0 [ 13505 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Remaining Estimate | New: 0 minutes [ 0 ] | |
Original Estimate | New: 0 minutes [ 0 ] |
Hello,
Can I also try to implement this ticket?
For example, I could implement 2 composite classes CompositeHistoryEventHandler and CompositeDbHistoryEventHandler inside the package org.camunda.bpm.engine.impl.history.handler.
Where:
Br,
Alexander