This article provides guidance for production campuses on the steps to follow when requesting a non-production CHRS environment connection to their own masked Campus Solutions environment.
Overview
Campuses requiring full CHRS/CS integration for CS development or specific testing scenarios (e.g., Tools Testing, Open Enrollment), where H*CHRPSA/H*CHRPSB does not meet their needs, must submit a ticket.
Before submitting the request, campuses are responsible for:
- Ensuring that the refresh of their masked Campus Solutions (CS) environment aligns with the designated CHRS environment.
Once given the green light, campuses must:
- Establish a database link from their masked CS environment to the designated CHRS environment.
- Complete the required integration setup within their own masked CS environment.
Campuses can connect their own masked CS database to any of the CHRS production support databases identified on the CHRS Non-Production Environments page.
Submit Request
Step 1: Submit a ServiceNow ticket:
- Type: Request
- Category: CMS-CHRS
- Subcategory: Integration
- Ticket Short Description:
- In the ticket short description, indicate that your campus needs to have CHRS connected to your own masked CS environment (example: Request for H*CHRHCA to Connect to C*FULTST-Fullerton)
- Description:
- In the description provide the following:
- CS Database Name
- CS Database Clone Date
- CS URL ( Under CSU_CHRS_CS_INTEGRATION_POST)
- CHRS Database Name
- Reason for Request (example MP, Tools, Open Enrollment testing)
- In the description provide the following:
The CS environment to be connected must be masked.
Step 2: CMS will complete the necessary steps to configure integration in the requested non-production CHRS environment, and update ServiceNow ticket that campus can proceed to connect their own masked CS environment.
Step 3: Campus completes Integration Configuration in CS
Job Aid: Configure Campus Masked CS to CHRS
End of Article