On a form’s overview page, select Edit Form → Edit Properties to edit the properties of the form itself, including its scope, layout, merge fields, and more.

General

Scope

Scope describes the Record or database object the form is tied to. Submissions of the form will modify the corresponding record or database object type.

• Person: Person-scoped forms collect or update information on a person and do not require them to be an applicant (for example, Inquiry Form).

• Application: Application-scoped forms require login and for the applicant to have at least started an application on their record (for example, Decision Reply Form).

• Application Creation: Application Creation forms do not require that the student be logged in and the form can be accessed publicly. This scope allows for the creation of an application upon form submission. In order for an application to be created, "Round" must be mapped. For further information, review Application Creation Forms.

• Person Page: Person Page-scoped forms are used to create custom tabs to display person-scoped data points on the student record. After creating a form with this scope, add a new tab using the Tab admin tool in Database to display this form as a tab on the student record.

• Application Page: Application Page-scoped forms can be used to create a custom application-scoped tab for displaying fields on the student record. Previously, they were also  used to create custom pages in the Slate-Hosted application. That functionality has been replaced by the Slate-Hosted Application Page form scope.

• Slate-Hosted Application Page:  This scope is used to create or add a custom form (page) to your Slate-Hosted Application. Unlike the Application Page scope, this form scope  allows access to widgets like Reference, School Report, and Courses.

• Reader: Reader-scoped forms should be used when creating forms to display within the reader (for example, Reader Review form).

• Dataset: Dataset-scoped forms, for form and event registrations, are intended only for a particular dataset (such as organization contacts, organizations, or alumni volunteers). Note that forms and events scoped for a specific dataset will not add student records, and should not be used to register students.

• Form/Event Notes: This option allows the user to create a form that can be tied to a specific form or event for internal use. Once created, these forms become selectable options on a form or event (such as comments on college fairs or high school visits).

Dataset (dataset, dataset page scope only)

Specifies which dataset the form is associated with.

Multiple

Allows multiple submissions by the same registrant. If not selected, a new submission by the same registrant will update the existing registration, which is typically the desired behavior.

Require Checklist (application scope only)

This form can only be accessed if the record has the form as a checklist item.

Save for Later (application scope only)

This flag applies to only forms that are displayed on an applicant's status page and will enable the applicant to save an in-progress form to return to later to submit. This flag is appropriate for financial aid applications and other long forms.

Unsafe

Updates system fields even when the registrant has an application for the current period. This should generally remain unchecked, unless a particular form should update these system fields for applicants.

Learn more about how safe and unsafe behavior can affect your records here.

Security

• Require secure link/login: Selecting this setting requires the form submitter to 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 show up based on previously captured data points for Citizenship.

• Allow secure link/login filters: With this setting, the filters available with "Require secure link/login" can be accessed without requiring a login by the form submitter. Slate can access the record data, typically through a query string parameters. Be aware that if the student has come to the form from an open link without first being logged in, Slate will not be able to identify the student, and such filters will generally not work. Fully testing these filters is recommended to be sure that form fields, sections, and prompts conditionally appear as expected.

Update Only

When set, this form will not create new records and will only update existing records.

Notes Form

May be used to associate a Form/Event Notes Form for the collection and review of data pertaining to the event or form.

Layout

Defines the layout of all of the form fields on the form, unless overridden on the form-field level. Options include:

• Stacked: The text label appears above the form field’s content. Selected by default.

• Table: The label appears at left, the form field’s content at right.

Custom List Fields

Adds exports and creates custom registration columns to replace or supplement default registration columns in forms, events, and slots. When utilized for events and slots, these custom registration columns carry over into the "Launch Check In" page.

Merge Fields

Add personalized content to the instructional text or display labels in your form by adding merge fields. See Merge Fields on Forms for more information.

Widget Settings (page construction widget scopes only)

Widget Height

Adjusts the height of the widget pop up.

Widget Width

Adjusts the width of the widget pop up.