How to Build an Application in Slate
  • 22 Aug 2024
  • 1 minute read
  • Dark
    Light
  • PDF

How to Build an Application in Slate

  • Dark
    Light
  • PDF

Article summary

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

  1. Create periods. A period must be active in order to use the application editor.

  2. Create rounds. Rounds should be inactive until ready to go live.

  3. Create application-scoped fields and person-scoped fields where necessary.

  4. Create prompts for prompt-based fields.

  5. Create materials collected as part of the application.

  6. 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.

  7. Add test types to collect test score information.

  8. Configure payment integration. For information on payments in Slate, see Payments.

Phase 2: Build out the application

  1. Create Application Page-scoped forms

  2. Add conditional logic to forms, where necessary (optional)

  3. Create Page Keys in Application Logic to show/hide entire pages (optional)

  4. Use Application Editor to customize Slate delivered pages (optional)

  5. Use Application Editor to manage additional pages - e.g., Digital Portfolio (optional)

  6. 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

  7. Use Application Editor to add Page Keys (optional).

  8. Create submission requirements (hard/soft fails) using Application Logic.

  9. Create system email notifications for Slate Applications.

    • If importing applications, system emails will not apply. Create notification emails using Deliver.

  10. Create custom recommendation/school report forms (optional).

  11. Test the application(s).

Phase 3: Checklist, automations, & status page

  1. Create checklist items and assign fulfillment requirements

  2. Organize all checklist items into checklist groups

  3. Create checklist rules to assign items in checklist groups

  4. Add and activate application status rules from the Slate Template Library; adjust as needed

  5. 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.

  6. Build payment rules where appropriate


Was this article helpful?