...
Universal Events can be defined:
Globally | In a Universal Event Template. |
Locally | As part of a Universal Extension-based Universal Template. |
If the Universal Extension can generate a non-global Universal Event, you must define the Universal Event here to allow the event to be monitored by an Universal Monitor.
...
Field Name | Description |
---|---|
Name | Name of this Universal Event. |
Label | User-friendly display name for this event, to be displayed within the client. The Label must be unique for Global Events and unique within Local Events.. |
Description | Description of this event. |
Time To Live | Default value for the length of time, in minutes, that the Universal Event data is valid. This value can be unspecified (null). The Time To Live value can be overridden in the published event. If the Time To Live does not exist in the published event, then this value, if defined, will be used. If neither value exists, the Time To Live is 0, which means the event is deleted as soon as it is published. |
Unmapped Attributes Policy | Defines how unmapped/unknown attributes that are in the published event are handled.
|
Attributes | Name, Label, and Type of each attribute.
|
System Event | Indication if this type of event is a System Event. |
Auditing Universal Events
The Universal Event Extension Publish Audit lets you specify whether or not an audit record is generated for each Universal Event published through an Extension-based Universal Task Instance.
(The Universal Event Web Service Publish Audit lets you specify whether or not an audit record is generated for each Universal Event published through the Universal Event Web Services.)
Note | ||
---|---|---|
| ||
Enabling these audit properties can generate a large quantity of audit. |