Prerequisite: Converting Existing Notifications to Notification Composer
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. Conversion processes must be completed for Approval Workflow Engine and Activity Guide Composer notifications.
Note: The conversion process only needs to be completed once. After successfully completing the conversion process, you do not need to perform it again.
Pages Used to Convert Existing Notifications to Notification Composer
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
EONC_AWE_RUN |
Specify the conversion method for your existing AWE notifications. |
|
|
AG Composer Conversion to NC page (Activity Guide Composer Notifications) |
AGC_CNVTONC |
Convert your existing Activity Guide Composer notifications to Notification Composer. |
Use the AWE To EONC Conversion page (EONC_AWE_RUN) to specify the conversion method for your existing AWE notifications. To convert existing AWE notifications, start by applying Notification Composer updates through Change Assistant. The change package process automatically directs you to this page. You do not need to access this page through the menu path.
Navigation:
This example illustrates the fields and controls on the AWE To EONC Conversion page.
|
Field or Control |
Description |
|---|---|
|
Map to Delivered AWE Configuration |
Select this option to map your existing Approval Workflow Engine notification events to PeopleSoft delivered Notification Composer events and related system data. |
|
Preserve Existing AWE Configuration |
Select this option to maintain 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. |
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: It is important to include all AWE notification composer updates in your change package to ensure that all the AWE configuration is properly converted.
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 this page after applying the change package.
This page does not retain the conversion selection you made while applying the change package. Do not use the page for this purpose after applying the change package.
Use the AG Composer Conversion to NC page (AGC_CNVTONC) to convert your existing Activity Guide Composer notifications to Notification Composer.
Navigation:
This example illustrates the fields and controls on the AG Composer Conversion to NC page.
Click Run to initiate the Activity Guide Composer notification conversion process.
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 perform it again. You do not need to return to this page after applying the change package.