Application Creation Form

An application creation form lets applicants create and submit an application in Slate through the submission of a form. Login is not required to access or submit the form by default, but can be configured if desired. You can use the form as:

    • A shorter version of your primary application (like a fast app)
    • A more user-friendly way of creating an application for a particular purpose, such as a scholarship, an honors application, or a specific program
    • A two-part process that enables applicants to start an application quickly, so that the applicant can subsequently be sent login credentials to finish the application through the traditional application architecture at a later date

An example Application Creation Form

An application creation form can be used if applicants are not required to provide the following within the form in a "traditional" Slate-hosted application manner:

  • Recommendations
  • Portfolio
  • Video Essay
  • School Report


Periods and Rounds

Before creating an application creation form, configure the following:

  1. Create an Application Period. Application periods help keep application rounds organized. They designate applications as active or inactive. Think of the application period as an on/off switch for your applications.
  2. Create an Application Round. Application rounds classify a distinct category of application types in an application period. Using separate application rounds in a single application period is helpful if there are separate application deadlines and decision notification dates for your different types of applications.

Creating the Form

  1. Select Forms on the main navigation bar.
  2. Click New Form.
  3. Enter a Page Title to name the form and click Save.
  4. Click Edit Form and retain the default fields on the form.
  5. Click Edit Properties. In the dialog box, set the Scope to Application Creation. Setting this scope allows the form to serve as the foundation of your application.
  6. For Security, consider the two optional settings: 
    • Require secure link/login: When selected, the form submitter must sign into their existing account to access the form. Additionally, filters for previously captured data points will be available for conditional logic. For example, a process might call for a form field to appear based on previously captured data points for Citizenship.
    • Allow secure link/login filters: When selected, the filters made available with "Require secure link/login" can be accessed, but no login is required for the form submitter. Slate can still access the record data, typically through query string parameters. Be aware that if a student who is not logged in opens the form through an open link, Slate will not b able to identify them, so some filters may not work. It is a best practice to thoroughly test filters to be sure that form fields, sections, and prompts appear conditionally as expected.
  7. Click Save and continue editing the form.

Add Form Fields

In addition to any application-scoped custom fields and personal information fields added to the form, it is necessary to include the App:Round and Generate PIN fields.

App: Round

This field will include a selection list of all rounds available in your database and must be a required field.

  • Add a field (such as a multi-select list) and map it to Application Fields > App: Round.
  • If the applicant needs to make a Round decision, you can use the right conditions to suppress unnecessary Rounds from the selection list. You can create filter criteria to exclude these values from being present (current date of 2050, for example).
  • If the applicant does not need to decide on the appropriate Round selection, the field can be marked as Hidden with a default round value set. If using a default value, this field should not have conditional logic applied to it. 
  • Only map the App:Round field on your form once in either scenario. The field should either be visible or marked as Hidden.
Generate PIN

This field is required to generate a merge field for the applicant's PIN that can be included in a form communication to send the applicant login credentials.
  • Add a select list or option buttons field and map it to Record > Generate PIN.
  • Set a default value of 'Yes' and configure the field as hidden.


When mapping to the App:Round field, it is important to avoid setting the field to "Hidden" and "Read Only." If this combination is used, Slate will not create a value for the Round field, no application will be created, and the form will not work as intended.
Not required but should be considered
App: Submitted Flag

When the default setting is set to 'Yes', the application will be set as submitted. The submission date will be set to the date of the form submission.

If this field is not mapped, applicants can be directed to the apply page to complete and submit the entire application.


Consider if an applicant may have an application with the same type in progress
App: Round Always Create

When set to 'Yes,' Slate will always create a new application using the Round specified in the import and will not attempt to match onto an existing application in that Round. When set to 'No,' Slate will match on the rank one application regardless of Round.
App: Round Override 
If mapped, Slate will attempt to match onto an existing application using those mappings selected.
App: Round Use Existing

When set to 'Yes,' Slate will use the rank one application in an active application Period, even if the Round of the existing application does not match the Round specified in the import.
App: Round Use Existing and Update

