Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
...
PA Program Spreadsheet | CASPA Source Field (API) | Slate Source Field | ||
---|---|---|---|---|
CASPA ID | CAS/Liaison Persion ID | |||
Last Name | Last Name | |||
First Name | First Name | |||
Middle Name | Middle Name | |||
Email Address | Email Address | |||
Repeat Candidate | ||||
PA/MPH | dualdegree_choice_code | Program | ||
Vet | DOB | persInfo.otheInfo,.milStat0.militaryStatus | Military Veteran or Military Veteran Status? | |
Age at Submission | persInfo.biogInfo.birtInfo.dob | Birthdate | ||
State | Current Mailing Address State | |||
College | Primary college | |||
Major | Primary college | |||
Science GPA | ||||
PreReq GPA | ||||
Overall GPA | ||||
App Score | Scoring: Application Score Score | |||
Interview 1 Score | ||||
Interview 2 Score | ||||
Total Score | ||||
Interviewer 1 Comments | ||||
Interviewer 1 Rec | ||||
Interviewer 2 Comments | ||||
Interviewer 2 Rec | ||||
Final Decision | ||||
Date PID sent to admissions | ||||
Pt Care Hours | Patient Care Experience: Total Hours |
Outcome:
Workflow View Queries
⚙️ To limit the output of the field value to be related to Interviewer 1 or Interviewer 2:
Start with a subquery export set to output = coalese. Then add a subquery export and add an export for the value you want to export if additional conditions are met. Then add a subquery filter to calculate if the current user (username) matches the username of the value of interviewer 1. If that is true, then the subquery export will populate with whatever was set for the export.
Set up the second subquery export for the next possible value in the same way, then save.
...
⚙️ To filter the view so the only results in the Reader are for candidates where the interviewer/reader is the one currently looking at the reader (i.e., can only see your own candidates in the Reader bin view):
In the View, add a subquery filter and set aggregate = comparison. Join to current user. Join Application to Form Responses, then Form Responses to Form Submitter. Join Form Responses to Form.
Add an export for current user username and an export for form submitter username, and set those as the two values you are comparing. Add filter for the form title to limit results to only the reader review form you need.
Custom PDF for Reader Form
After too much troubleshooting issues, here is what I have learned about creating a custom PDF for the reader review form:
The merge query does not matter. There is “native” support for a custom PDF of the reader form, and the merge query doesn’t seem to work and/or be necessary.
Any fields you want merged in from the review form should be pre-pended with “form_” when added to the custom PDF in the file editor. This will cycle through the submitted values on the form if there is more than one reader form submitted and generate however many custom PDFs are needed in the reader to show all submitted form results.
You can add merge fields to the custom PDF that are not from the form for general applicant information (e.g. “name” can be used to fill in the applicant’s name, and shouldn’t be labeled as “form_name” in the file editor.
These are the standard merge fields for forms:
form_user = name of faculty/reviewer who submitted the form
form_timestamp = date of when the form was submitted
To get your custom field labels you just need to add “form_” to the beginning of the label you used for the export key in the form builder. Example:
In the form:
...
In the file editor:
In the reader:
...