To keep your integration running smoothly, there are steps you'll need to take to maintain the connection between the CAS API and Slate.
See our documentation on yearly maintenance for guidance and best practices with maintaining your integration.
CAS API Maintenance
CAS API access and subscriptions automatically roll over from one cycle to the next. For example, if you subscribed to the application.program.received event (application submitted) for BusinessCAS 2023-2024, when BusinessCAS 2024-2025 launches, a new subscription with the same settings as the original is automatically created for the application.program.received event for BusinessCAS 2024-2025.
If you want to change anything about your CAS API subscriptions (e.g., which payloads are delivered, which events trigger delivery, what formats the payloads are in, etc.), you'll need to delete the automatically created subscription and create a new one with the desired changes.
There are several types of maintenance that may need to be performed with your Slate integration, including:
- Regular maintenance: With a new CAS admissions cycle, you will likely need to update certain mappings. For example, you may need to append additional prompt values for the new application terms. Other items to consider include:
- Have any of the field names changed (e.g. "lastName" is now "last_name")?
- Have any of the possible values changed (e.g. "Monday" is now "MON")?
- If you are importing SSN you will need to make a copy of the SSN Source Format and update the import automation.
- CAS-level changes: A new admissions cycle in a CAS is an opportunity for the CAS to respond to the needs of applicants and schools by changing what information is collected or how it is collected. For example, when the COVID-19 pandemic arrived, a question asking about hardships related to COVID-19 was added. Be on the lookout for changes to the CAS that may affect the information available to you. Questions to consider:
- Have any questions been added, removed, or changed on the CAS application?
- Have any application requirements been added, removed, or changed?
- Has Liaison made any changes to the CAS platform that might affect your data integration?
- Program-level changes: A new admissions cycle in a CAS is an opportunity for each school to update the way their programs are configured to better attract applicants or to find better-fit students. Schools may change the way program properties (delivery, campus, start term) are used and they may change the way transcript collection, custom questions, documents, and recommendations are configured for any or all programs. Be alert to these changes to program configuration that may affect the information available to you. Questions to consider:
- Has your institution added, removed, or changed any custom questions on your CAS application?
- Has your institution added, removed, or changed any application requirements (materials required for review)?
- Admissions process changes: Over time, schools may change their business processes for managing the admissions funnel (i.e., recruitment, application, review, decision, matriculation) in pursuit of better outcomes for the institution, staff, and students. Changes to your business process will likely change how you use Liaison software in managing your admissions funnel. For example, you may decide to change how you import in progress applications (as unsubmitted applications instead of prospects or vice versa). Pay attention to admissions business process changes and how they may affect your use of Liaison software. Questions to consider:
- Has your intended use for CAS data in Slate changed?
- Does that change require you to move applications earlier or later in the admissions funnel?
- Do you need to transfer any additional data points to serve the new purpose?
- Do you need to transfer any additional data points to meet the needs of downstream units on campus?