Use this checklist to prepare your campus to use the Temporary Academic Employment (TAE) functionality in CHRS.

Security 

• Review the CHRS Security List

  • All TAE roles begin with CHR_TF_
  • Security Roles for CHRS
• Originator (Submitter of Appointments) 

  • Confirm who on the campus will be an Originator.
  • Confirm what roles the Originator should have.
  • Work with your security admin to have the identified users assigned the correct roles. 
• Approvers

  • Confirm who on the campus will be an Approver
  • Confirm what roles the Approver should have.
  • Work with your security admin to have the identified users assigned the correct roles. 
• TAE Super User

  • Confirm who on the campus will be a TAE Super User.
  • Confirm what roles the TAE Super User should have,
  • Work with your security admin to have the identified users assigned the correct roles. 
• Testing Prep

  Utilize the TAE Testing Prep document to plan out your testing. 

  ***Please note that the security roles mentioned in the TAE Testing Prep document may be different than what is in CHRS. Make sure to refer to the Security Roles for CHRS to confirm the roles you are assigning. 

  

General Setup

• Set up CSU TAE Academic Year 

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Setup Table >CSU TAE Academic Year

  Job Aid: Set Up CSU Academic Year

• Set up CSU TAE Pay Calendar

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Setup Table > CSU TAE Pay Calendar

  Job Aid: Set Up CSU TAE Pay Calendar

• Set up CSU TAE Term Table

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Setup Table > CSU TAE Term Table

  Job Aid: Set Up CSU TAE Term Table

• Set up CSU TAE Session Codes

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Setup Table > CSU TAE Session Codes

  Job Aid: Set Up CSU TAE Session Codes

• Set up CSU TAE Process Defaults

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Setup Table > CSU TAE Process Defaults

  Job Aid: Set Up CSU TAE Process Defaults

Workflow Setup

• CSU TAE WorkFlow Steps 

  Navigation: Menu > CSU Temp Academic Employment > CSU TAE Approval Workflow > CSU TAE WorkFlow Steps

  Job Aid: Set Up TAE Approval Workflows

• CSU TAE WorkFlow Approvers 

  Navigation: Menu > CSU Temp Academic Employment > CSU TAE Approval Workflow > CSU TAE WorkFlow Approvers

  Job Aid: Set Up TAE Approval Workflows

• CSU TAE Appointment Authority

  Navigation: Main Menu > CSU Temp Academic Employment > CSU TAE Appt Notification > CSU TAE Appointment Authority

  Job Aid: Set Up Appointment Authority

• CSU TAE Hide Approval Fields

  Navigation: Menu > CSU Temp Academic Employment > CSU TAE Approval Workflow > CSU TAE Hide Approval Fields

  Job Aid: Configure Hidden TAE fields

Submit ServiceNow Tickets

• Campus Logo

  Each Appointment Notification has the ability for campuses to have their campus logo displayed. Open a Optimize Case with your campus logo attached.

  When submitting the ticket: 

  • Platform/Product: CHRS 9.2 (Peoplesoft)
  • Business Application: TAE (CHRS 9.2)
  • Operational Service: CHRS Non-Production
  • Short Description:
    • In the short description, indicate that the campus name, the module, and the what the request is for. (Example: CHI - TAE- Campus Logo - MTP)
  • Description:
    • The description section should include the following:
      • Database Name (Example: HACHRSIT to HCHRPRD)
      • Reason (Example:  Campus Logo change)
      • Attachment Title
  • Attachments:
    • Include an attachment (JPEG) 
• Campus URL

  Each Appointment Notification has the ability for campuses to have a specific campus link displayed (LETTER_CAMPUS-LINK). URL's can be specific by EE group.   

  Open an Optimize Case indicating what EE Group, Effective Date, and link you want to appear in the appointment notification. Please make sure you indicate which EE groups the URL is for.  You can enter multiple URL changes under one case.

  When submitting: 

  • Platform/Product: CHRS 9.2 (Peoplesoft)
  • Business Application: TAE (CHRS 9.2)
  • Operational Service: CHRS Non-Production
  • Short Description:
    • In the short description, indicate that the campus name, the module, and the change needed. (Example: CHI - TAE Config - URL-Pass A)
  • Description:
    • The description section should include the following:
      • Database Name (Example: HACHRSIT to HCHRPRD)
      • Reason (Example:  Conversion from Pass C  to MTP)
      • EE Group and URL
• CSU TAE Appointment Type

  The CSU TAE Appointment Type Table is CMS owned. However, each campus will have version under their BUSN Unit when they enter the CHRS environment. Campuses can request modifications for their BUSN Unit table for Appt Type 022 (Daily Rate- 172). 

  Open an Optimize Case indicating what the numerical value Appt Type 022 (Daily Rate) needs to be changed to, and the effective date the change needs to occur. 

  When submitting: 

  • Platform/Product: CHRS 9.2 (Peoplesoft)
  • Business Application: TAE (CHRS 9.2)
  • Operational Service: CHRS Non-Production
  • Short Description:
    • In the short description, indicate that the campus name, the module, and the change needed. (Example: CHI - TAE Config - Appt Type Change-Pass A)
  • Description:
    • The description section should include the following:
      • Database Name (Example: HACHRSIT to HCHRPRD)
      • Reason (Example:  Conversion from Pass C to MTP)
      • Details for change (Example: 172 to 175 effective 8/1/2026)
• Campus Config Migration between Passes/MTP

  Submit an Optimize Case to CHRS App Dev using the example campus configuration document, update for your the template with your campus information based on what should be migrated from each pass through MTP. 

  When submitting: 

  • Platform/Product: CHRS 9.2 (Peoplesoft)
  • Business Application: TAE (CHRS 9.2)
  • Operational Service: CHRS Non-Production
  • Short Description:
    • In the short description, indicate that the campus name, the module, and the Pass/MTP this is requested for. (Example: CHI - TAE Config - MTP)
  • Description:
    • The description section should include the following:
      • Database Name (Example: HACHRSIT to HCHRPRD)
      • Reason (Example:  Conversion from Pass C  to MTP)
      • Pages to migrate
      • Attachment Title
  • Attachments:
    • Include an attachment with all the details of what your campus needs to have migrated. The attachment should look similar to the example below. 

  Download 

End of Article