📚 Part of the series Application Building Phase II: The Slate-hosted Application

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 example 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 (hard fail library)

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

Testing queries Suitcase ID

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

Require name

This example prevents application submission if the applicant is missing a last name.

• Type: Submission Requirement

• Section: Select the application page that includes biographical information

• Name: Enter text to appear when applicant is missing name information

• Warning: Hard Fail

• Base: Configurable Joins: Application

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

Warn if middle name missing

Warn applicants if they did not enter a middle name. Since not everyone has a middle name, making this a hard fail would prevent applicants who do not have a middle name from being able to submit the application.

• Type: Submission Requirement

• Section: Select the application page that includes biographical information

• Name: Enter text to appear when applicant is missing middle name information

• Warning: Soft Fail

• Base: Configurable Joins: Application

• Filters: Create a Subquery Filter (Aggregate: Not Exists) for each field that should have a value saved. In this example, the middle name is a free text field: an export is required to identify those without a middle name added.

  

📖 More submission requirements you can create in Slate