In the Slate-hosted application, application logic determines whether an application can be submitted without a given piece of applicant information.

You can create two types of submission requirements for any data in a Slate-hosted application: hard fails and soft fails.

This section of the Knowledge Base provides a number of different examples of the types of application logic you can employ.

Hard fails

Hard fails warn that required data is missing from the application and must be provided before an applicant can submit their application.

For example:

• At least two letters of recommendation

• One essay

• Mobile phone

• Mailing address

• Permanent address

Soft fails

Soft fails warn that required data is missing from the application, but don’t prevent submission.

For example:

• Middle name

• Work experience

• Optional personal statement

Adding new application logic

To create a new submission requirement:

1. Go to Database →  Application Logic.

2. Select Insert.

3. Configure the following settings:

   • Status: Set the status to active for any logic that will be used in a Slate application. Inactivate logic that is no longer used. Any inactive logic can be reactivated at any time should a process call for it again.

   • Folder: Keep organized by using folders. Select Other to create a new folder.

   • Type: Select the type of application logic:

     • Submission Requirement: A submission requirement is a warning to the applicant that required data is missing from the application. Submission requirements can be created for any data in a Slate application.

     • Group/Page Key: Group/page keys are used to show/hide pages within a Slate application conditionally.

   • Section: Use section to select the page within the application on which the application logic is applied (for submission requirements only).

   • Name: Provide a clear name that indicates what page key or submission requirement is and what it is used for.

   • Warning: Choose if the submission requirement should apply as a hard fail or soft fail on a Slate application (for submission requirements only).

   • Group: Group is optional. Add a group to apply the requirement to only the application records who meet the group criteria. Slate will automatically include the filter criteria for the group in the requirement rule (for submission requirements only).

   • Base: Select the base for adding filters that define the records to which the application logic is applied.

   • Filters: Add filters to isolate that applicants who should see the message. See the next section for more detail.

4. Select Save.

Filters

You can apply filters to show requirements for a specific segment of the application population.

For example, an international applicant applying to a Graduate Round with interest in Engineering must submit the following materials particular to that program.

Submission requirements appear on the Review page of the application:

Active doesn't matter

Applicants see submission requirements on the Review page of the application before submitting the application.

If the applicant can access the Review page, the application round and period are active, and the deadline has not passed. Therefore, you do not need to filter on current application period or application submission status when making submission requirements.

Examples of submission requirements

The remainder of the submission requirements section provides examples of commonly used hard and soft fails:

• Require Biographical Information

• Require Address & Citizenship Information

• Require Custom Fields

• Require Materials

• Require Academic Information

• Require School Reports

• Require Employment Information

• Require Recommendations / References

• Require Video, Audio, and Slides (Digital Portfolio)

• Collecting Payments on the Application

• Require Payment to Submit Application

• Require Test Scores

• Require Relationship Data

• AI Identity Verification