Implementing Notification Composer and Converting Existing Notifications

Once you adopt Notification Composer, you must use the component to create new notifications and manage your existing ones. As part of this process, you must convert some of your existing notifications to Notification Composer.

Notification Composer impacts notifications for these components:

  • Approval Workflow Engine

  • Activity Guide Composer

  • Questionnaire Framework

  • Forms and Approval Builder

  • Page and Field Configurator: Change Tracking

  • Notification Publisher

Approval Workflow Engine (AWE) Notifications

Existing AWE notification events must be assigned to Notification Event IDs. Oracle - PeopleSoft provides two conversion options for your existing AWE notifications:

  • Map to Delivered AWE Configuration: This option maps your existing Approval Workflow Engine notification events to PeopleSoft delivered Notification Composer events and related system data.

    If you included notification names for your AWE notifications, the name is assigned to the notification Event ID. If you did not include notification names for your AWE notifications, a name is automatically assigned based on existing event-level AWE indicators (such as whether the notification is delivered through email or pushed).

  • Preserve Existing AWE Configuration: This option maintains your existing AWE configuration, including custom-built and modified AWE notifications.

    In this scenario, a new Notification Composer configuration is created and the new Notification Composer data is linked to the existing AWE configuration.

To convert existing AWE notifications, start by applying Notification Composer updates through Change Assistant. The change package process automatically directs you to the AWE To EONC Conversion Page (AWE Notifications) page, where you can specify the one of the aforementioned conversion methods for your AWE notifications.

Both conversion methods migrate converted AWE notifications and Notification Composer configuration. The DataMover script EONC_IMPORT_MTP.DMS must execute in order to complete the conversion process. This step imports the converted data (which was exported from the target during Initial Pass) in the Subsequent and Move to Production passes.

Note:

The conversion process only needs to be completed once. After successfully completing the conversion process, you do not need to perform it again. You do not need to return to the AWE To EONC Conversion page.

It is important to include all AWE notification composer updates in your change package to ensure that all AWE configuration is properly converted.

Converted AWE notification data is populated into the following Notification Composer records:

  • EONC_NOTFY_HDR

  • EONC_NOTFY_HDRL

  • EONC_NOTIF_XREF

  • EONC_NOT_XREF_L

  • EONC_NOTFY_PREF

  • EONC_EMSBJ_BIND

  • EONC_EMSBJ_BNDL

  • EONC_EMAIL_BIND

  • EONC_EMAIL_BNDL

  • EONC_PUSH_BIND

  • EONC_PUSH_BNDL

In addition, the AWE records EOAW_NOT_USRAUX and EOAW_NOT_UDFAUX are populated.

Activity Guide Composer Notifications

Use the AG Composer Conversion to NC page (Activity Guide Composer Notifications) page to convert your existing Activity Guide Composer notifications to Notification Composer.

The conversion process:

  • Enables Notification Composer for Activity Guide Composer (sets the AGC_EONC_INSTALL flag to Yes in the AGC_INSTALL table).

  • Generates a Notification ID and corresponding Notification Event for existing notification text IDs that are defined in the AGC_CAT_NOT_DEFN table.

  • Generates a log you can use to review conversion details.

Note:

The conversion process only needs to be completed once. After successfully completing the conversion process, you do not need to run it again.

Questionnaire Framework Notifications

When you enable Notification Composer and create new Questionnaire Framework notifications, it accommodates Notification Composer functionality. For example, the Notification ID field on the Notification Designer Page provides Notification Event ID values from Notification Composer.

Forms and Approval Builder Notifications

When you enable Notification Composer, your existing Forms and Approval Builder notifications automatically accommodate Notification Composer notifications.

Page and Field Configurator: Change Tracking

When you enable Notification Composer and create notification IDs and notification events, you can associate them with a Change Tracking configuration type in Page and Field Configurator. This allows you to notify specific users when a change it made to information, from another user. For more information, see Understanding How To Use Notification Composer With Page and Field Configurator.

Notification Publisher Notifications

When you enable Notification Composer and create notification IDs and events, you can associate them with notifications for the landing page that are sent in Notification Publisher. This allows you to take advantage of Notification Publisher features, such as sending notifications immediately, on a specific date, on a recurring schedule, or with an expiration date. For more information, see Understanding Notification Publisher.