| Name | Helptext Description | Data Type | Len | Codetable |
|---|---|---|---|---|
| INR | Internal Unique ID | Text | 8 | |
| USR | User (Optional Field, when SSNINR Specified) | Text | 8 | |
| SSNINR | Session ID to Address Sessions (Optional Field) | Text | 8 | |
| TYP | Type of Notify Entry | Text | 1 | Embedded |
| DATTIM | Timestamp of Issue | Datetime | 15 | |
| EXPDATTIM | Timestamp of Expiry | Datetime | 15 | |
| TXT | Text of Entry | Block | 60 | |
| SHWDATTIM | Timestamp when Processed | Datetime | 15 | |
| SHWSSNINR | Session ID where Processed | Text | 8 | |
| SHWFLG | Processing Mode | Text | 1 | Embedded |
| INIUSR | Creating User ID | Text | 8 | |
| INISSNINR | Creating Session ID | Text | 8 | |
| VER | Version | Text | 4 |
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
Defines the user to whom this message is to be sent. If this field is empty, the Session ID field has to be specified. Once this field is filled, any session relating to that user will process the notify message, providing the user remains logged in until this notify message expires.
The ID number of the session to which this notify message was sent. If the field is empty, the User ID field has to be specified. If the field is filled, it specifies the session assigned to process the notify message.
This field identifies the entry type. This type then determines how the received message is displayed. Icons displayed may vary and, depending on the severity, the notifier may sound an alarm and/or a warning will pop up.
| Code | Text |
|---|---|
| 1 | Emergency |
| 2 | Alert |
| 3 | Critical |
| 4 | Error |
| 5 | Warning |
| 6 | Notice |
| 7 | Info |
| 8 | Hint |
| C | Close transaction |
| U | Update session status |
| X | Exit session |
| 9 | Debug |
This field holds the date and time when the entry was made. The date and time of the application server is taken.
When issued, an expiry date/time can also be defined to limit the life of a notify entry. If such a limit is issued, the date and time of expiry is stored here. Entries with expiry dates in the past can still remain in the database, but the notify routine will no longer prompt the user.
The notify text to be shown to the user.
The field identifies the date/ time when this notify entry was processed.
The session, identified by its ID number, which processed this notify entry.
Non-empty values in this field identify entries that have already been processed and are no longer displayed automatically. 'Expired' means that at the time of processing the expiry time has already passed. In this case, the only action is to update the notify entry and mark the entry as expired. 'Processed' shows that the actions requested (Update Session, Return to Menu, or Logoff) have been initiated. 'Sent to Notify' means that the notify message has been sent to the user's notifier.
| Code | Text |
|---|---|
| Pending | |
| X | Expired |
| N | Sent to Notify |
| P | Processed |
The user creating this notify entry is identified in this field by the User ID.
The session which created this notify entry is identified in this field by the ID number of the session.
This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.