In order to reduce redundant typing of dates in text fields, several fields on the Application Configuration allow for the value date-fields from the Application Configuration to be substituted into the text dynamically.
Supported Text Fields
The following fields are supported. We can add more easily.
- Login Text: PreOpen
- Login Text: Open
- Login Text: Closed
- appOverview: Program Text
- Recommendation Instructions
- Transcript Instructions
Note: these fields are cached, and in you'll need to Reset Cached Data to see changes.
Supported Date Fields
Date/Time Fields
Currently only the primary date fields are supported:
- Date Open: Date/Time on/at which the application opens for the current cycle (the application is open when the current time is equal to or later than the DateOpen)
- Date Close: Date/Time on/at which the application closes for the current cycle (the application is closed when the current time is equal to or later than the DateClose)
- Date Close Display: Date/Time on/at which the application advertises that it closes for the current cycle (so that there is a grace period for last-minute applicants, if desired)
- Final Accept Date: Date/Time on/at which the applicants can no longer accept an offer of admissions
Specificity
Each time/time field is accompanied by a "specificity" field. The determines the default specificity and preposition that a substitution uses. Each Date/Time field must have both a date and a time component. However, if the exact time is unknown (early in the application cycle) or we do not want to display a specific time to the applicant, we can call out how specific to be when presenting the date/time.
- Year: only display the year (in year: "in 2017")
- Month: display both the year and the month ( in mm/yyyy: "in 03/2017")
- Day: display the full date, year, month, and day (on Month day, year: "on March 08, 2017")
- Minute: display the full date-time (at time on Monday day, year: "at 4:30pm on March 08, 2017")
Basic Syntax
In the text field, add date field you want looked up surrounded by braces inside angle-brackets.
| Field | Specificity | Resultant Text |
|---|---|---|
| {<DateOpen>} | Year | in 2017 |
| {<DateClose>} | Day | on March 08, 2017 |
| {<FinalAcceptDate>} | Minute | at 4:30pm on March 08, 2017 |
Other fields:
{<CloseDateDisplay> ... NOTE: this is not the name of the field (which is "Date Close Display") in order to clearly differentiate it from the "DateClose" field.
Extended Syntax and Options
Formatting
The default format for the date/time from the specificity field can be overridden. Following the date-field, add an underscore as a separator, then 'p' (for preposition), colon, and the single word for the altered format.
| Field | Resultant Text |
|---|---|
| {<DateOpen_f:year>} | in 2017 |
| {<DateOpen_f:shortDate>} | on 03/08/2017 |
| {<DateOpen_f:longDate>} | on March 08, 2017 |
| {<DateOpen_f:shortTimeDate>} | at 6:30pm on 03/08/2017 |
| {<DateOpen_f:shortDateTime>} | on 03/08/2017 at 6:30pm |
| {<DateOpen_f:longTimeDate>} | at 6:30pm on March 08, 2017 |
| {<DateOpen_f:longDateTime>} | on March 08, 2017 at 6:30pm |
Preposition
The default preposition from the specificity field can be overridden. Following the date-field, add an underscore as a separator, then 'p' (for preposition), colon, and the single word for the altered preposition. Any single word of text can be used as the new preposition.
| Field | Resultant Text |
|---|---|
| {<DateOpen_p:by>} | by 2017 |
| {<DateOpen_p:before>} | before 2017 |
| {<DateOpen_p:within>} | within 2017 |
Combinations
Formatting and prepositions changes must be added in that order.
| Field | Resultant Text |
|---|---|
| {<DateOpen_f:shortTimeDate_b:before>} | before 6:30pm on 03/08/2017 |