- Issue created by @DamienMcKenna
- 🇩🇪Germany jurgenhaas Gottmadingen
This is a difficult one. Building ECA models does not always know about any context. Let's say you just create an action in the bpmn_io canvas, not being linked to any predecessor yet, i.e. not connected by any arrows. When building the config form for the property panel, the system doesn't know which tokens will be available, so it's impossible to provide a list of available tokens.
The same is true for later changes. The model building process is often such that plenty of changes are made, and each of those changes can have an impact on the context for each of the action contained elsewhere in the model.
Often, we only really know at runtime, i.e. when the model is executed, what tokens are available when processing an action. And that can even be different each time the same model gets executed.
With that in mind, while we can certainly see the wish for a more user-friendly UI in this situation, it's very hard and often times even impossible to do.
Instead of doing nothing, I can only see to improve the user experience by adding more detail and samples to the documentation.
