Show TOC

Function documentationCustomizing of Notification Framework

 

In Customizing of the Notification Framework, you can establish your customer-specific requirements.

Features

  • You can define the business object types for which you want to make the Notification Framework available.

  • You can define the conditions that you want to make available for the creation of subscriptions. You can enhance the conditions of the standard by customer-defined conditions or create a customer-specific set of conditions.

  • You can implement customer-specific methods for the following steps of the subscription processing.

    Example Example

    • Checking the conditions that are defined in the subscriptions. The system processes these methods when a subscription is saved.

    • Sending of the notifications with the different communication channels

    End of the example.
  • You can create forms that you can make available for the communication channels. The forms can contain standard texts and placeholders that are dynamically filled by the system.

    Example Example

    You want to send an e-mail with the following text in case an incident has changed:

    Dear subscriber of subscription <ID> <DESCRIPTION>,

    please be informed that the incident <ID> <DESCRIPTION> has been changed.

    <DATE> <TIME> <USER-NAME>

    End of the example.

    If required, you can create forms that refer to the different conditions and subscribers that you define in your subscriptions. When creating a subscription, you can select a form that contains the appropriate standard text.

    Note Note

    For creating e-mail and SMS forms, you can use the attribute context Notification Framework. It contains the following attribute categories:

    • Service request attributes

    • Notification framework attributes

    • Processing time attributes to inform about reaching or exceeding a threshold. For more information, see Management of Processing Times.

    End of the note.
  • You can define defaults that are to be used when a user subscribes directly to a service request.

Activities

  1. Make the subscriptions available for the required business roles (UI component CRM_NOTIF_S, View CRM_NOTIF_S/NFSearchQueryView).

  2. Maintain the authorizations and assign them to your user roles.

  3. If required, set up the communication channels that you want to use.