Email Notifications Reference Page Setup

The following reference pages are required in order to use the Email Notification processing in Advantage HRM:

Email Triggers - The Email Trigger Maintenance (EMTM) page contains information about the recipients of the email, the delivery date, and the message to be delivered. The recipient roster can be either static (a defined list of recipients at creation) or “smart”, meaning that at delivery time the Email Agent determines the recipients from organizational or group information in the trigger. Email Triggers allow the use of templates so that custom form messages can be delivered.
Email Reminders and Notifications - The Email Reminders and Notifications (EMRM) page contains criteria that is used to evaluate against Employee Timesheet (TIMEI), Benefits Enrollment (ENRL) and Performance Journey transaction tables. The configurations are used to determine whether or not a specified set of employees has submitted a particular transaction or action.

When Notification is set to Performance Type Triggers, either the Performance Type or Conversation Reminder Flag has to be selected.

When Performance Type is chosen then, Evaluation From, Evaluation To, Home Department, Home Unit and Union local are mandatory fields. Wild card entries for Home Department, Home Unit and Union Local are supported. However, due to performance considerations, wild card is not recommended to bet setup for all fields. The offline process refers the Notifications tab on the related Performance Type reference page, to trigger the reminders. Templates and Evaluation Status, Linked conversation related other criteria for Evaluation related reminders are to be set up on the Notification tab on the Performance Type (PERFTYP) reference page.

When the Notification field is set as Performance Type Triggers and Conversation Reminder Flag is chosen along with other fields for Employee Criteria then clients can send reminders to Evaluators about any ad hoc conversations which are pending and past due follow up dates.

Performance Type - Notifications Tab - The Notifications tab on the Performance Type page needs to be set up for the Emails and Notifications related to upcoming or overdue due dates on Evaluation. This table defines different Evaluation Status and whom to send the notification to - Employee, Evaluator, Reviewer or 360 Degree Reviewer and when to send the notification before and after the due date. Refer to following scalar and fields for more information

