Event Maintenance - Fields 
The following tables describe fields requiring explanation:
Field |
Description |
|---|---|
Event Activity |
The activity that is called when the event is logged. CONSEC_NC_HOLD_REL: Can place an operation or resource on hold when consecutive nonconformance codes are logged. SPC_VIOL_HOLD_REL: Can place an operation or resource on hold when an SPC violation occurs. SPC_WARN_HOLD_REL: Can place an operation or resource on hold when an SPC warning occurs. YIELD_HOLD_REL: Can place an operation or resource on hold when the yield is above or below the defined value. |
Severity |
The severity of the specific event type. Valid numbers are between 1 and 999998. The higher the number, the higher the severity. |
Subject |
Briefly describes the event. This text is stored in the database and is displayed in the following fields:
The subject entry can include replaceable parameters (see Replaceable Parameters). |
Field |
Description |
|---|---|
Address Type |
The address type of the event channel Explicit Address: An individual with a specific e-mail address. System User: A system user set up in User Maintenance. |
User |
The system user name to whom you want to send this event notification message. Note that this field is required only if the user selects the System User option from the Address Type field. |
Field |
Description |
|---|---|
Delivery Restriction |
The destination to which the real-time event notification message is sent. Operation: The specific operation or any operation to which you want to send this real-time event notification message. Resource: The specific resource or any resource to which you want to send this real-time event notification message. User: The specific user or to any user to whom you want to send this real-time event notification message. |
Display Text |
A detailed textual explanation of the event This text appears in the Message Text column of the real-time event notification message. It can include replaceable parameters. |
Field |
Description |
|---|---|
Filter Type |
Incoming: Filtering rule for handling incoming events. All Outgoing: Filtering rule for handling outgoing events. This rule applies to all propagation channels simultaneously and is eventually replaced by channel-specific filtering rules. Outgoing: Filtering rule for handling outgoing events. This rule applies to a specified propagation channel. |
Propagation Channel |
The specific propagation channel for the events. Note that this field is required only if the Outgoing option is selected. |
Exclude or Include Events |
The attribute filter that describes the filter rule. Include One: Includes events having a severity that is greater than or equal to the value specified in the Severity field. Exclude One: Excludes events having a severity that is less than or equal to the value specified in the Severity field. Note that you must enter data in the Attribute Name and Attribute Value fields. Include All: Includes all events, regardless of severity, and disables the Attribute Name and Attribute Value fields. |
Attribute Name |
The name of the ALARM_LOG attribute to which the filtering specification is applied. |
Attribute Value |
The specific value of the attribute filter selected in the Attribute Name field. Note that information entered in the Attribute Value field is case-sensitive and must match the database value exactly. |
Field |
Description |
|---|---|
Require Cause for Clearing |
If selected, you must enter a cause in the Cause field on the Event Log screen in Event Viewer before clearing the event. |
Use Auto Delete Interval |
If selected, allows you to delete cleared events at the specified time. Deleting an event removes the event from the database. Note that you can delete only cleared events. |