Event Context Properties
For each type of event context data, the following properties can be set:
| Property | Database table and column | Description |
|---|---|---|
| Context Type | EVENT_EXP_CONTEXT. EVENT_CONTEXT_TYPE | The type of context data that is expected in events of this type. Some examples are TRANSACTION and TRANSMISSION. |
| Cardinality | EVENT_EXP_CONTEXT. CARDINALITY | The number of items of this context type that are expected in events of this type:
|
| Aggregatable Flag | EVENT_EXP_CONTEXT. AGGREGATABLE_FLAG | If set to Y, this context type may be used to aggregate this event type. Event aggregation can occur when an event that is raised is the same as another raised event with the sole exception of a difference in the aggregatable context data. In this case, it is possible that the context data can be added to the existing event of the same type instead of raising a new event. In this way, the two events are aggregated into a single event. Event aggregation is a performance mechanism. For example, a batch containing 80 transactions is mapped to ISF. Rather than having 80 E_MpInTxnMapped events, one for each transaction, there could be a single E_MpInTxnMapped event containing all 80 transaction IDs in its context data. |