Table 1 summarizes the data a message consist of.
Datum |
Description |
Sender |
The sender of a message. Each message is linked to the Redbex user who sent that message. |
A list of system internal recipients. While you can address messages to users and user groups, user groups are expanded automatically when the message is sent. For each recipient the system also stores a flag that defines if that recipient has to acknowledge the message. |
|
A message can have external email recipients. While Redbex can of course not support acknowledgment and other advanced messaging features for external recipients it might be useful to directly send messages to email |
|
Subject |
A text template used for the subject of the message. Unicode text up to 400 characters. |
Body |
A text template used for the message body. Either plain Unicode text or HTML encoded text. No length limitation. |
Source context |
Describes the context in which a message was created. The context is automatically set by Redbex and cannot be changed by the user. It is however available as a filter in Message forwarding. Following contexts are used: •Undefined •User to User: Set when a user manually sends a message (via used client Software) •Observation monitoring: Set when a message is created from a message action in observation monitoring •Observation Plan: Set when a message is created during the evaluation of observation plans. •Message Acknowledgment Notification: Set when a message is sent as result of a message acknowledgment. |
Severity of the message defined by the sender. |
|
Files that are attached to the message. There is no limit to the number or size of attachments. However delivery of attachments via email is usually limited. |
|
Acknowledgment information |
Includes the acknowledgment due date and a setting that defines if the sender gets notified whenever a recipient acknowledges a message. |
Read marks for each recipient |
Table 1: data stored with messages.