PeopleSoft Policies and Procedures

PeopleSoft Backdoor Fixes

In rare circumstances, the Enterprise Applications team may encounter errors that must be resolved by a direct database edit within PeopleSoft, called a "backdoor fix". Whenever possible, this should be avoided. If the same issue prompts multiple backdoor fixes, it may become a priority for development and feature enhancements that reduce risk and technical debt.

All backdoor fixes should be logged in the ticketing system, as follows:

• Create a ticket that logs the issue
• Whenever possible, test the change in a non-production instance (usually STG)
• Apply an appropriate approval workflow to that ticket
• Follow the approval workflow:
  • Review and approval by assigned technician
  • Review and approval by additional technician (peer review)
  • Review and approval by EAPP Director (MPP)
  • Review and approval by data owner (or their delegated MPP)
  • Review and approval by Area Change Coordinator
• Area Change Coordinator documents the change with an Emergency Request for Change (ERFC)
• Assigned technician implements the change, and attaches log information to the ticket

All backdoor fixes will be reported to multiple teams for review:

• DAWGS group (meets weekly)
• CAB group (meets weekly)
• Information Security team (via CAB and DAWGS)

PeopleSoft COMR

The Chancellor's Office Migration Request (COMR) is a process by which campus technicians can request system changes in PeopleSoft PRD by the Chancellor's Office CMS team.

PeopleSoft Unmasked Data Request

To make a request for un-masked data in a non-production instance, use the the PeopleSoft Service Request form titled "Request for Database Refresh (Non-production Instances) with un-masked Data" which is located on the PeopleSoft Service Catalog page.

PeopleSoft Code Freeze

See PeopleSoft Code Freeze.

PeopleSoft Training

For information regarding CMS-HR Training, please contact Dana Shepherd at x4947 or  dshepherd@csuchico.edu

*Prerequisite Training Class