A Slate form updates or adds data to a Slate record or related data object. The form’s scope tells Slate which type of record to send the form submission data to. A person-scoped form will make updates to a person record, a dataset-scoped form makes updates to a dataset record, like funds or organizations, and an application-scoped form will make updates to an application record.
When you create a form, select Edit Form, then select Edit Properties. In the popup, you can select the form’s scope.
Form scopes fall under the following scope categories:
Records
Person
These forms should be used for things like your inquiry form, to collect or enter information on students while on the road, or for events that do not require a student to be an applicant. There are other use cases, but largely, this scope should be used to update anything related to the person record.
Application
Application-scoped forms are forms that get filled out on a per application basis (you might want a form to be filled out for each application a student might submit rather than just one for the person themselves). These forms require a login and a selection of an application round where the student has started an application. An excellent example of an application-scoped form would be a Decision Reply Form, where the student decides if they will attend your school based on their application and your decision on that application. If, when attempting to access your form via the URL, you are presented with a login page, the form scope has likely been incorrectly set to Application. It can be changed by modifying the properties in the form itself.
Application Creation
Similarly to the "Application" scope, Application Creation allows you to map to application field destinations. However, "Application Creation" does not require that the student be logged in—the form can be accessed publicly. This allows you to create an application for a person record upon form submission. For an application to be created, "Round" needs to be mapped, and "Submitted Flag" may also be mapped (this creates the application at a submitted status upon form submission). These fields can be set as "hidden" to ensure the same round is always created when a particular form is submitted.
Dataset
Forms with a dataset scope update and add data to the dataset with which they are related. When you select the Dataset scope, a list of the datasets to which you have access appear. Select a dataset to relate this form to that dataset.
Dataset-scoped forms for form and event registrations are intended only for a particular dataset (e.g., organization contacts, organizations, alum volunteers, etc.).
📝 Dataset records are distinct from person records: forms scoped to a dataset will not create or update person records.
Related
Reader Review Form (Application/Person/Dataset)
Reader-scoped forms should be used when creating forms that you wish to display within the reader. For example, your Reader Review form will be Reader scoped. The scope is likely incorrect if you are attempting to add your Reader Review Form to the Reader and do not see it as an option in the dropdown.
Event Survey
Configures the form as an event survey.
Unsubscribe Survey
Configures the form as an unsubscribe survey.
System
Form/Event Notes
Creates 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. Organizations often use these to comment on college fairs, high school visits, etc.
Material
Material-scoped forms add or update metadata associated with a material.
Source Metadata
Source-metadata-scoped forms add or update metadata associated with source formats.
Inbox Message Metadata
Configures the form to add or update metadata associated with an Inbox conversation.
Page Construction
Application Page
Application Page scope is used for forms that you wish to include in an application, or for a custom application-scoped tab that you would like to use to display fields on the student record. For example, if you would like to add a custom application page with questions that do not currently exist in the Slate Application template, you would use this scope.
Slate-Hosted Application Page
Slate-Hosted Application Page-scoped forms create custom pages that can be added to the Slate-hosted application through the Application Editor. Use this scope for custom application pages that need application-page behavior and support for page-construction widgets such as references or school reports.
Person Page
This scope is used to create custom tabs to display person-scoped data points on the person record. After creating the form with this scope, add a field with the ID tab_Tab Name and choose this form from the drop down list.
Dataset Page
Dataset Page-scoped forms are used for custom tabs on dataset records. Select the dataset when you set the form scope, then link the form to a dataset-scoped tab.
Reference Page
Reference Page-scoped forms provide the application page that hosts the reference process. A custom reference page typically works with a reference widget form and the external reference form sent to the recommender.
School Report Page
School Report Page-scoped forms create a custom school report page that a school official completes after a student requests a school report.
Page Construction Widgets
When you select this scope, the form you build is scoped to a widget. A widget in this context is like a form-within-a-form: you can add multiple widget forms to a host form, and the registrant can submit the widget form one or more times. Widget forms appear as popups, or widget modals, when the registrant adds or edits an item.
The various scopes you see in this category correspond to the Slate-hosted application pages of the same names.