Require Custom Fields

Inserting Submission Requirements

Hard and Soft Fails can be added to an application through the Application Logic function within Slate:

  1. Select Database on the top navigation bar and select Application Logic.
  2. Select Insert.
  3. Enter the following configurations for each desired submission requirement:
    • Status - Make your requirement status Active.
    • Folder: Keep your records organized by putting them in a folder. Select Other to create a new folder.
    • Type - Type should be Submission Requirement.
    • Name - Provide the text that will display when the applicant is missing information.
    • Warning -Select Hard Fail or a Soft Fail.
    • Group - Group is optional. Add a Group here to quickly restrict the requirement to only the applicants who meet the group criteria you set up earlier. Slate will automatically include the filter criteria for the group in the requirement rule.
    • Base -  Select Applications as the base

Select the Light Bulb  for a complete listing of all setting descriptions.

Require a Custom Field

What the submission requirement does:

Prevents submission of the application if the applicant has not entered information for any of the specified fields.

Within the Application Logic configuration, set the following:
  • Section: Select the page where your custom fields appear.
  • Filters
    • Field Missing (Application) - Returns true if the selected field does not exist for an application.

  Who will see this submission requirement?

Applicants who are missing values for any of the selected fields.

  Best Practice

Be specific! Sometimes multiple fields can be combined and referred to within a single submission requirement on the application without confusing applicants; however, when combining a large number of items on a page that has many fields, it is often helpful to specify precise fields that are missing.

Important

Don't Combine Pages! If you require that applicants have previous work experience, select Hard Fail to prevent application submission without entering job history. Otherwise, select Soft Fail to simply display a warning.
Require Custom Fields with Multiple Scopes

What the submission requirement does:

Prevents submission of the application if the applicant has not entered information for any of the specified application-scoped or person-scoped fields.

Within the Application Logic configuration, set the following:
  • Section: Select the page where your custom fields appear.
  • Filters
    • Field Missing (Person) - Returns results for prospects who do not have a specified field values.
    • Field Missing (Application) - Returns true if the selected field does not exist for an application.

  Application vs. Person?

Use the Field Missing (Application) filter to find records that are missing any of the selected application-scoped fields.

Use the Field Missing (Person) filter to find records that are missing any of the selected person-scoped fields.

Use an OR between the filters to combine the person-scoped and application-scoped fields on the same page as a single submission requirement.

Who will see this submission requirement? Applicants who are missing either field value.

Require One of Two Sets of Custom Fields

What the submission requirement does:

Prevents submission of the application if the applicant did not complete both of the defined sets of fields.

Within the Application Logic configuration, set the following:
  • Section: Select the page where your custom fields appear.
  • Filters
    • Field Missing (Application) - Returns true if the selected field does not exist for an application.

  Why no "OR" operator?

If program selection causes different fields to conditionally display for applicants, use the Field Missing filter multiple times to require at least one set of the fields.

For example, if Concentration and Degree are conditionally displayed and required for engineering programs, and all other programs just require Minor, use this example to require either Minor or both Concentration and Degree.

The submission requirement will only appear for applicants who are missing any of the fields selected in both of the filters.

Who will see this submission requirement? Applicants who are missing both sets of field values.

  Best Practice

Keep it simple! If you find that your submission requirement logic is more complicated than simply requiring one of two sets of fields, use more than one submission requirement to accomplish the task. Simply filter on the Program and Field Missing.

Use the Field Missing (Person) filter to find records that are missing any of the selected person-scoped fields.

Use an OR between the filters to combine the person-scoped and application-scoped fields on the same page as a single submission requirement.

Require Custom Fields that Display Conditionally

What the submission requirement does:

Prevents submission of the application if the applicant did not complete one of the required fields, based on the applicant’s response to another field.

Within the Application Logic configuration, set the following:
  • Section: Select the page where your custom fields appear.
  • Filters
    • Field Missing (Application) - Returns true if the selected field does not exist for an application.
    • Program of Study - Returns applicants who have selected a specific value from the custom field.

  Who will see this submission requirement?

Applicants who selected Computer Engineering or Physics and are missing the Degree or Concentration fields.

Require Multiple Custom Fields that Display Conditionally

What the submission requirement does:

Prevents submission of the application if the applicant did not complete one of the required fields, based on the applicant’s response to another field.

Within the Application Logic configuration, set the following:
  • Section: Select the page where your custom fields appear.
  • Filters
    • Field Missing (Application) - Returns true if the selected field does not exist for an application.
    • Felony Flag - Returns applicants who have selected yes to the custom bit prompt based field.
    • Dismissal Flag - Returns applicants who have selected yes to the custom bit prompt based field.

  Who will see this submission requirement?

Applicants who respond affirmatively to the Felony or Disciplinary questions and are missing the associated explanation.

Important

Close the parentheses! When using logic that includes both ANDs and ORs, use parentheses to ensure the proper order of operations. Make sure you close all parentheses to avoid syntax errors on the Review page.
Was this article helpful?
2 out of 3 found this helpful