Overview
This is an old version of the documentation for Flowable until version 3.13 and for the Angular-based Flowable Design 3.14/3.15. If you are running the latest version of Flowable please check out the current version of this page.
Flowable ships with an "event registry" which handles and manages two types of models of importance for this guide:
- event model: a model describing the data structure of the event data.
- channel model: an abstraction of receiving or sending events using a transport mechanism.
Like any model in Flowable, an event or channel model gets deployed (and is queryable) as a definition. Like any other definition type (process, case, action, template, etc.), it is versionable.
This is especially important for channel definitions, which are linked with a real listener that needs to be instantiated or removed. For example, a channel model linked to a JMS queue will create the listener at runtime when the channel model is deployed. Likewise, it will remove the listener when the definition is removed or a new version of the definition is deployed.
