Currently it can happen that no camunda event data is available but users use camunda process data sources in an event based process. This leads to errors on publish as the expected activity event indices do not exist.
The configuration of the event based process feature itself and the camunda engine event import got decoupled with
OPT-3370 to save the camundaEvent import overhead if not needed as well as to support cluster environments. However this can lead to unexpected behavior when a user activates event processes but not the camundaEvent import and then tries to use camunda sources in event based processes. (Publish get's stuck, failures of missing indices are thrown)
- it should not be possible to include camunda event sources if there are no particular activity indices present
I create a process I can select camunda processes as sources and publish the process.
The publishing get's stuck, the log contains errors about missing indices.
I shouldn't be allowed to select camunda processes
We can't rely solely on the configuration as in cluster setups the event import might be disabled for a particular instance but the data is still imported by another.
This is the controller panel for Smart Panels app
|Add definition key endpoint query parameter||Done||Unassigned|
|Remove exclude event process flag from definition key endpoint||Done||Unassigned|
|Use the Camunda query parameter when fetching definition keys for event based processes||Done||Unassigned|
|Prevent adding event sources where camunda events have not been imported||Done||Unassigned|
|Update event based process documentation with reasons for presence of definition keys||Done||Unassigned|