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 2020-2021, when BusinessCAS 2021-2022 launches, a new subscription with the same settings as the original is automatically created for the application.program.received event for BusinessCAS 2021-2022.
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 have a static mapping that sets the application round for incoming CAS application data; with a new cycle, you'll want to update that static mapping. A big decision to make in terms of maintenance is whether you want to use a new Source Format for each CAS admissions cycle. You'll be able to continue using a single Source Format cycle over cycle, but making a copy for a new cycle might give you more flexibility to accommodate possible changes (see below for an overview of changes to be prepared to accommodate).
- 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.
- 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.
- Business 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 implement blind review in your faculty review process, in which case you'd need to update your review process configuration to hide the relevant data elements from the relevant reviewers. Pay attention to admissions business process changes and how they may affect your use of Liaison software.
For more information, also see the Slate Knowledge Base.
For support in your CAS data integration project, visit the Data Integration Help Center for project planning resources, instructions on Liaison tools, and best practices in CAS data integrations.
For support in using the CAS API, refer to our CAS API documentation:
For further support, contact the Liaison Client Support Specialist Team, or reach out to your Liaison Account Manager or Client Success Manager directly.