After creating a Graduate Programs dataset and deadline entity, you can use that data in a Slate-hosted application to guide applicants, display program-specific information, and prevent invalid submissions.
This example uses a program prompt field, a hidden related dataset row field, an application-scoped entry term field, and a Graduate Program Dates entity.
⭐ Get Inspired
This article was adapted from a post by Technolutions staff in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? Let us know!
Collect the program and entry term
Add the program selection field and entry term field to an application-scoped page. The example uses an initial Welcome page to collect the applicant’s selected program and entry term before later pages evaluate program availability.
Slate-hosted application page configured to collect graduate program and entry term information
Application form containing a graduate program field, related dataset row field, and entry term field
Create a page key for unavailable program terms
Use a page key to display a separate page when the applicant selects a program and entry term combination that is not available. In the example, the applicant selected Accounting - MS for Fall 2028, but Fall 2028 is not listed in that program’s deadline entity.
The page key uses two conditions:
The selected entry term does not exist on the selected program’s deadline entity.
A selected graduate program value exists.
Page key filter checking that the selected entry term does not exist on the selected graduate program record
Subquery filter comparing the selected application entry term to graduate program deadline entity terms
Page key filter confirming that a graduate program value exists on the application
Build the unavailable program page
Create an application page that tells the applicant the selected program is unavailable for the selected entry term and instructs them to return to the previous page to update their selection.
Program unavailable message
You can also use merge fields and Liquid Markup to display the available terms for the selected program. This gives the applicant enough information to update their selection without leaving the application.
Application page source using merge fields to display available graduate program terms
Liquid Markup configuration for listing available terms from the graduate program deadline entity
Code view of applicant-facing unavailable program page displaying available entry terms
Create a hard fail for deadline enforcement
Use application logic to prevent submission when the selected program’s deadline has passed. In this example, the hard fail compares the current system date to the deadline date stored on the selected program’s deadline entity.
Application logic hard fail configured for graduate program deadline enforcement
Hard fail subquery comparison between system date and the graduate program application deadline
Join from Application to the selected Graduate Program dataset record.
Join from the Graduate Program dataset record to the Graduate Program Dates entity.
Add a filter that compares the application-scoped entry term field to the corresponding entry term field on the deadline entity.
Add a comparison between the current system date and the relevant deadline date.
⭐ Best practice
Duplicate critical page key logic in a hard fail. A page key can guide the applicant, while a hard fail prevents submission if the applicant reaches the submit step with an invalid program or term combination.