Processes - Subsequent events

There are various events that can trigger a process. By default, an event handler reacts to all events. By using the options in the properties of the event handler, you can restrict the number events so that the process is not triggered in every single case.

External events

Normally, an event is triggered extrernally. Examples of such an event are: creating, editing, or deleting a data record in the web, an event triggered at a specific time by a timer, or a user-defined event which is triggered via JavaScript when a button is clicked on.

Internal events

Internal events are only created when the action Include processes is performed. If a Include processes action is part of a process and configured for these 1-n processes, then when this action is performed, 1-n so-called internal events are generated which trigger the individual processes.

Primal event / Subsequent events

As part of the execution of a process which is triggered by an event ("primal event"), additional events, so-called subsequent events, can occur which can then trigger other processes.


A data record is created in data group A in the browser. The first event is generated for the addition to data group A because of this. A data group event handler monitors additions to data group A and creates a new data record in data group B via a data group action. If the option Activate subsequent events is activated in the data group action, then a so-called subsequent event is generated when the data group action is performed, adding a record to data group B in this case. With another event handler, which monitors additions to data group B, you can react to this subsequent event and perform additional actions.