Event actions
Event actions – sometimes referred to as 'actors' – are building blocks executing predefined actions, e.g. 'Send Mail' or 'Set value'. Event actions included in an event handler are only executed when the validation rules are passed. However, the 'rules' section is not the only level of an event handler that may contain logic. There are also 'logical' event actions (see Logic (Event actions)), such as the 'If then else' actor, which may define a simple logical condition or a complex cascade of cases.
The same category of event actions features the Abort, which interrupts the execution of events – e.g. depending on the result of a 'Benutzer Rückfrage' (another Logic (Event actions)) – and causes a roll-back of the whole transaction. Loops and variables are available to enable smart designs for complex workflows.
Event action configuration is represented graphically according to a simple set of principles, to provide a visualization of logical dependencies.
By 'Eigenes Aktionsevent auslösen (Aktion)', event handlers may trigger other event handlings, which enables the modular breakdown of complex processes.
Visualization
The following pages describe the most important event actions by categories resembling the context menu items in the software.
►NOTE◄ Availability of event actions may vary depending on the modules installed or licensed. Depending on context within an event handler, all available event actions are regarded as 'matching' or 'unmatching' (the context) and consequently appear either directly in a sub menu representing their category or in a virtual category 'Unmatching'. 'Unmatching' event actions are listed by category as the sub items of 'Unmatching'. If only a subset of the event actions in a category is regarded as 'unmatching', the category appears twice: in the context menu and as an item of 'Unmatching'. However, 'unmatching' event actions may be added to an event handler regardless of context, since later changes in the structure of the event handler might make them a useful choice.
In the following example, the validation rule (including Typprüfung, not visible here) returns a business object of the 'Manifest' type (see Manifests) as expected data context for event actions. Consequently, all event actions explicitly linked to other business object types are regarded as 'unmatching' and some categories move into the respective menu item:
