Event Type Properties

For each FSM event type, the following properties can be set:

Table 1. FSM Event Type Properties
Property	Database Table and Column	Description
Name	EVENT_TYPE. TYPE	The name of the event type is a code that contains a maximum of twenty characters. By convention the first two characters are "E_". For example, E_MpInTxnMapped.
Log Event Flag	EVENT_TYPE. LOG_EVENT_FLAG	Indicates if events of this type are persisted in the database as follows: Y Events are persisted in the database T Only events that cause a state transition for an object are persisted in the database Anything else Events are raised and processed without being persisted in the database Note: Be careful, because events that are not persisted are not viewable in the web-based Operation and Administration Console.
Render As Message	EVENT_TYPE. RENDER_AS_MSG	If set to Y, events of this type, when raised, are placed on the events queue to be picked up by the event processing flow. Otherwise, raised events will be processed "in-flow", that is, they will be processed in the same thread of execution (and unit of work) as where they are raised. Processing events in-flow has obvious performance benefits over putting events on a queue for asynchronous processing. However in-flow processing implies a wider transaction which, if rolled back, will undo work associated with earlier events processed in the same flow.
Aggregation Threshold	EVENT_TYPE. AGGREGATION_THRESH	The maximum number of events that can be aggregated onto an event of this type.