Recipients and Recipients Editor Tab
A recipient is a person, device, location, or group that is notified by a message (text, audio, and multimedia) or a live announcement from Notification.
Notification informs people about disruptions during Emergency Events, by addressing notifications to recipients. Notification launches notifications from pre-configured notification templates, either in the form of messages or live announcements. Recipients are added to message templates and live announcement templates. Notification delivers the notification content to the devices through which those recipients can be reached.
There are four types of recipients:
- Recipient users
- Recipient groups
- Recipient devices
- Recipient locations
Recipient users represent persons who will receive messages from Notification through one or more recipient user device types.
Recipient user devices are the personal communication devices that receive notifications for the corresponding recipient users. Recipient user profiles contain personal contact information, information about one or more personal communication devices, and the preferred delivery method for those devices. Some of the recipient user device type examples are listed below:
- Home phone
- Personal email
- Personal mobile phone
- Work email
- Work mobile phone
- Work pager
- Work phone
Each recipient user device type supports one or more delivery methods. Each of the delivery method is mapped to a modality supported by a handling driver. Modality is the mode through which messages are transmitted by Notification. Notification drivers support one or more modalities to send messages. By configuring the handling driver and modality used to deliver notifications to a particular device type and delivery method, the path can be selected through which the notifications will be sent. For example, the SMS delivery method of a mobile phone recipient user device type can be configured to be sent through the SMS modality of a bulk notification driver, or through the SMS modality of a GSM modem driver.
When the system launches messages, the configured recipient user device types, preferred delivery methods, associated driver instances, and modalities are considered for routing the message to a recipient device.
The devices to which a notification is sent and the notification's delivery methods are selected based on user preferences and delivery mode settings.
The languages in which recipient users can be notified are configurable, and each recipient user is configured with a preferred language. Recipient languages are configured with a culture (required for proper formatting of number, dates and times) and with speech voices (required for conversion of text to speech and speech voice is available only for MNS license users).
Additional recipient languages may be configured at any point in time. However, if it is necessary to remove or reorder recipient languages, it is strongly recommended to only perform this immediately after project creation and before the remaining project is engineered (drivers, devices, incident templates, notification templates, and so on) to maintain consistency of recipient language-specific properties like message content.
Additional recipient user device types may be configured at any point in time. However, if it is necessary to remove recipient user device types, it is strongly recommended to only perform this immediately after project creation and before recipient users and their devices are added to maintain data consistency within the project.
If any recipient language is added, edited, reordered, or removed, restart the Desigo CC application to view the changes.
Drivers and devices of certain types might require additional configuration steps after changes in the recipient language configuration. Please refer to the respective device Help for more details.
Bulk importing of recipient users is possible with the import feature that allows importing a .CSV file, an XML file, or an Active Directory. Similarly, exporting and saving the information of the recipient users as a CSV file or an XML file is possible.
NOTE:
Recipient users can receive text, audio, and multimedia messages. However, live announcements cannot be received by the recipient users.
System users can be given recipient user profiles to allow Notification to send messages to those users as well.
For more efficient management, group multiple recipients into a recipient group. Recipients can be members of multiple groups. Also, nest recipient groups by adding one recipient group to another. When Notification sends a notification to a recipient group, the notification is sent to all recipient users and recipient devices within that recipient group and its contained recipient groups.
NOTE 1:
Circular references in groups that include each other are not possible.
NOTE 2:
Recipient groups are system-wide: Every operator sees the same groups.
The operator can create a personal contact list. A contact list is a list of preferred recipients that a user can define similar to favorites in a web browser. When a operator has to select recipients, for example, to add them to a notification, you can choose the recipients from the personal contact list, too. The difference between a contacts list and a recipient is that recipient groups are defined system-wide, meaning that all operators see the same groups, whereas each operator has their own, personal contact list, which is not visible to others.
NOTE:
Contact list is available for Reno Plus and MNS license users.
Recipient devices represent notification devices connected to and controlled by Notification
Recipient locations associate recipient devices with physical or logical locations. Locations are typically organized as trees with buildings, floors and rooms. Recipient locations are aggregators in the System Browser that are explicitly configured to be recipient locations in Notification. When Notification sends a notification to a recipient location, the notification will be sent to all recipient devices associated with that location and sub-locations.
For related procedures or workflows, see step-by-step section.
