Customizing Standard Fields & Prompts
  • 17 Jun 2024
  • 7 minute read
  • Dark
    Light
  • PDF

Customizing Standard Fields & Prompts

  • Dark
    Light
  • PDF

Article summary

Slate delivers a multitude of customizable standard fields and prompts. This article indicates each field and the steps required to customize it.

đź“– Related articles

đź”” Important!

Only create fields and prompts using the exact Field IDs and Prompt Keys as instructed below. Do not create custom fields for Slate standard fields.

Configuring prompts for standard fields

To configure prompts:

  1. Select Database on the top navigation bar

  2. Select Prompts.

Consult the sections in this article for customization options for each standard field.

Person Information

Biographical

Language

🔑 Prompt key: language

  • A prompt list for language exists in Slate, which can then be used system-wide with any number of custom fields.

  • If no language prompt key exists, download Code Table - Languages from the Standard Query Library and batch import as prompts.

  • The prompt list can be modified in the Prompts tool; however, the Index values for all language prompts must be unique.


Sex

🔑 Prompt key: sex

  • Sex uses a special prompt key of sex.

  • To modify the preexisting options, all options including the preexisting default values (Male and Female) must be inserted.

  • Each prompt must include a single letter index value.

📦 Preexisting options:

  • Value: Male; Index Value: M

  • Value: Female; Index Value: F

⚙️ Custom example:

  • Value: Non-binary; Index Value: B

Pre-existing options: Male and Female must include the Index Values exactly as shown in the preceding table. The index value is limited to 1 character.


Prefix

🔑 Prompt key: prefix

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of prefix.


Suffix

🔑 Prompt key: suffix

  • A standard list of prompt values is provided.

  • Additional prompts can be added to the list using a key of suffix.


Address

Address Type

🔑 Prompt key: address_type

  • Address Type uses a special prompt key of address_type.

  • To modify the preexisting options, all options, including the preexisting default values (Mailing Address, Permanent Address) must be inserted.

  • Each prompt must include an index value.

  • Do not create index values that are longer than 16 characters.

📦 Preexisting options:

  • Value: Mailing Address; Index Value: mailing

  • Value: Permanent Address; Index Value: permanent

⚙️ Custom example:

  • Value: Location Address; Index Value: location

Preexisting options of Mailing Address and Permanent Address must include the Index Values exactly as shown above.


Contact

Device Type

🔑 Prompt key: device_type

  • Device Type leverages a special prompt key of device_type.

  • To modify the preexisting options, all options including the preexisting default values (Primary Phone, Mobile Phone, Evening Phone, Email Address) must be inserted.

  • Each prompt must include an index value.

  • Each Device must have a unique index value.

📦 Preexisting options:

  • Value: Primary Phone; Index Value: phone

  • Value: Mobile Phone; Index Value: mobile

  • Value: Evening Phone; Index Value: business

  • Value:  Email Address; Index Value: email

⚙️ Custom examples:

  • Value: Twitter; Index Value: twitter_id

  • Value: Skype; Index Value: skype_id

  • Value: Instagram; Index Value: instagram_id

  • Value:  Videophone; Index Value: videophone_id

  • Preexisting options of Primary Phone, Mobile Phone, Evening, and Email Address Phone must include the Index Values exactly as shown above.

  • Custom Email Address device types:

    • The category must be set to email to include the email address in the recipient select list for ad-hoc emails.

    • If social media accounts are created as custom device types, the following should not be used as index values:

      • facebook

      • google

      • linkedin


Schools

Level of Study

🔑 Prompt key: school_type

  • A standard list of prompt values is provided. Existing values can be modified, and additional types may be added to the list of options.

  • This must include an index value to be stored, such as for “High School,” include an index value of H, for “Graduate,” use an index value of G, and for “Undergraduate,” use an index value of U.


Degree

🔑 Prompt key: degree

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of degree.


Major or Minor

🔑 Prompt key: major

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of major.


