Application logic, including hard and soft fails, ensure applicants enter all necessary data prior to submitting an application.

  Try a Slate Example!

Use Suitcase to import the examples in this article (and others in this section) into your institution's database. These examples are also featured in the Clean Slate Showcase environment.

Using Testing Queries

Before you commit to using the application logic records, try a testing query by importing the Suitcase link in the second tab. These queries recreate the application logic records, taking advantage of the Query Builder's Preview Results function to ensure the records that should be receiving the hard or soft fails appear. If you only use the application logic records, you'll only see the number of records affected.

Application Logic Suitcase ID

082d8112-e41b-4fc5-aef5-9c7beef46969:slate-showcase

Testing Queries Suitcase ID

a04770f5-349d-4e95-a9c0-0c5d0b1ba3b0:slate-examples

Require Rank 1 Address

This submission requirement looks for applicants who do not have a rank 1 overall address, which can be considered an Active Address. Individual hard fails can also be made for mailing and Permanent addresses if that suits your business practice best. Add a filter of Address Type and select the one which is needed.

1. Type - Submission Requirement

2. Section: Custom Application Page, which will begin as "frm?"

3. Name - Provide the text that will display when the applicant is missing information.

4. Warning -Select Hard Fail.

5. Base - Configurable Joins - Application

6. Filters - Create a Subquery Filter (Aggregate - Not Exists).

Require Permanent Address

Prevents submission of the application if the applicant has not entered a permanent address.

1. Type - Submission Requirement

2. Section: Personal Information page, which will begin as "per -"

3. Name - Provide the text that will display when the applicant is missing information.

4. Warning -Select Hard Fail.

5. Base - Configurable Joins - Application

6. Filters - Create a Subquery Filter (Aggregate - Not Exists) that includes a filter for Address Type.

Require Mailing Address

Prevents submission of the application if the applicant has not entered a mailing address.

1. Type - Submission Requirement

2. Section: Personal Information page, which will begin as "per -"

3. Name - Provide the text that will display when the applicant is missing information.

4. Warning -Select Hard Fail.

5. Base - Configurable Joins - Application

6. Filters - Create a Subquery Filter (Aggregate - Not Exists) that includes a filter for Address Type.

Require Postal Code for US/CA Mailing Addresses

This hard fail looks for applicants missing a U.S. and Canadian citizenship postal code. Students residing outside of one of these countries will not see the hard fail.

1. Type - Submission Requirement

2. Section: Custom Application Page, which will begin as "frm?"

3. Name - Provide the text that will display when the applicant is missing information.

4. Warning -Select Hard Fail.

5. Base - Configurable Joins - Application

6. Filters - Create a Subquery Filter (Aggregate - Exists) with a nested Subquery Filter (Not Exists)

Require Citizenship Information

This example prevents submission of the application if the applicant is missing a primary citizenship.

1. Type - Submission Requirement

2. Section: Custom Application Page, which will begin as "frm?"

3. Name - Provide the text that will display when the applicant is missing information.

4. Warning -Select Hard Fail.

5. Base - Configurable Joins - Application

6. Filters - Create a Subquery Filter (Aggregate - Not Exists) for the field that should have a value saved.