- 02 Apr 2025
- 1 minute read
- Print
- DarkLight
- PDF
Introduction to Applications in Slate
- Updated 02 Apr 2025
- 1 minute read
- Print
- DarkLight
- PDF
Slate was tailor-made to handle applications.
Building a Slate-hosted application is a powerful way to manage, streamline, and hyper-personalize the application process. You can also import applications from external sources.
Follow these steps to build out your application:
Phase 1: Initial setup
📝 Steps one through five apply to both imported applications and the Slate-hosted application.
Create periods. A period must be active in order to use the application editor.
Create rounds. Rounds should be inactive until ready to go live.
Create application-scoped fields, person-scoped fields where necessary, and prompts for prompt-based fields.
Create the materials to be collected as part of the application.
For imported applications, add & remap application source formats from Source Format Library. If a source format is not available in the Source Format Library, create a custom New Source Format.
Add test types to collect test score information.
Configure Slate Payments.
Phase 2: Application structure
Create Application Page-scoped forms.
(Optional) Add conditional logic to forms, where necessary
(Optional) Create Page Keys in Application Logic to show/hide entire pages
(Optional) Use Application Editor to customize Slate delivered pages
(Optional) Use Application Editor to manage additional pages - e.g., Digital Portfolio
Use Application Editor to add custom form pages. These pages can all be built in a more sustainable manner using Forms:
Custom App Page (Special Use Only)
Essays (Retired)
Instructional Page
Upload Material
(Optional) Use Application Editor to add Page Keys.
Create submission requirements (hard/soft fails) using Application Logic.
Create system email notifications for Slate Applications.
If importing applications, system emails will not apply. Create notification emails using Deliver.
(Optional) Create custom recommendation/school report forms.
Phase 3: Checklists, automations, & the status page
Organize all checklist items into checklist groups
Create checklist rules to assign items in checklist groups
Add and activate application status rules from the Slate Template Library; adjust as needed
Use Application Editor to modify the Slate delivered status page or create custom status portal using the Portal Editor (Optional).
The status page settings pertain to a Slate-delivered status page only. If using a custom status portal, edits can be made directly to the status portal using the Portal Editor.
Build payment rules where appropriate
➡️ Up next: Introduction to application periods and rounds
Your first step in building your Slate application is understanding how periods and rounds shape your application structure.