---
title: "Optional Source Formats for Liaison CAS"
slug: "optional-source-formats-for-liaison-cas"
updated: 2026-03-06T21:54:48Z
published: 2026-03-06T21:54:48Z
canonical: "knowledge.technolutions.net/optional-source-formats-for-liaison-cas"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Optional Source Formats for Liaison CAS

There are two optional source formats available, described below, that may be configured if desired:

1. All CAS by Liaison - In Progress Applications
2. All CAS by Liaison - Coursework
3. All CAS by Liaison - SSN

> [!CAUTION]
> 🔔 Important!
> 
> Starting September 2025, in the scheduled delivery feature in WebAdMIT, scheduled jobs will be disabled if there are consecutive failures. Specifically, if WebAdMIT is unable to connect to the Slate SFTP after 10 consecutive attempts (this includes two retries for each attempt for a total of 30 connection attempts), the export job will be disabled in WebAdMIT.

## 1. In Progress Applications Source Format

Applicants who are **In Progress** have selected at least one of your programs, but have not yet submitted their application. Depending on the CAS, you may be able to receive full or partial data for these applicants. Consult Liaison's documentation for your CAS to determine if there are any [visibility restrictions on In Progress applications](https://help.liaisonedu.com/WebAdMIT_Help_Center/Documents_and_Reference_Guides/Data_Visibility_of_In_Progress_Applicants).

### Add the Source Format

To add the **All CAS by Liaison - In Progress Applications**source format:

1. Select **Database** from the top navigation bar and select **Source Format Library**.
2. Search for "All CAS by Liaison - In Progress Applications" and select **Add**.
3. Navigate to the new source format and click **Edit**.
4. On the **Import Automation**tab, update the **Import Path/Mask**field to specify the file path and file name pattern that the source format should use to pick up the file. For example: **liaison/casapi-app-started_*.csv**

