Notification Services Data Model

The Notification represents the data for a Notification. This includes the Recipient(s), type of message, and data for the message. The dto is delivered to the NotificationService as part of the NotificationRequest.

A client passes in a Notification instance into the NotificationService#sendNotification() method. The service uses a NotificationHandler to populate key properties on the notification including the messageBody which is typically populated by taking the Notification#data and using it within a template.

A Recipient refers to who the Notification will be sent to (email or phone). Typically, a transactional message has a single recipient. Multiple recipients are supported by some providers and email providers allow recipient’s to be flagged as cc or bcc. A Notification represents a single email. If an implementation wanted to bulk send notifications as part of a campaign, each target would need to use a different Notification and Recipient.

A Sender refers to who the Notification is coming from (email or phone). Typically, Sender information would be configured as part of the NotificationSender setup, although the system by default will try to send on behalf of the sender set on the Notification if one exists.