Topics Map > Human Resource System (HRS) > Finance
Adding New Users to Receive Email Notifications for PeopleSoft Processes for Testing in Non-Prod Databases
Overview
This document describes the steps required to add new users to receive email notifications for PeopleSoft processes for testing in non-production databases.Process Considerations:
- These steps are only required for testing in non-production databases as the email address that is in the production database is the user's true business email address - not the HRTST@g-groups.wisc.edu
You may click on the links below to navigate directly to a section:
Instructions
1. Create a Jira that has the following information:
| Title | Process Type + Process Name + "Email Adjustment" - ex. Application Engine UW_DR_AFTERC Email Adjustment |
| Type | System Issue |
| Problem Type |
5-System Change |
| Environment | HRS |
| Team | HRS-Financials |
| Description | 1. Within HRS Navigate to: PeopleTools > Process Scheduler > Processes. Please add the following user IDs to the Notifications tab of the Process Definition for <Process Name>: 9999999 9999999 And check the following: On Error, On Warning, On Success - see sample below.  2. When that is done, then create a SQL in HRTST to update PSOPRDEFN correctly for the following people with these email addresses. NOTE this step only needs to be completed in the non-prod databases for testing. 9999999 to email@address.com (ex. 00934563 to jpanke@uwsa.edu) 9999999 to email@address.com (ex. 00934563 to jpanke@uwsa.edu) Thanks! |
NOTE: Typically the email addresses in the non-production databases uses the generic email HRTST@g-groups.wisc.edu so that is why the email addresses need to be updated so the email notification functionality can be tested to ensure it is working correctly and sending to the correct people.
2. Assign the JIRA to the Team: HRS Development for an estimate of the work.
3. When it comes back, assign to the HR/TAM/Finance manager and ask for approval.
4. After HRS Development team does the required updates in HRTST, run the process affected to be sure the emails are sent to the appropriate people.
5. If emails not going to the correct people, ask for the HRTST PSUNX batch scheduler cache to be cleared when nothing is running. This is because the Distribution agent might have some bad/old cache.
6. If initial testing in HRTST is successful, follow the necessary steps to move along the JIRA from regression testing to migration to production. NOTE: Do not include the SQL update in the PHIRE CR for HRQA - have the developer ask the DBAs to run that separately/manually in HRQA.