Event types

* New for 9.5 *

An event type is the definition of a situation that can occur. A unique name identifies each event type. Event types can be active or inactive on a server and can be used only when active.You can use the following event types:

  • Service-defined events: Services can provide events and appears in the Events view when the service is activated.

  • Custom events: You can create these event types using Workbench. It is useful to create an event type if an existing one does not meet the requirements of your process.

When an event occurs at runtime, use event types to provide a notification about the occurrence of the event (throw the event) and to receive the notification (receive or catch the event).

Event notifications carry data with them so that information about the event is communicated by the event thrower to the event receiver. Events distinguish between two types of data:

Event data:
A small set of discreet data items that event receivers use for decision-making purposes.

Event message data:
The payload of asynchronous events is in the form of a larger amount of XML data. Typically, this data either cannot be altered during the process because it is a document of record or the process requires the XML document structure to be validated. For example, the process for a company’s internal purchase order request throws an event when a purchase order requires approval. The event message data is the original purchase order form that needs to be approved.

// Ethnio survey code removed