Object to which is given event related. It can be a PrismObject or any other object (Item, PrismValue, plain Java object, or even a collection of objects).

adHocHandler

Event handler that should be used to process this event.

These custom events can be processed in one or both of the following ways:

Using standard notification configuration in system configuration object. I.e. they might be filtered and eventually translated into messages using a notifier. Because no out-of-the-box notifier exists for custom events, a generalNotifier has to be used. This notifier has to specify the recipient(s), subject, and body of created message.

Using ad-hoc event handler, specified within the event itself. Definition of this handler is exactly the same as definition of handlers in system configuration.

When a custom event is processed, first the ad-hoc handler is used (if present), followed by handler(s) from the system configuration object.

How to submit custom events

Using bulk actions

In order to easily send custom events there is the notify scripting (bulk) action. It takes the input from the pipe - usually a list of PrismObjects - and creates an event for each one of them. (Alternatively, for the whole list, if forWholeInput parameter is set to "true".)

The following parameters are available:

Parameter

Meaning

subtype

Subtype of the event created.

operation

Operation to be put into event (add, modify, delete). Default is "add".