[![mceclip0.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/rzr6fefvoekcdf2rts9jamceclip0.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/rzr6fefvoekcdf2rts9jamceclip0.png)

These file names will be configured in the [CAS API subscription step](https://help.liaisonedu.com/Integration/CAS_API/CAS_Slate_Integration/Configuring_Automation/03_Creating_Data_and_Document_Subscriptions).

For example, in the subscription, to configure the data files to correspond with the Import Path/Mask value **liaison/casapi-app-started_*.csv**, the following settings in the CAS API subscription can be used:

```plainText
 "sftpBaseDirectory": "/incoming/liaison/",
                "sftpPathTemplate": "casapi-app-started_
                ___
                _.csv"
```

***Note****: The user account added in the previous step has access to the****/incoming/liaison/****directory. If you choose to configure the CAS API subscriptions to deliver data files to different directories, then the user account****must****be updated to grant it access to those additional directories. Using the example path and file name pattern shown above, the pre-configured access settings can be used.*

> [!CAUTION]
> 🔔 Important!
> 
> You will not be able to map any fields until you receive or manually upload a file from Liaison.
> 
> Be sure to use a sample file delivered by the CAS API subscription for an in-progress application to ensure that all possible data points are included. By default, blank/null values are not sent via CAS API subscriptions, so if you need to adjust remap settings for a particular source field, and you do not see it on the Fields page, you will need to upload this sample file again.

### Configure the Remap Settings

To configure the remap settings for the **All CAS by Liaison - In Progress Applications** source format:

1. Select **Database** from the top navigation bar and select **Source Formats**.
2. Find the **All CAS by Liaison - In Progress Applications** source format and select **Remap** to confirm destinations and to set up additional data mappings for this source format.
3. After selecting Remap, you will see all of the Slate destination fields currently mapped for the data points included in the file.

There is a **unique for merging** field that is used to properly match subsequent application data to the appropriate person record within Slate. This field is pre-mapped in the All CAS by Liaison - In Progress Applications source format:

- CAS/Liaison Person ID

This field is automatically created during an **overnight process** that occurs after you have added the All CAS by Liaison - Applications source format. **The following field is pre-mapped and *should not* be adjusted, nor should other fields be mapped to this destination.**

| Source Field | Destination Field |
| --- | --- |
| casApplicantId | CAS/Liaison Person ID |

> [!CAUTION]
> 🔔 Important!
> 
> This data is considered in progress, and it does not contain a completed application. As such, application-scoped fields should not be mapped. When an application is submitted, all application data points are sent in the submitted applications API subscription configured above.

> [!NOTE]
> 💡 Tip
> 
> Refer to [Liaison's documentation](https://help.liaisonedu.com/WebAdMIT_Help_Center/Documents_and_Reference_Guides/Application_Statuses_Reference_Guide) for more information about the different application statuses.

#### What should I do if my institution accepts multiple CAS applications?

Refer to the section [Multiple CAS Applications](/docs/optional-source-formats-for-liaison-cas#activation) below.

#### How do I activate the import?

Refer to the section [Activation](/docs/optional-source-formats-for-liaison-cas#activation) below.

## 2: Coursework Source Format

The All CAS by Liaison - Coursework source format will import coursework information entered on the application at the point of verification. Learn more about CAS coursework verification in Liaison's [Applicant Processing Reference Guide](https://help.liaisonedu.com/WebAdMIT_Help_Center/Documents_and_Reference_Guides/Applicant_Processing_Reference_Guide#Verification). Each course entered on the application will be represented by its own row in the coursework file.

### Add the Source Format

To add the **All CAS by Liaison - Coursework**source format:

1. Select **Database** from the top navigation bar and select **Source Format Library**.
2. Search for "All CAS by Liaison - Coursework" and select **Add**.
3. Navigate to the new source format and click **Edit**.
4. On the **Import Automation**tab, update the **Import Path/Mask**field to specify the file path and file name pattern that the source format should use to pick up the file. For example: **liaison/casapi-app-coursework_*.json**

[![mceclip0.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/t2cujo0tn0qfpdrdvdmdwgmceclip0.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/t2cujo0tn0qfpdrdvdmdwgmceclip0.png)

These file names will be configured in the [CAS API subscription step](https://help.liaisonedu.com/Integration/CAS_API/CAS_Slate_Integration/Configuring_Automation/03_Creating_Data_and_Document_Subscriptions).

For example, in the subscription, to configure the data files to correspond with the Import Path/Mask value **liaison/casapi-app-coursework_*.json**, the following settings in the CAS API subscription can be used:

```plainText
 "sftpBaseDirectory": "/incoming/liaison/",
                "sftpPathTemplate": "casapi-app-coursework_
                ___
                __.json"
```

***Note****: The user account added in the previous step has access to the****/incoming/liaison/****directory. If you choose to configure the CAS API subscriptions to deliver data files to different directories, then the user account****must****be updated to grant it access to those additional directories. Using the example path and file name pattern shown above, the pre-configured access settings can be used.*

> [!CAUTION]
> 🔔 Important!
> 
> You will not be able to map any fields until you receive or manually upload a file from Liaison.
> 
> Be sure to use a sample file delivered by the CAS API subscription for coursework to ensure that all possible data points are included. By default, blank/null values are not sent via CAS API subscriptions, so if you need to adjust remap settings for a particular source field, and you do not see it on the Fields page, you will need to upload this sample file again.

### Configure the Remap Settings

To configure the remap settings for the **All CAS by Liaison - Coursework**source format:

1. Select **Database** from the top navigation bar and select **Source Formats**.
2. Find the **All CAS by Liaison - Coursework**source format and select **Remap** to confirm destinations and to set up additional data mappings for this source format.
3. After selecting Remap, you will see all of the Slate destination fields currently mapped for the data points included in the file.

There is a **unique for merging** field that is used to properly match the coursework file to the appropriate person record within Slate. Another **unique for merging** field is mapped to associate each course with the appropriate school record. These fields are pre-mapped in the All CAS by Liaison - Coursework source format:

- CAS/Liaison Person ID
- CAS/Liaison School ID

These fields are automatically created during an **overnight process** that occurs after you have added the All CAS by Liaison - Applications source format. **The following fields are pre-mapped and *should not* be adjusted, nor should other fields be mapped to these destinations.**

| Source Field | Destination Field |
| --- | --- |
| casApplicantId | CAS/Liaison Person ID |
| collegeAttendedId | School: CAS/Liaison School ID |
| id | School Courses: School Course: External ID |

#### How should I map the term or semester?

This depends on your processes. Some institutions choose the **Semester** date field to store this data, others institutions use the prompt-based **Term**field (prompt key *course_term*), and others store data in both fields.

Within the data, the source field **termYear** contains the year that the term began. This can be mapped to **School Course: Semester**, but note that because Semester is a date field, the date will be stored as January 1 of that year, since the month and day are not included in the data.

If your institution stores data in the **Term**field, the **term**, **termType**, and **termYear** fields can be mapped to **School Course: Term**as a field fusion, should your course term prompts require that level of specificity.

#### What should I do if my institution accepts multiple CAS applications?

Refer to the section [Multiple CAS Applications](/docs/optional-source-formats-for-liaison-cas#activation) below.

#### How do I activate the import?

Refer to the section [Activation](/docs/optional-source-formats-for-liaison-cas#activation) below.

## 3. SSN Source Format

The All CAS by Liaison - SSN source format will import social security numbers for students. Learn more about CAS coursework verification in Liaison's [Applicant Processing Reference Guide](https://help.liaisonedu.com/WebAdMIT_Help_Center/Documents_and_Reference_Guides/Applicant_Processing_Reference_Guide#Verification). Each course entered on the application will be represented by its own row in the coursework file.

### Add the Source Format

To add the **All CAS by Liaison - SSN**source format:

1. Select **Database** from the top navigation bar and select **Source Format Library**.
2. Search for "All CAS by Liaison - SSN" and select **Add**.
3. Navigate to the new source format and click **Edit**.
4. On the **Import Automation**tab, update the **Import Remote Server**field and replace the [ENTER USER IDENTITY ID HERE] with the USER IDENTITY ID provided by Liaison and the [ENTER YOUR API KEY HERE] with the API Key provided by Liasion:
5. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image-RFIPW6OQ.png)

> [!CAUTION]
> 🔔 Important!
> 
> You will not be able to map any fields until you receive or manually upload a file from Liaison.
> 
> Be sure to use a sample file delivered by the CAS API subscription for social security numbers to ensure that all possible data points are included. By default, blank/null values are not sent via CAS API subscriptions, so if you need to adjust remap settings for a particular source field, and you do not see it on the Fields page, you will need to upload this sample file again.

### Configure the Remap Settings

The remap settings for the **All CAS by Liaison - SSN**source format are pre-configured

Select **Database** from the top navigation bar and select **Source Formats**.

1. Find the **All CAS by Liaison - SSN**source format and select **Remap** to confirm destinations and to set up additional data mappings for this source format.
2. After selecting Remap, you will see all of the Slate destination fields currently mapped for the data points included in the file.

There is a **unique for merging** field that is used to properly match the coursework file to the appropriate person record within Slate. Another **unique for merging** field is mapped to associate each course with the appropriate school record. These fields are pre-mapped in the All CAS by Liaison - SSN source format:

- CAS/Liaison Person ID

This field is automatically created during an **overnight process** that occurs after you have added the All CAS by Liaison - Applications source format. **The following fields are pre-mapped and *should not* be adjusted, nor should other fields be mapped to these destinations.**

| Source Field | Destination Field |
| --- | --- |
| casId | CAS/Liaison Person ID |
| SSN | Record: SSN |

#### How do I activate the import?

Refer to the section [Activation](/docs/optional-source-formats-for-liaison-cas#activation) below.

## Multiple CAS Applications

If your institution accepts multiple CAS applications (e.g., Business CAS and Graduate CAS), additional CAS API subscriptions can be created. The **same source format** can be used to import the data from multiple subscriptions. To do this, use the same SFTP Path Template for each CAS API subscription.

## Activation

Use the same [testing steps](/v1/docs/liaison-cas-applications-integration#step-4-testing) described in the [Add the Applications Source Format](/v1/docs/liaison-cas-applications-integration#application-source-format) section in this article. Once you have finished testing the remap configurations, the source format can be activated in production:

1. In the **All CAS by Liaison - In Progress Applications** source format, click **Edit**.
2. Update the **Remap Active** flag to **Active**.

*Note: When this flag is active, data for existing files uploaded on or after the Remap As Of Date that are Awaiting Import will be imported using the remap settings as they are currently configured.*

[![mceclip1.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/3u9q3emo0imn921twi6wmceclip1.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/3u9q3emo0imn921twi6wmceclip1.png)
3. Click **Save**.
