Testing in the Production, the live ctcLink environment, can be dangerous. For this reason, multiple test environments are maintained for testing purposes. ctcLink colleges have their exclusive test environment called "PCD." The PCD test environment is available for colleges testing and query development. Testing in PCD can include practicing established business processes, developing new business processes, testing security access, developing queries, or researching "What would happen if I did X?" questions. Because PCD is a test environment, any EmplID can be used for testing purposes, including EmplIDs that belong to real students or staff.

The PCD test environment is "refreshed," or updated to match Production, on the first Monday of each month. This also means that any changes (or mistakes) made in PCD during the month will be erased with each refresh. Go wild with testing in PCD-- the slate is wiped clean with each refresh!

All staff members have access to the PCD test environment. The link to PCD is: https://pt-pcd.peoplesoft-nonprod-aws.ctclink.sbctc.edu/ptpcd/signon.html

Users new to PCD can establish their PCD logins by following the "First Time User?" link. Please contact your campus security administrator if you cannot log in to the PCD test environment.

Any testing that can occur in the PCD test environment should occur in the PCD test environment. If testing must take place in Production, colleges have three authorized test EmplIDs that can be used for testing. These authorized test EmplIDs are the only EmplIDs that can be used for testing in Production. Do not use any other EmplID for testing in Production.

Each college can update the bio demo information associated with its authorized EmplIDs. The EmplIDs can also be activated in program/ plan stacks, and term activated as needed. These EmplIDs can be used for a variety of testing purposes. Be careful to document the testing that occurs in Production and undo testing changes as needed. For example: If an authorized test EmplID is used to test an enrollment requirement, ensure that the authorized test EmplID is dropped from any classes that it is enrolled in so that it does not take up space in a class that could have been occupied by a real student.

Do not create additional test EmplIDs for testing in Production. Fake EmplIDs have severe impacts on a number of critical systems, including data, reporting, FTEs and Financial Aid. For more information, please contact your Registrar or submit a ticket to the SBCTC CS Support team.

Unapproved test EmplIDs are marked with an SUI service indicator upon identification by the SBCTC CS Support Team for deletion at a later date. Colleges can identify unauthorized test EmplIDs and mark them with an SUI service indicator, or submit a ticket when unauthorized test EmplIDs are identified. Do not remove SUI service indicators from unauthorized test EmplIDs.

If you have questions about how to use authorized test EmplIDs, please submit a ticket to the SBCTC CS Support team.