Goals Initiated - This scalar is used to set up emails and alerts that need to be sent to Employee or Manager when Evaluation is in Goals Initiated status.
Notification Lead Days - The number of days before the Goals Finalization Due Date the system sends the reminder when the batch job is run. For example, if Goals Finalization Due Date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please release the Goals’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is the Goals Finalization Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please release the Goals’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is the Goals Finalization Due Date.
Notification Lag Days- The number of days after the Goals Finalization Due date is overdue the system will send the reminders if the batch job is run. For example if Goals Finalization Due date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder will be sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past to release the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past to release the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Notify Employee - This field can be used so an employee can reach out to the evaluator to release the goals. However, in this evaluation status employee has no action in the system to perform.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator.
Goals Pending Employee Review - This scalar is used to set up emails and alerts that need to be sent to Employee or Manager when Evaluation is in the Goals Pending Employee Review.
Notification Lead Days - Number of days before the Goals Finalization Due date the system sends the reminder if the batch job is run. For example, if Goals Finalization Due Date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please review and sign the Goals’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please review and sign the Goals’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Notification Lag Days - The number of days after the Goals Finalization Due Date is overdue the system sends the reminders if the batch job is run. For example, if Goals Finalization Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past, please review and sign the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past, please review and sign the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Notify Employee - This field needs to be used to send out alerts and emails to the employee.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator about employee signature. However, in this evaluation status evaluator has no action in the system to perform.
Goals Pending Manager Approval - This scalar is used to set up emails and alerts that need to be sent to Employee or Manager when Evaluation is in the Goals Pending Manager Review.
Notification Lead Days - Number of days before the Goals Finalization Due Date the system sends the reminder if the batch job is run.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please review and sign the Goals to complete the Goal finalization process’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is approaching, please review and sign the Goals to complete the Goal finalization process’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Notification Lag Days - The number of days after the Goals Finalization Due Date is overdue the system sends the reminders if the batch job is run.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past, please review and sign the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Goals finalization due date %p is past, please review and sign the Goals’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Goals Finalization Due Date.
Notify Employee - This field might be used in this scalar as employee can reach out to the evaluator one on one, to sign and approve the goals. However, in this evaluation status employee has no action in the system to perform.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator.
Self-Assessment - This scalar is used to set up emails and alerts that need to be sent to Employee or Manager when Evaluation is in the Assessment in Progress status and Self-assessment is not yet submitted. Sites who do not use self-Assessment should not be using this scalar.
Notification Lead Days - Number of days before the Self-assessment Due Date the system sends the reminder if the batch job is run. For example, if Self-Assessment Due date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Self-Assessment Due Date %p is approaching, please submit your self-assessment’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Self-Assessment Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Self-Assessment Due Date %p is approaching, please submit your self-assessment’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Self-Assessment Due Date.
Notification Lag Days - The number of days after the Self-assessment Due Date is overdue the system sends the reminders if the batch job is run. For example, if Goals Finalization Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Self-Assessment Due Date %p is past due, please submit self-assessment’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Self-Assessment Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Self-Assessment Due Date %p is past due, please submit self-assessment’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Self-Assessment Due Date.
Notify Employee - This field needs to be used to send out alerts and emails to the employee.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator about employee self-assessment submission. However, in this evaluation status evaluator can continue with their assessment or reach out for 360-degree feedback from other reviewers in the system.
360 Degree Feedback - This scalar is used to set up emails and alerts that need to be sent to Manager or 360 Reviewer when Evaluation is in the Assessment in Progress status and 360 Review feedback is in pending state.
Notification Lead Days - Number of days before the 360-degree feedback Due date the system sends the reminder if the batch job is run. For example, if 360 feedback Due date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘360-degree feedback is pending, and due date %p is approaching, please provide your feedback’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is 360 Feedback Due Date.
Alert CTEXT - Alert reminders uses this CTEXT. The message should be configured similar to ‘360-degree feedback is pending, and due date %p is approaching, please provide your feedback’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is 360 Feedback Due Date.
Notification Lag Days - The number of days after the 360-feedback due date is overdue the system sends the reminders if the batch job is run. For example, if Goals Finalization Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘360-degree feedback is past due %p, please provide your feedback’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is 360 Feedback Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘360-degree feedback is past due %p, please provide your feedback’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is 360 Feedback Due Date.
Notify 360 Reviewer - This field needs to be used to send out alerts and emails to the reviewer.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator, about 360 feedback status. Evaluator can choose to follow up for the feedback to be submitted. However, in this evaluation status evaluator can continue with their assessment or reach out for other 360-degree feedback from other reviewers in the system.
Pending Reviewer Feedback - This scalar is used to set up emails and alerts that needs to be sent to Manager or Reviewer when Evaluation is in the Pending Review feedback status and Review status is in ‘Review Pending’ status.
Notification Lead Days - These many days before the Review Due Date, the system sends the reminder if the batch job is run. For example, if Performance Type Triggers 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Reviewer feedback is pending, and due date %p is approaching, please provide your feedback’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Reviewer feedback is pending, and due date %p is approaching, please provide your feedback’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Notification Lag Days - The number of days after the review due date is overdue the system sends the reminders if the batch job is run. For example, if review Due date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Reviewer feedback is past due , please provide your feedback’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Reviewer feedback is past due %p, please provide your feedback’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Notify Reviewer - This field needs to be used to send out alerts and emails to the reviewer.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator about review status. Evaluator can choose to follow up for the feedback to be submitted.
Reviewer Requested Update - This scalar is used to set up emails and alerts that needs to be sent to Manager or Reviewer when Evaluation is in the Pending Review Feedback or Assessment in Progress status and Review status is in Reviewer Requested Update status.
Notification Lead Days - These many days before the Review Due Date, the system sends the reminder if the batch job is run. For example, if Review Due date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Please provide an update as Reviewer Feedback Due Date %p is approaching’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Please provide an update as Reviewer Feedback Due Date %p is approaching.’ This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Notification Lag Days - The number of days after the review due date is overdue the system sends the reminders if the batch job is run. For example, if review Due date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Please provide an update as Reviewer Feedback Due Date %p is past’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Please provide an update as Reviewer Feedback Due Date %p is past’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Review Due Date.
Notify Reviewer - This field might be used to send out alerts and emails to the reviewer, however at this stage, reviewer has no action to perform in the system.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator to make updates and send out the review request again for review to complete.
Release Evaluation - This scalar is used to set up emails and alerts that need to be sent to Manager or Employee when Evaluation is in the Assessment in Progress status and Evaluation Due Date is approaching or Past Due.
Notification Lead Days - These many days before the Evaluation Due Date, the system sends the reminder if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please release the evaluation for employee signature’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please release the evaluation for employee signature’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notification Lag Days - The number of days after the Evaluation Due Date is overdue the system sends the reminders if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please release the evaluation for employee signature’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please release the evaluation for employee signature’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notify Employee - This field might be used to send out alerts and emails to the employee, however at this stage, employee has no action to perform in the system.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator to release evaluation for employee signature.
Evaluation Pending Employee Signature - This scalar is used to set up emails and alerts that needs to be sent to Manager or Employee when Evaluation is in the Evaluation Pending Employee Signature.
Notification Lead Days - These many days before the Evaluation Due Date, the system sends the reminder if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please Sign the evaluation. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Alert CTEXT- Alert reminders usea this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please Sign the evaluation’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notification Lag Days - The number of days after the Evaluation Due Date is overdue the system sends the reminders if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please Sign the evaluation’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please Sign the evaluation’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notify Employee - This field might be used to send out alerts and emails to the employee.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator.
Evaluation Pending Manager Signature - This scalar is used to set up emails and alerts that need to be sent to Manager or Employee when Evaluation is in the Evaluation Pending Manager Signature.
Notification Lead Days - These many days before the Evaluation Due Date, the system sends the reminder if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lead Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/05/2023 till 12/15/2023 the reminder is sent with the CTEXT used in this scalar.
Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please Sign the evaluation. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is approaching, please Sign the evaluation’. This CTEXT cannot be used if Notification Lead Days is not checked. Same CTEXT is used for both reviewer and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notification Lag Days - The number of days after the Evaluation Due Date is overdue the system sends the reminders if the batch job is run. For example, if Evaluation Due Date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run after 12/15/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please Sign the evaluation’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Past Due Alert CTEXT - Email reminders uses this CTEXT. The message should be configured similar to ‘Evaluation Due Date %p is past, please Sign the evaluation’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Evaluation Due Date.
Notify Employee- This field might be used to send out alerts and emails to the employee.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator.
Conversation Reminders - This scalar is used to set up emails and alerts that needs to be sent to Manager about the check-ins or conversation touch points that are past due and still pending with the reporting employees. This scalar is used for conversations that are linked to the Employee evaluations.
Notification Lag Days - If any conversation linked to the evaluation is pending, then these many days due past the Conversation Follow-up Date the system sends the reminder if the batch job is run. For example, if Follow-up date is 12/15/2023 and the Notification Lag Days is set to 10 then anytime the Email Reminder batch job is run on or after 12/16/2023 till 12/25/2023 the reminder is sent with the CTEXT used in this scalar.
Past Due Email CTEXT- Email reminders uses this CTEXT. The message should be configured similar to ‘Follow-up date %p on conversation is past due, please complete Check In’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Conversation Follow-up Date.
Past Due Alert CTEXT- Alert reminders uses this CTEXT. The message should be configured something ‘Follow-up date %p on conversation is past due, please complete Check In’. This CTEXT cannot be used if Notification Lag Days is not checked. Same CTEXT is used for both employee and evaluator hence the CTEXT should be generic in nature. %p in the CTEXT is Conversation Follow-up Date.
Notify Employee - This field needs to be used to send out alerts and emails to the employee.
Notify Evaluator - This field needs to be used to send out alerts and emails to the evaluator.
Personnel Action Extension - The Personnel Action Extensions (PACTX) page extends the Personnel Action Code logic and allows Personnel Actions to initiate the sending of emails, either immediately or delayed through triggers. This table allows notifications to be delivered to the employee on which the action is performed and/or to another employee, user, or external email address.

