Some Notification Types Use Service Task
Prior to the introduction of notification preferences functionality, the system supported notifications set up through self-service. These notifications used service tasks to store customer preferences and in some cases trigger notifications. The destination information for the notification existed outside of the system. Notification preferences, and more particularly communication preferences, define the user’s preferences on how to be notified for each notification type and where the notification is to be sent. This reduces, but does not eliminate, the need to use a service task to store a customer’s preference. These service tasks will not contain the self-service information when created internally by the system
There are four existing notification types that rely on service tasks to trigger a notification. Additionally, one of the prepaid notifications uses a service task type business object with specific fields for that notification type. Refer to
Designing Notification Types for information regarding the configuration requirements for certain notification types.
Notification Preferences supports configuring notification types with or without a service task and only subscription-based notification types can be configured with an underlying service task.
Parent topic