CSI Residency Status Determination Automation
Status
In Development
Audience
Staff and Students
About This Project
Currently, determining which students need to confirm or establish residency status is a complicated issue that is done in Element 451 based on tasks that are assigned to students via Workflow Rules. These rules are associated with the passback information from PeopleSoft and have been created to assign the tasks. The tasks are what drives the residency team to know which students need to be looked at. However, the rules don’t seem to be working as designed, and there are cases where a student may get multiple residency tasks assigned that shouldn’t be, and cases where a student wasn’t assigned a task at all when they needed one. Even when the tasks work as expected, staff have to update residency in Element 451 and in PeopleSoft manually.
Objectives:
The objective of this project is to automate the process of determining which students need to confirm or establish residency status, and eliminate the need for manual updates in Element 451 and PeopleSoft. In addition, it should also be determined which system, PeopleSoft or Element, should be used to move the student through the residency process. The new process should be designed to:
Accurately identify which students need to confirm or establish residency status.
Streamline the process for residency team to review and update student residency status.
Eliminate manual updates in Element 451 and PeopleSoft.
Timeline
Fluid page(s) for Residency development:
Demo for FSCJ 08/22/2023
Demo for FSCJ 08/24/2023
Internal testing will begin 09/05/2023
FSCJ user testing 09/18/2023
Deploy to production 10/02/2023
Inbound Integration (From Element to PeopleSoft):
Internal testing to start 08/28/2023
FSCJ user testing 09/11/2023
Deploy to production 10/02/2023
Support
Contact IT through the standard channels, available at https://help.fscj.edu.
