Overview of Testing Your Integration

It's important to test your integration to confirm it is producing the records you need for your processes. When testing, pay special attention to any custom mappings you've added to the standard Source Formats.

We recommend you test your integration using our general guidance documentation. For more information, also see the Slate Knowledge Base.

Recommended Testing Pattern

If you are already accepting applications through a Liaison CAS, we recommend you test using Liaison Production data. Otherwise, we recommend you test using Liaison prelaunch data by going to the prelaunch Application Portal and creating test applications. Regardless of which CAS data you are using, we recommend you test your data mappings in the Slate Test Environment. Documents will not be imported to the test environment and must be tested in Slate Production. See Slate Documentation for a comparison of the behaviors of the test and production environments.

Overview of Environments

Liaison offers two environments:

Delivery of Test Application Data

After creating your subscriptions from prelaunch, you can trigger the delivery of test application data and documents by following these steps:

  1. Navigate to the appropriate prelaunch Applicant Portal for the CAS and cycle of interest. If needed, contact Liaison's Client Support Specialist team or a member of your account team directly for the prelaunch Applicant Portal link.
  2. Create an account. Usernames are based on email addresses, so if you need multiple accounts, you'll have to use alias email addresses. Keep in mind, though, that an individual email address can log in to many different CASs across many different cycles. An application to an individual CAS/cycle can be designated to many different programs.
  3. On the Add Program page, scroll down to find your institution's programs and select at least one. Selection triggers the program.application.selected business event, depending on In Progress visibility.
  4. Navigate to the My Application tab and complete the application. Periodically, application updates will trigger the application.updated business event, depending on In Progress visibility.
  5. Upload some documents in the Supporting Information and Program Materials sections. These will trigger the file.*.updated subscription details.
  6. Submit the application after filling out the required answers. Submission triggers the application.program.received business event.