Field of Study

🔑 Prompt key: field

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of field.

  • This field can only be accessed when a prompt list exists.


Honors

🔑 Prompt key: honors

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of honors.

  • This field can only be accessed when a prompt list exists.


School Courses

Course information stored on the student record on the Profile tab is commonly used to track classes taken before admission to a college.

If you are sharing an instance between Admission and Student Success, you might want to use entities to capture current college-level classes rather than using the Courses table.

School courses are related to a specific school on the person record, so data for each course must have a school saved to the person record on which to save it.

Course Name

🔑 Prompt key: course_name

  • By default, “Course Name” is a text box field.

  • Adding prompts with Key of course_name automatically changes this text box list to a select list.


Level

🔑 Prompt key: course_level

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of course_level.

  • This field can only be accessed when a prompt list exists.


Type

🔑 Prompt key: course_type

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of course_type.

  • This field can only be accessed when a prompt list exists.


Grade

🔑 Prompt key: course_grade

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of course_grade.

  • Until this prompt list is established, grade only functions as a text field.


Grade Level

🔑 Prompt key: course_grade_level

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of course_grade_level.

  • This field can only be accessed when a prompt list exists.


Term

🔑 Prompt key: course_term

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of course_term.

  • This field can only be accessed when a prompt list exists.


Jobs

Job history information stored on the student record within the Profile tab is commonly used to track employment occurring before admission to a college.

If you are sharing an instance between Admission and Student Success, you may wish to use entities to capture enrolled student job history.

Function

🔑 Prompt key: function

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of “function.”

  • This field can only be accessed when a prompt list exists.


Industry

🔑 Prompt key: industry

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of industry.

  • This field can only be accessed when a prompt list exists.


Sector

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of sector.

  • This field can only be accessed when a prompt list exists.


Recommendations

Reference Type

🔑 Prompt key: reference_type

  • A standard list of prompt values is provided.

  • Additional reference types can be added to the list of options, and the entire list will be overwritten by adding prompts. This must include an index value to be stored.

    • For example, for “Counselor Recommendation,” include an index value of C, for “Teacher Recommendation” include an index value of T, for “Clergy Recommendation” include an index value of O.

Do not use R as an index value. R is a standard reserved index value.


Relationships

Relationship Type

🔑 Prompt key: relationship_type

  • Enables an applicant to include a type when providing relationship details.

  • The prompt requires that a Category be included for proper relationship ranking.

  • Categories:

    • Sibling

    • Parent

    • Legal Guardian

    • Step-Parent


Relationship Education Level

🔑 Prompt key: relationship_education_level

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of relationship_education_level.


Relationship Prospective Entry Term

🔑 Prompt key: term

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of term.

  • This list will likely be shared across multiple fields/scopes that revolve around Entry Term.


Interests

Interest information stored on the student record’s Profile tab is commonly used to track interests before admission to a college.

If you are sharing an instance between Admission and Student Success, you might want to use entities to capture enrolled student interests.

Interest Type

🔑 Prompt key: activity_type

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of activity_type.


Interest Name

🔑 Prompt key: activity_name

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of activity_name.


Sports

Sport information stored on the student record within the Profile tab is commonly used to track sports before admission to a college.

If you are sharing an instance between Admissions and Student Success, you might want to use entities to capture enrolled student sports.

Sport

🔑 Prompt key: sport

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of sport.


Sport Rating

🔑 Prompt key: sport_rating

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of sport_rating.


Projects

Project Status

🔑 Prompt key: project_status

  • A standard list of prompt values is not provided.

  • Add a prompt list to define those values using a key of project_status.

  • A “Complete” prompt must exist and requires that a category be included for Projects and Tasks to be marked as “Complete.”

  • Note: This field is required for the use of Projects.

Prompts and corresponding category examples include:

Prompt

Category

Complete

Complete

In Progress

In Progress

Not Started

Not Started


Was this article helpful?