Summary of "PeopleSoft Spotlight Series: Notification Composer Part 4 (4 of 4)"

Summary of “PeopleSoft Spotlight Series: Notification Composer Part 4 (4 of 4)”

This video is the final installment in a four-part series focused on PeopleSoft Notification Composer, a framework for managing and delivering notifications within PeopleSoft applications. The session includes a practical demo, advanced technical topics, configuration guidance, and troubleshooting tips.

Key Technological Concepts & Features

1. Notification Composer Overview & Demo

Walkthrough of PeopleSoft Notification Composer setup and usage in an HCM (Human Capital Management) environment.
Demonstration of configuring notification names, delivery methods (in-app, email, texting), and personalization options.
Example scenario: Employee updates address, triggering approval workflow notifications for both employee (alert) and administrator (action).
Integration of Notification Composer with approval workflows replacing legacy notification methods.

2. Notification Administration & Configuration

Notification settings are organized by functional categories and pillars (HCM, FSCM, ELM, CRM, Campus).
Notification names group related notifications; configuring these controls user visibility and personalization.
Personalization is a customer choice and tied to roles/permissions.
Global settings enable delivery channels (in-app, email, texting).
Synchronization of contact preferences (email addresses) across HCM and ELM using delivered App Engine processes.

3. Advanced Topics

Event Mapping: Allows triggering notifications based on PeopleSoft transactions with configurable event levels (component, record field, record) and timing (pre-change, post-change, override).
Code Conversion: Legacy trigger business event code is conditionally replaced by Notification Composer-enabled code, allowing coexistence and gradual migration.
Customers can create custom notifications with minimal coding, mainly for conditional logic; advanced conditions still require developer involvement.
Notification Composer does not currently support CC/BCC in emails, which is a known limitation.
Notification Composer does not integrate with EOEN (Event and Notification Framework) used by Campus pillar.
Active Analytics Framework (used in CRM) still relies on trigger business events, limiting Notification Composer uptake.

4. Pillar Delivery Plans & Differences

Notification Composer rollout varies by pillar and application image:
- HCM: Began in Image 47, completed by Image 49 (except federal notifications phased).
- FSCM: Started in Image 49; mix of legacy and Notification Composer approaches due to prior use of notification names.
- ELM: Partial delivery in Image 23, completed by Image 24.
- CRM: Limited uptake due to Active Analytics Framework dependency.
- Campus: Evaluation ongoing; currently uses EOEN.
Enabled-by-default delivery methods differ by pillar and role:
- HCM/ELM employees/managers default to email; admins default to in-app.
- FSCM varies by role and transaction.
- CRM defaults to email for approvals.
HCM uniquely provides a navigation collection for notification-related setup pages.

5. Notification Composer Pages & Tools

New application pages allow customers to view all delivered notification events, improving visibility over previous undocumented or hidden notifications.
Customers can search/filter notification events by category, business process, owner, etc.
Ability to clone and override delivered notifications to customize behavior without modifying delivered objects.

6. Tips & Troubleshooting

Extensive documentation and knowledge base articles (MOSS docs) are available, including implementation guides, known issues, and inventory spreadsheets per pillar.
Important to check:
- Global settings (enablement of delivery channels).
- Notification name settings (allow personalization, enabled by default).
- Notification ID status (active/inactive).
- User personalization preferences.
Recommended approach for customizing notifications is cloning and overriding rather than direct modification.
Conversion logs are critical for troubleshooting migration from legacy notifications to Notification Composer.
Common pitfalls include misunderstanding personalization settings and delivery channel enablement.

7. Limitations

No support for CC/BCC in emails within Notification Composer.
Buying variables cannot be easily added to delivered notifications without customization.
Conditional notification sending requires developer coding.
Notification Composer does not support inbound notifications.
Long links in text messages may break due to carrier message splitting; TinyURL is not supported.
Notifications that override message content/recipients at runtime can be confusing to manage.
EOEN and Active Analytics Framework notifications are not currently converted to Notification Composer.

8. Future & Support

New notifications delivered after pillars adopt Notification Composer will exclusively use this framework.
Legacy notification methods are planned for deprecation by December 31, 2025, encouraging customers to migrate.
Ongoing discussions and development planned to improve integration (e.g., with EOEN) and add features like conditional logic configuration.

Main Speakers / Sources

Primary speaker is a PeopleSoft product expert familiar with Notification Composer and HCM, likely a PeopleSoft product manager or senior consultant.
References to PeopleSoft development teams and support engineers involved in Notification Composer implementation and troubleshooting.
Mention of PeopleSoft documentation (PeopleBooks) and MOSS (My Oracle Support) knowledge base as key sources for technical details.

Overall, this video provides an in-depth practical and technical overview of PeopleSoft Notification Composer, focusing on its configuration, usage, advanced customization, pillar-specific delivery plans, troubleshooting best practices, and known limitations to aid customers and implementers in adopting and managing this notification framework effectively.