The Enrollment Management Association (EMA) can generate data and documents for Standard Application Online (SAO) applications.

EMA has an automated process that sends application data and associated documents to the Slate SFTP server. The data and documents are then imported through an automated process using standard source formats in Slate.

Step 1: Creating a SAO ID

If your institution already receives data from the Standard Application Online, you likely have an application-scoped field representing the SAO Application ID in Database → Fields. If you find this field, you can move to the next section.

If you don’t have this field:

1. Select New Field.

2. Configure the following settings:

   • Status: Active

   • Scope Category: Records

   • Scope: Application

   • ID: sao_app_ID

   • Name: SAO Application ID

   • Folder: Keep fields organized by placing them in a folder. To create a new folder, select Other and enter a name.

   • Category: Select or create an optional field category.

   • Field Type: Free Text

   • Unique for Merging: Value contains a unique ID which identifies a single record for merging.

3. Select Save.

4. Select the link in the sidebar to force refresh the fields cache.

   

Step 2: Adding the Enrollment Management Association service account

To add the Enrollment Management Association service account to your database:

1. Go to Database → Slate Template Library.

2. Select refresh the Slate Template Library.  

3. Select OK.

4. Next to the Enrollment Management Association Service Account, select Add.

5. Select Add to confirm.

   To configure the Enrollment Management Association service account

6. Go to Database → User Permissions.

7. Select Service Account, Enrollment Management Association.

8. Select Edit User.

9. Select Roles.

10. Verify that SFTP Access is selected.

11. Copy the username.

12. Select Save.

13. Share the username with Enrollment Management Association to grant them SFTP access.

The Enrollment Management Association service account uses an RSA Keypair for authentication, so no password is needed.

Step 3: Adding the SAO application source format

To add the Standard Application Online (SAO) applications source format:

1. Go to Database → Source Format Library.

2. Enter Standard Application Online in the search bar.

3. Select Add.

🔔 Do not change the source format’s name or format settings. Notes and internal name can be edited.

You cannot map fields until you receive or manually upload a file from EMA.

Testing the source format

To test importing application data:

1. Complete the remap configurations in your production environment.

2. Refresh your test environment.

3. Activate the source format’s remap settings in the test environment.

4. Confirm that the behavior of the import matches what you expect.

Repeat as necessary until you are satisfied with the configuration of the remap settings.

Activating the source format

Once you’ve finished testing remap configurations, you can activate the source format in your production database:

1. Navigate to the Standard Application Online (SAO) source format and select Edit.

2. Set the Remap Active flag to Active.

3. Select Save.

Data for existing files uploaded on or after the Remap As Of Date that are Awaiting Import are imported using the remap settings you’ve configured.

Step 4: Adding the SAO Document Import source format

EMA generates PDF files associated with the applications delivered in the data files.

These files are associated with Slate records using unique IDs that come in through the Standard Application Online (SAO) source format.

You must configure these files as Slate materials using the SAO Document Import source format.

To add this source format to your database:

1. Go to Database → Source Format Library.

2. Search for "SAO Document Import".

3. Select Add.

Remapping the source format

To remap the source format:

1. Go to Database → Source Formats.

2. Select the SAO Document Import source format.

3. Select Remap.

4. Select Prompt Value Mappings.

5. Select Material.

6. For each SAO document type, select the Slate material type as which you want to store the document type.

Only document types that have been mapped to a valid Slate material type will be imported.

PDFs associated with unmapped document types will remain in the SFTP directory until they are mapped (and imported) or purged.

Mapping data points

The SAO Document Import source format contains 3 data points to map:

• File Name

• SAO ID (the app-scoped application ID)

• Document Type

Import Path/Mask

The standard process that runs to import the documents will pick them up from the /incoming/ema/ SFTP directory.

🔔 Leave the import path/mask setting as the default.