While this table does not have a field defined as a primary key, the ALERTID field should be unique and considered a primary key.
The ALERT table stores information about alerts that are assigned to urgency codes. An alert specifies the time period when action should be taken on an overdue ticket. Alerts are created using the Administrator. The tables stores information such as the urgency code ID, alert description, delay time, and the message that appears in the e-mail for the alert.
|
|
While this table does not have a field defined as a primary key, the ALERTID field should be unique and considered a primary key. |
| Field | Datatype (Length) | Allow Nulls | Indexes | Relationship | Related Table and Field |
|---|---|---|---|---|---|
|
ALERTID |
STANDARDID |
NOT NULL |
ALERT_ALERTID_PK (CA) |
(One) to (Many) |
|
|
(One) to (Many) |
|
||||
|
URGENCYCODE (FK) |
STANDARDID |
NOT NULL |
ALERT_URGENCYCODE (IE) |
(Many) to (One) |
|
|
DELAY |
float(8) |
NULLS |
|
|
|
|
DESCRIPTION |
varchar(255) |
NULLS |
|
|
|
|
CREATEUSER (FK) |
STANDARDID |
NULLS |
|
(Many) to (One) |
|
|
CREATEDATE |
datetime |
NULLS |
|
|
|
|
MODIFYUSER (FK) |
STANDARDID |
NULLS |
|
(Many) to (One) |
|
|
MODIFYDATE |
datetime |
NULLS |
|
|
|
|
EMAILMSG |
varchar(128) |
NULLS |
|
|
|