Set the status to ‘Inactive’ until the Slate-hosted application is ready to go live.
If all applications are being imported, the round should always be set to ‘Inactive.’
Keep your database organized by using folders. Select Other to create a new folder.
|Period||This required setting ties the Round to a specific application Period. An application Period must be created before associating it with a Round.|
This round name will be visible to applicants, so enter a descriptive name (such as “Undergraduate Application”).
|Short Name||The short name will be visible administratively only. This setting is optional, and, when present, will override the display name of the round on the application tab.|
|Order||Enter an integer value for this required setting. This order will dictate the display order of the application rounds.|
|Round Key||Enter a short-code that will identify this round type (e.g., “UG” for undergraduate and “GR” for graduate, or “ED” for early decision and “RD” for regular decision). The round key is used in application logic, automation, and communications for your application. To prevent the need to update rounds each year, omit year information so that the same round key can be used for future rounds. It is best practice to omit year information so that the same round key can be used for rounds that you create in the future.|
|Round Path||This setting can be used to override certain shared application files for a particular round. Use-cases are limited.|
This setting is for Slate-hosted applications only. If a deadline is configured here, applications in this round cannot be submitted after this time.
|Payment Grace Period (Days)||Enter the number of days after the deadline for which an application fee payment will be accepted.
For example, if the application submission deadline is January 1, but application fee payments will be accepted through January 15, enter '15' here.
This setting is applicable only to Slate-hosted applications. Selecting 'Allow multiple applications' allows an applicant to submit more than one application in this particular Round.
Note: The 'Allow Multiple' setting must also be configured at the Period level to enable multiple applications per Round.
|Locked||This setting is applicable only to Slate-hosted applications.
If multiple rounds share the same application questions and have different submission deadlines, it is best practice to configure the Rounds as Unlocked. This configuration allows a potential applicant to change to a Round with a later deadline if the original Round has passed.
This setting is typically used by graduate institutions who refer applicants to other programs.
Configuring a Round as 'Hidden' allows the applicant to not see this extra application during the review process. To display the hidden application at a later date, update the application to be in an unhidden Round.
|Protected from Rank||
Standard application rounds (applications for admission/enrollment) should always be Rankable. Applications for other items, such as summer high school programs or scholarships, should be configured as "Do not rank.'
This setting will help define which admission application has the highest-ranking based upon application priority and application creation/submission dates. See Determination of Table Ranks for additional information.
|Custom Status Portal||This setting will override the Slate-delivered Application Status Portal, if a custom portal was built using the Portal Editor.|
|Export Value||Configure up to 5 export value for the application Round. This is typically a short value or code that is used by external systems (such as an SIS) upon the consumption of application data from Slate.|