How to Build an Application in Slate

Article summary

Did you find this summary helpful?

Thank you for your feedback

Building a Slate-hosted application is a powerful way to manage, streamline, and hyper-personalize the application process.

Follow these steps to build out your application:

Phase 1: Initial setup

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 and person-scoped fields where necessary.
Create prompts for prompt-based fields.
Create materials 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 payment integration. For information on payments in Slate, see Payments.
- If using Slate Payments, please read the following articles:
  - Setting up Slate Payments
  - Slate Payments FAQ
- If using a third party vendor, please read Using an External Processor to Collect Payments through Slate.
  - If payments will be accepted via a third party vendor, submit a request to the Payments Integration team 30-60 days in advance of application go-live date.

Create Application Page-scoped forms
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 (optional)
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
Use Application Editor to add Page Keys (optional).
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.
Create custom recommendation/school report forms (optional).
Test the application(s).

Create checklist items and assign fulfillment requirements
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

Was this article helpful?

Table of contents