When set to 'Yes,' Slate will use the rank one application in an active application Period, even if the Round of the existing application does not match the Round specified in the import. This setting will also update the existing application's Round to what was mapped in the import.


You should use only one of these special field mapping destinations at a time. When using one of these field mapping destinations, it should be marked as Hidden and set with a default value of "Yes."

Confirmation and Login Information

Because the scope of this form is Application Creation, use form communications to create communications that include applicant login information. This ensures that the applicant receives login credentials immediately and that there is a consistent approach to communications for all applications created. It potentially prevents students from receiving “duplicate” communications if they submit applications through various means.

To set up the mailing to confirm the form submission or application creation and to inform an applicant of login details:

1. From the Application Creation form summary page, click Edit Communications.

2. Click New Mailing.

3. Enter the appropriate configurations and select Save.


4. When editing the message, include the 'sys-pin' merge field.

This merges the PIN generated during the submission of the Application Creation form into the confirmation mailing so that the applicant receives their login credentials and can access the status page immediately.

5. Add a hyperlink in the confirmation mailing to direct applicants to the status page. Append "?id=" and the 'Form-Person-ID' merge field to the end of the login URL. When configured this way, the hyperlink directs applicants to the login page, where they are asked to enter the PIN provided in the mailing and their birth date before being prompted to create and set a new password.


You can configure a separate form communication on the Application Creation form to create a confirmation page to acknowledge the form submission and instruct the applicant to check their email to receive their login credentials.

Additional Optional Form Fields

The Application Creation form provides access to some optional Slate standard settings that can be used for matching and submission capability. You can find the following in the list of application fields on the form:

Optional for matching and submission functionality
App: Priority

When added, you can use priority to set the rank of an application.
  • Priority (high, then normal, then low)
App: Submitted Date

Captures the date the form has been submitted. The most recent submission date is reflected if a form is submitted more than once.
App: Submitted Date (Force Update) If a submitted date exists, this option forces an update to an existing submitted date.
App: Deadline Override
Used in conjunction with the round field to override the round's deadline.

  Try a Slate Example

Suitcase ID: f242d4ab-b4f2-41ab-8f08-abe8cf289893:slate-applications


Troubleshooting Common Application Creation Form Issues

Here are some common application creation form issues and initial troubleshooting steps you can take. If these steps do not help to resolve your issue, we are happy to help with a Service Request submitted by your institution.

My application creation form is not creating an application upon submission.

An application will not be created upon submission if a Round is not set correctly. Ensure that you've mapped to your Round and configured the field appropriately: if there is only one round, set the Default Value to this round and check the Hidden option. If there are multiple options for the applicant to choose from, ensure that the field is not Hidden and check the Required option. If you need to curate the list of Rounds that may be selected, you can just build logic in the Edit Prompt Conditions window to avoid unnecessary Rounds from a selection.

If you have used Briefcase or Suitcase to import your application creation form and are using the "Override system prompts" checkbox, you will want to verify that your Round prompt is mapping to the appropriate Round ID post-import.

When collecting data on previously attended schools on our application creation form, any name entered appears in all school name fields.

Each section intended to collect school data will need to given a separate group number and separated by section breaks. The best practice consists of using a hidden school-scoped CEEB Code field in conjunction with the school name field; you can configure both of these fields to be set to the same group and use their respective auto-suggest features for a quick and easy process.

Data in my field(s) are not showing upon submission.

This can occur when the same field is mapped multiple times in your form. If the applicant qualifies for multiple submissions of this field, Slate will work from top to bottom and use the last value provided from these fields, which can nullify the value provided by the applicant. Whenever possible, it's best practice to map a field once per form and use prompt logic to show the appropriate prompts for selection. 

My widgets in my application creation form aren't working.

At this time, widgets are not compatible with application creation forms. If widgets are necessary, consider having the applicant jump directly into a Slate Hosted application (Direct Round URLs can make this more manageable if you are only reaching out to students for a specific round) or use the App Creation form as a fast application to get them started and then direct them towards your Slate Hosted application via the form communication that provides them with their account information. They can then provide the necessary material in the application itself or from their status portal post-submission.

Was this article helpful?
21 out of 26 found this helpful