Understanding Due Date Notifications

The Due Date Notifications feature sends email messages to managers, employees, and peer reviewers automatically and reminds them about the due dates of their evaluation documents. It leverages the HR Notification framework to identify recipients, configure email templates, and generate email notifications for delivery.

Note: Email notifications for employees are created in the same language as their associated documents. For managers and participants, these notifications are created in their preferred language that is selected on the User Profiles - General page (USER_GENERAL), or the base language if the preferred language is not specified.

As an administrator, you can select the type of notifications that users receive. Each process step in the evaluation cycle is a type of due date notification, which includes:

  • Define Criteria

  • Checkpoint

  • Finalize Criteria

  • Nominate Participants

  • Evaluation

For each step that you want to enable for due date notifications, you can specify when they are sent. ePerformance delivers three alert types, which define the number of days before the due date that these reminders need to be generated and sent. You can select up to three levels of due date reminders to send to users for each step.

After the configuration for due date and alert types is complete, you run an application engine (AE) program (EP_INIT_NOTIF) that first extracts the due date information from all documents that are not completed or canceled and are currently in progress at any step in the evaluation cycle, and then loads it into the schedule table (EP_NOTIFY_TBL). Going forward, any evaluation creation or update that occurs after this initial load is validated online, and added or updated in the schedule table when applicable. This table provides the most current scheduling information for processing due date notifications.

As mentioned previously, ePerformance leverages the HR Notification framework to configure recipients and email templates for use in due date notifications, and deliver them. As scheduled, the framework runs to look up from the schedule table a list of evaluations for which due date notifications need to be sent based on the configuration settings. Then, it generates due date notifications for these evaluations and sends them to the corresponding recipients. A recipient of a due date notification is a user whose role is given permission to update a document in a process step, as specified in the document template setup. For managers who may receive multiple reminders from their teams’ evaluations on a single day, their reminders are consolidated in one email notification for delivery.

This diagram illustrates the high-level process flow for due date notifications, which includes preparing data, setting up the feature, and running a nightly job that composes and sends due date reminders to corresponding recipients.

Due Date Notifications Process Flow

Refer to the Setting Up Due Date Notifications topic for a complete list of setup steps for the Due Date Notifications feature.

Video: Image Highlights, PeopleSoft HCM Update Image 27: ePerformance Due Date Notifications

Here is an example of a due date notification schedule of an evaluation document. In this example, the system is configured to send all three types of email reminders for all evaluation steps using these values: 60 days, 30 days, and 5 days before due date. The column on the far right lists the calculated dates on which due date notifications are sent for each step based on step due dates and the setup of the feature.

Due Date Type or Evaluation Step

Step Due Date

Who To Notify

WHEN DUE DATE NOTIFICATIONS ARE SENT

Define criteria

April 1

Manager, employee, or both

Note: Roles of recipients come from the document template.

January 31 (courtesy, 60 days before due date)

March 2 (warning, 30 days before due date)

March 27 (critical, 5 days before due date)

Nominate participants

May 1

Manager, employee, or both

March 2

April 1

April 26

Complete mid-period checkpoint

June 1

Manager or both

April 2

May 2

May 27

Finalize criteria

October 1

Manager, employee, or both

August 2

September 1

September 26

Employee completes self-evaluation

December 1

Employee

October 2

November 1

November 26

Participant completes peer review

December 5

Participant

October 6

November 5

November 30

Manager completes employee evaluation

December 31

Manager

November 1

December 1

December 26