Create ability to control what events are collected by collector. - Githubissues

holunda-io / camunda-bpm-taskpool

Library for pooling user tasks and process related business objects.

https://www.holunda.io/camunda-bpm-taskpool/

Apache License 2.0

67 stars 26 forks source link

Create ability to control what events are collected by collector. #801

Closed zambrovski closed 1 year ago

zambrovski commented 1 year ago

Scenario

camunda-bpm-taskpool version: 7.10.0
Camunda BPM version: 7.18
Description of your use case: Currently, if camunda-task-collector is activated, it will react on all Spring Events fired by the engine (both direct task lifecycle events and historic events). There should be a way to configure which events are collected, and which not.

Current Behaviour

All events are collected.

Wanted Behaviour

I want to configure collected events based on event name.

Possible Workarounds

None.