Slate provides a Slate.org Application Portal template that can be imported using Briefcase and edited in an institution's database. This portal is configured to display custom institutional information.
Briefcase: 33c9070d-c308-de8d-09ca-e175e2a4d1d2@slate-showcaseAdditionally, new Slate.org Application and Slate.org Organization portals can be created in the Portal Editor.
Important!
Be sure to enable Slate.org Application Sharing.
- Click Database in the top navigation bar and select Slate.org Application Sharing Settings.
- Review the Rounds, Application Status, Checklists, Materials, and Decisions sections.
- Click on an individual item to then select either
- Share with Slate.org institutions
- Do not share with Slate.org institutions
Click the Slate Scholar Lightbulb in the top left corner for a complete listing of all setting descriptions.
Once the Slate.org Applicant Display portal has been imported via Briefcase, the exports can be customized to return the data points to display in the portal.
Application Details
We'll start with a Configurable Joins - Application query to pull a list of exports that can be used as merge fields. For example, if you wish to display the applicant's entry term, major, and decision for your institution, you would add those exports to the query.
- From All Portals, select your Slate.org Application Portal from the list.
- Under Queries, click New Query.
- Configure the following in the New Query popup:
- Name: Application Data
- Type: Configurable Joins
- Base: Applications
- Click Save to start editing the query.
- Add any exports.
-
On the right, click Rename Exports. Make sure all export labels are lowercase, and use underscores, not spaces. Click Save.
Note
By default, the query also has a filter for GUID that should not be removed: it ensures the query will export the data of the applicant being viewed.
If you accidentally remove the filter and need to add it back, its custom SQL is as follows:
GUID = @identityNo other filters are necessary for this query. The GUID filter limits the results to just the applicant clicked on in the portal.
Sharing Decision Reasons
The custom join to Decisions accomplishes the following:
- Isolates decisions that have been released prior to today. This can be updated based on when you would like to share additional decision details.
- Selects decision codes that are also marked to be shared in the Slate.org Application Sharing Settings. Note: This is an example! You will need to update this decision code filter to pull codes from your Slate database specifically.
- Sorts by Decision Release Date
- Includes a Row Offset of '1', which will pull the most recently released decision.
Events
A Configurable Joins - Form Response query will allow you to pull events that students have registered for or attended. This is an example of how you can help counselors see how their students have engaged with your campus.
This query has an identity filter that looks for person and application-scoped form responses:
fr__JID_.[record] IN (@identity,(select [person] from [application] where [id] =@identity))Exports can be used to define which event details you would like to share with counselors in the portal view.
The standard Slate.org Application portal comes with pre-defined content blocks. You may also edit the views to display any additional data points added to the queries, remove items, or reformat in a different visual layout.
Application Details View
The Application Details view includes several static content blocks, containing images, merge fields, Liquid markup, and snippets. The table widget pulls in data from the linked Events query. Review the article on portal table view widgets before editing the existing widget or adding a new widget.
Tip
Think about leveraging dynamic content blocks to display information, such as staff assignments or advisors. This allows edits to the content blocks to dynamically update the information that displays in the portal, too!
The customized content in the Slate.org Application Portal will appear below the standard Slate.org data sharing content and to the left of the checklist (if configured to share in your Application Sharing Settings).
A portal method is needed to tie the portal query and the portal view together.
Application Method
The Application method is configured as follows:
- From All Portals, select your Slate.org Application Portal from the list.
- Under Methods, select New Method.
- Configure the following in the Edit Details popup:
- Name: Application
- Type: GET
- Leave Action blank.
- View: Application
- Output Type: Default Branding
- Status: Active
It is unlikely any of these settings will need to change. Don't hesitate to reach out via the Service Desk if you believe you might need to alter one of these settings.
A list of queries display below these settings. This method is linked to the "Application Details" query. If any other queries were created, such as a query that generates a list of test scores or other items, you can:
- Click Edit Linked Queries in the top right.
- Select the additional queries.
- Click Save.
To test the Slate.org Application portal:
- From All Portals, select your Slate.org Application Portal from the list.
- On the right, select Impersonate.
- In the Record field, start typing the name of an applicant record. Select the applicant you'd like to impersonate from the list.
- Click Impersonate.
Best Practices
Avoid putting too much information in the portal. Consider what information is truly helpful to counselors, and be sure to limit the amount of Personally Identifiable Information included.
Remember that portals are dynamic! Updates to data and design elements within the portal will be immediately reflected in Slate.org.
Keep the portal status Inactive until ready to make live.