Understanding Notification Setup

The Notification setup steps are:

  1. Use the Notification Registry page to identify the notifications to be used and to enable any overrides at the system or business unit levels. In addition, the Notification Registry page can create custom actions or allow a pre-processing user exit.

  2. Use the System-Level Notifications page to override information from the message that determines who should be notified (user, user role, email address, or node) and how they should be notified (worklist, email, or XML notification). You can also disable worklist, email, or XML notifications. These overrides are applied for the process name and process category combination to the entire PeopleSoft system.

  3. Use the BU-Level Notifications page to override information from the message that determines who should be notified (user, user role, email address, or node) and how they should be notified (worklist, email, or XML notification). You can also disable worklist, email, or XML notifications for a specific business unit. These overrides are applied for the process name, process category, and business unit combination. Values at the business unit level override any system-level overrides.

  4. Set up and activate the EOEN Notify Message to enable the PeopleSoft Integration Broker to send a message to a third-party system using a XML-formatted messages.

Additional steps are necessary if you are modifying a PeopleSoft process to generate new messages or are using PeopleSoft Query to monitor PeopleSoft tables.

Understanding System and Business Unit Level Overrides

A notification message includes values used to build the message, such as:

  • Where to log the message (any combination of the Notification Dashboard, PeopleSoft Worklist, email, and XML notification).

  • A message set and message number. (optional)

  • User roles, user IDs, email addresses, or PeopleSoft nodes needed to route the notification message to the correct location.

  • Links to the PeopleSoft page where the transaction can be viewed or corrected.

The values are obtained from the PeopleSoft process generating the notification or in the case of Alerts from the Alert Setup component, BU-Level Notifications page, and System-Level Notifications page.

For notifications that are not Alerts, you can override the values from the initial PeopleSoft process in order to accommodate a temporary change or permanently provide more specific values using:

  • System-Level Notifications page.

  • BU-Level Notifications page.

System-level notifications are defined by the process name and the category and enable you to override the notification for the entire system. For example, if Bob receives all of the notifications for the OM_PEGGING / RECEIPT process and he goes on an extended vacation, you can set up an override at the system level to route all of these specific messages to Steve.

Business unit-level notifications are defined by the process name, the category, and the business unit and enable you to override the notification at the business unit level. For example, if the notifications for the OM_PEGGING / RECEIPT process need to be specific to the inventory warehouse, you can set up an override at the business unit level to route all of the messages for business unit US001 to Steve and to route all of the messages for business unit US008 to Ralph.

When you set up system and business unit level notification overrides, you determine who should be notified when a notification occurs and how they should be notified. As with most default hierarchies in the PeopleSoft system, the more specific information overrides the more general information. In this case, if values are defined at both levels for the same process name and category, then the values defined at the business unit level (BU-Level Notifications page) override the values defined at the system-level (System-Level Notification page).