Personnel Action Code Extensions (PACTX) allows administrators to kick off notifications whenever a specified Personnel Action is performed for an employee. The extension page allows notifications to be sent to the relevant employee or to a chosen user, employee, or external email address. Both employee and other notifications also feature a field that allows emails to be sent when a transaction is submitted, on the day of the Personnel Action, or based on a chosen number of days before or after the event.

When transactions are submitted with a Personnel Action (or Department Action) are processed, the personnel extensions are processed as well. For each notification type on the extension, an Email Trigger is created. The date of the trigger is determined by the value in the Recipient Delay (for a user, employee, or external email address) or the Employee Delay (for the associated employee on the transaction). If the field is blank, the Email Trigger uses the current date (System Date) as the Maturity Date. If the field has a zero, then the email is scheduled for the date of the Personnel Action. If the value is a positive number, the email is scheduled a given number of days after the Personnel Action, and if the number is negative, the email is scheduled a given number of days before the Personnel Action.

Email Template - The Email Template reference page allows the creation of custom form-letters through the use of variables in the text. The variables support information such as the employee's first name, full name, address, a variety of dates (dependent on the particular process creating the trigger or populating the template), and custom parameters (also dependent on the process creating the trigger or populating the template).
Employee Benefits Enrollment Administrator (EBEA) can automatically create Email Triggers to send reminder emails when enrollment periods begin and when enrollment deadlines are approaching.

The Employee Benefits Enrollment Administrator reference page supports automatic notifications of Open Enrollment period start and end dates. Employee Benefits Enrollment Administrator allows for the notification of employees at an administrator-specified interval before Open Enrollment begins, one notification during the period, and a last reminder that the period is about to conclude. Each of these notifications can have their own independent Template specified on the page.

Whenever an EBEA entry is saved, the HRM application creates an Email Trigger for each of the notification dates. The Email Trigger contains the designated Template, a Maturity Date matching the specified notification date on the reference page, and has a smart recipient roster that corresponds to the Department/Benefits Policy combination entered on the EBEA entry. The EBEA page store the ID numbers for these triggers so that modification of the EBEA entry in the future does not result in duplicate Triggers, but in the modification or deletion of the existing associated Triggers.

For more information on the Employee Benefits Enrollment Administrator (EBEA) page, refer to the "Employee Benefits Enrollment Administrator" topic in the Benefits User Guide.