If you ALREADY had access to PQA for testing Work Package #1 - Role Grouping Templates

You STILL have access and DO NOT need to request it again.

To request access to the User Acceptance Test environment (PQA), follow the link below and provide the name, last 4-digits of EMPLID, email, contact phone number and college. Please note: College Advisory Group members will have advanced access to the environment to perform initial shake-down testing prior to the All College UAT activity and have a separate tab to submit their access requests:

Access Request (Google Sheet) [UAT environment access for ALL Colleges tab]

Testing will occur in the PQA environment. Testers will be logging on using their EMPLID. In order to access the Launchpad feature, testers performing this step must have Local Security Administrator access (ZZ Local Security Admin) This environment rests behind an OKTA instance and therefore you will be prompted to establish a password during activation.

Login Access Link: https://oktapreview.ctclink.us/

NOTE: If access was already granted, it will be noted in the Google sheet linked above.

Testers who have already activated themselves in the PQA environment for other testing activities (concurrent UAT activities in this environment) will not be required to re-activate as this is a shared environment for all concurrent UAT activities.

Having Issues Logging In? Contact the Security Team. ([email protected])

Don't Forget: You have the ability to reset your own password in Okta. If encountering password issues, try this first. You might be able to self-help quicker!

Also, if you're struggling after regular service hours, feel free to download the Tester Login Reference Guide (below) to see if the answer you need is in here:

• Issue Details: Messaging in log files states that Primary/Row Permission List was updated, but CTC_PT_MASK_ALL value remains the same.
  • Update Row Security and Primary Permission Lists
  • Primary Permission List = CTC_PT_MASK_NONE  Row Security Permission List = CTC_PT_MASK_NONE
  • Updated Primary and Row Security Permission List = CTC_PT_MASK_ALL
• Research: Program function is to remove Permission List values and replace with CTC_PT_MASK_ALL. If the user profile original had CTC_PT_MASK_ALL, it is technically correct to state that it was removed and updated to add it back, thus generating the update message.
• Resolution: Provide clearer instructions on program behavior in the Quick Reference Guide. [Complete]

• Issue Details: Messaging in log files gives impression that the expense delegation was removed for the separated employee and another individual.
  • Expense Delegation Removed - Emplid / Authorized Oprid
  • 101001234 / 101001234
  • 101001234 / 101023456
• Research: Program behavior is correct. The Authorize Expense Users page had two rows for the separated employee, one allowing the employee authorization to submit expense reports AND another employee was also authorized to submit expense reports "on behalf of" the separating employee. Both rows were removed from the table and are reflected in the log file.
• Resolution: Provide clearer instructions on program behavior in the Quick Reference Guide. [Complete]

• Issue Details: Messaging in log files states it updated rows for Enrollment Security, but the user did not have Enrollment Security assigned.
• Research: Program behavior was correct, but messaging in log file could prove confusing.
• Resolution: Update program logic to ignore SACR Enrollment Security records where the Enrollment Access ID field is blank, thus not generating a message in the log file displaying an update to blank out a value that is already blank.
• RETEST APPROACH:
  • TEST 1: Identify an employee who DOES NOT have a value in the Enrollment Access ID field. Offboard the employee and confirm that no message appears in the log file relating to UPDATING the Enrollment Security status.
  • TEST 2: Identify an employee who DOES have a value in the Enrollment Access ID field. Offboard the employee and confirm that a message DOES appear in the log file relating to UPDATING the Enrollment Security status.

• Issue Details: Messaging in log files states ***Employee is a STUDENT*** , but the user does not the ZZ SS Student role assigned.
• Research: Program behavior was incorrect, revision needed to select for complete role name.
• Resolution: Updated code to only generate the alert when the user has the ZZ SS Student role.
• RETEST APPROACH:
  • Test for Non-Student: Identify an employee who is NOT a student, but has CS roles with the word "Student" in the role name. Offboard the employee and confirm that the ***Employee is a STUDENT*** message does not appear in the log file.
  • Test for Student: Identify an employee who is ALSO A STUDENT, and has the CS roles with the word ZZ SS Student. Offboard the employee and confirm that the ***Employee is a STUDENT*** message appears in the log file.

• Issue Details: CS Log file noted the removal of the Student Institution Set value for a student.
• Research: Program behavior was incorrect, the value should not be removed for the user who is also a student.
• Resolution: Updated code to omit the removal of this value.
• RETEST APPROACH:
  • Test for Student:
    1. Identify an employee who is ALSO A STUDENT at your institution.
    2. Navigate to Main Menu > Set Up SACR > Security > Secure Student Financials > Student Institution Set and confirm that the student HAS their Student Institution Set value set for your institution.
    3. Offboard the employee and confirm that the "Updated value to blank for menu item:  Student Institution Set - PS_OPR_DEF_TBL_CS (ISET_OVRD)" message no longer appears in the log file.
    4. Navigate to Main Menu > Set Up SACR > Security > Secure Student Financials > Student Institution Set and confirm that the student has their Student Institution Set value STILL set for your institution.

• Issue Details: HCM Log file noted the the employee as being a manager when no job record existed listing the user as a supervisor on an active job record.
• Research: Program behavior was incorrect, the should only appear for a user who is listed as a supervisor on an active job data record.
• Resolution: Updated code to correctly identify the supervisor condition.
• RETEST APPROACH:
  • Test for Non-Supervising Employee: Offboard the employee in HCM to confirm that log file message "***Employee is a Manager**** does not appear.

• Issue Details: On Scheduling Process pop-up message  "Person active at another institution, are you sure you want to proceed?"
• Research: Program message was incorrect, the warning will appear for a user who an active job data record at ANY company.
• Resolution: Updated warning message to read as "Person has active job record."
• RETEST APPROACH:
  • Navigate in HCM to Main Menu PeopleTools > Security > CTC Custom > Offboarding Automation
  • Identify EMPLIDs for employees that meeting the criteria below and enter your Company Code and their EMPLID to verify
    • Test appearance of warning message for an 'Active' employee at your institution.
    • Verify NO warning message appears for an 'Inactive' employee at your institution, who is NOT currently an 'Active' jobs at other institutions.
    • Test appearance of warning message for an 'Inactive' employee at your institution, who is currently an 'Active' employee at another institution.

• Issue Details: Messaging in log files gives impression that the Student Financials SACR Security section for the separated employee needed some form of action to be taken:
      •    ----- Secure Student Financials --------
      •    Processing SACR Setup for : 101001234
      •           Company: xxx (0,0)
      •         Institution:    (0,0)
      •    Business Unit:    (0,0)
  •    Research: Program behavior is correct. There is no SF SACR Security for this individual, therefore no Institution or BU to remove.  
  •    Resolution: Provide clearer instructions on program behavior in the Quick Reference Guide. [Complete]
   

• Issue Details: Each pillar generates an email notification that contains the EMPLID and Name of the offboarded employee and the LSA who performed the offboarding. This is a risk.
• Research: Confirmed that AAG ruling was EMPLID may be included in email notifications, but cannot be combined with other PII data. Developer confirmed that the Notification Template can be edited to remove names. Changes applied to the templates in PQA.
• Resolution: Updated template to remove names from email notifications, which will remove this displayed information in the log file where the email notification messaging is displayed.