Designing Notification Types

Some notification types require a specific configuration in order for the system to create notifications for that type.

Service Task Based Notification Types

There are system processes that rely on a hard-coded notification type lookup, referred to as notification type (legacy) on the notification type configuration. The system identifies the user-defined notification type from the lookup value.

The following identifies the configuration requirements for the notification types that are supported by existing processes in the system that rely on service tasks.


Notification Type (User Defined)	Push/Subscription	Controlled By	Notification Type (Legacy)	Service Task Type
Prepaid billing new charge	Subscription	Service Task	C1PC	Self-Service Task Type with BO C1-NotifyTaskType
Prepaid billing payment request	Subscription	Service Task	C1PP	Self-Service Task Type with BO C1-PPBPaymentNotifyTaskType
Payment Received	Subscription	Service Task	WSPR	Self-Service Task Type with BO C1-NotifyTaskType
Bill Ready	Subscription	Service Task	WXBR	Self-Service Task Type with BO C1-NotifyTaskType
Bill Due	Subscription	Service Task	WXBD	Self-Service Task Type with BO C1-NotifyTaskType
Late Payment	Subscription	Service Task	WSLP	Self-Service Task with BO C1-NotifyTaskType

Non-Service Task Based Notification Types

The following identifies the configuration requirements for the notification types that are supported by existing processes in the system that rely on the user-defined notification type to be configured.

Note:

Marketing and forms notification types can be set up one of two ways: as subscription-based or as push-based. For it to be push-based, it would be an individual push, meaning that it references a parent push notification type specified by the implementer.


Notification Type (User Defined)	Push/Subscription	Controlled By	Notes
Marketing Preference (Lead Event)	Subscription or Individual Push	N/A	Notification type configured on lead event type of BO C1-LeadEvtTypeNotificationPref
Forms Update	Subscription or Individual Push	N/A	Notification type configured on form task type of C1-FormTaskTypeForNotification
Forms Closed	Subscription or Individual Push	N/A	Notification type configured on form task type of C1-FormTaskTypeForNotification

Bill and Quote Routing

Notification types can also be used to define contact preferences for bill and quote routing for email and fax. This can enable a bill or quote to create a routing for each active contact preference. For example for a single person on an account that receives a copy of the bill, the bill can be sent to more than one email address.

Some specific configuration is needed to support this.

The notification types are to be set up as follows and must use the message-based notification type business object.


Notification Type (User Defined)	Push/Subscription	Controlled By	Bill/Quote Route Type	Algorithm
Bill Route	Subscription	Bill Route	Specify the Bill Route Type	Use the Suppression Algorithm for Bill/Quote Route
Quote Route	Subscription	Quote Route	Specify the Quote Route Type	Use the Suppression Algorithm for Bill/Quote Route

Configure only the delivery type that corresponds with the bill or quote route’s routing method. For example, if the bill route type’s routing method is email, configure the email delivery type on the notification type.

Configure only person contact types whose contact routing corresponds with the bill or quote route’s routing method. For example, if the bill route type’s routing method is email, configure only person contact types with a contact routing of email. Ensure that the person contact type allows only the delivery type specified on the notification type.

This very specific configuration is needed because the system will override the existing logic that creates bill and quote routings when a notification type exists as described above and there are active contact preferences for that notification type with the specified delivery type and the person contact’s person contact type.

Collection Events

The system is delivered with a collection event algorithm type that supports template-based notifications. To send collection based notifications, define individual push notification types for each collection notification. These notification types should reference a parent notification type such as “Collection Notices”. Configure algorithm(s) using the delivered algorithm type, specifying the individual push notification type(s) in the algorithm parameter. Create collection event types using these algorithms and incorporate them into your collection process templates.