It is possible to start a process in response to an event being raised. This requires the setup of some configuration data (either through an administration interface or as pre-configured database entries). The configuration specifies the process/processes to start in response to a specific event being raised. Mappings of event data to the enactment data required by the process can also be configured in this way.
Process enactment event configuration is stored on the database and a user interface is supplied to allow the manipulation of this data. As such process enactment created in this way can be enabled, disabled, changed and even removed at runtime. The main drawback of this approach is that since events have a finite amount of information, only process definitions that require such a small amount of enactment data can be enacted in this way.
A Process Enactment Event Handler is supplied with Cúram and is automatically registered to listen for events raised in the application. Where a process has been configured to be enacted from an event, the data from the event is mapped into the enactment data of the process, and the process is started.