Is your feature request related to a problem? Please describe.
As an integrator I'm used to listen to events in order to understand if certain UI changes happen. I use these events to enable or disable certain global actions (cf. Camunda Desktop Modeler).
Unfortunately the FEEL popup is currently burried (interaction wise) deep in the properties panel, and gives me no chance as an integrator to understand if it is open, closed, or otherwise interact with it.
Describe the solution you'd like
I'm able to understand if the FEEL popup state changes, via events:
Is your feature request related to a problem? Please describe.
As an integrator I'm used to listen to events in order to understand if certain UI changes happen. I use these events to enable or disable certain global actions (cf. Camunda Desktop Modeler).
Unfortunately the FEEL popup is currently burried (interaction wise) deep in the properties panel, and gives me no chance as an integrator to understand if it is open, closed, or otherwise interact with it.
Describe the solution you'd like
I'm able to understand if the FEEL popup state changes, via events:
Additionally I want to introspect + interact with the FEEL popup via API:
The later would expose the feature in a way that complies with our core modeling patterns.
Describe alternatives you've considered
None.
Additional context
None.