Reference: Student Eligibility Rules Naming Conventions
Workday Student uses eligibility rules as a foundational framework throughout its product areas. Eligibility rules use data about a student or student prospect (such as, residency, program of study, student tag, last name) to determine if they're eligible for something (such as, enrollment, course completion, financial aid) within Workday. We recommend that you discuss naming convention for eligibility rules with your cross-functional teams.
Workday suggests naming conventions for these Eligibility Rules functional areas:
When naming eligibility rules, we suggest:
- Using a date reference and using+to signify that the eligibility rule is applicable on or after that the date. Example:AR_UG_Econ_Major (2021+).
- Clarifying the date if your institution makes updates to academic requirements more than once a year. Example:2021F(for Fall 2021), or2020SP(for Spring 2020).
- Consistency in naming subrules when using the Combination type of Student Eligibility Rules. Consider using numeric values where a student must complete1 AND 2. Consider using alpha values where a student has the option betweena OR b. Examples:
- Combination Rule:AR_UG_CHEM_Chemistry Core (2020)
- Sub Rule 1:AR_UG_CHEM_Chemistry 1 (2020)
- Sub Rule 2:AR_UG_CHEM_Chemistry 2 (2020)
- Combination Rule:AR_UG_COMM_Speaking (2020)
- Sub Rule 1:AR_UG_COMM_Public Speaking A (2020)
- Sub Rule 2:AR_UG_COMM Public Speaking B (2020)
Eligibility Rules for Academic Requirements
You create Academic Requirements using Student Eligibility Rules. While Academic Requirements have effective dates for versioning, Student Eligibility Rules don't. To associate an eligibility rule to a specific effective date, we suggest adding the date as part of the name.
You can use these naming conventions to configure Student Eligibility Rules for Academic Requirements:
[Area Prefix]_[Academic Requirement]_[Name of Requirement]_[Abbreviated PoS Code]_[Effective Date]
| Examples:
|
[Area Prefix]_[Level]_[ Abbreviated PoS Code]_[Name of Requirement ([Effective Date])
| Examples:
|
[Academic Requirement]_[Level]_[Abbreviated PoS Code]_[Name of Requirement ([Effective Date]+)
| Examples:
|
Eligibility Rules for Curriculum Management
You can use these naming conventions to configure Student Eligibility Rules for Curriculum Management:
[Area Prefix]_[Eligibility Rule]_[Name of Requirement]_[Effective Date]
| Examples:
|
[Area Prefix]_[Level]_[Name of Requirement ([Effective Date])
| Examples:
|
[Area Prefix]_[Level]]_[Name of Requirement ([Effective Date]+)
| Examples:
|
Eligibility Rules for Student Records
You can use these naming conventions to configure Student Eligibility Rules for Student Records:
[Area Prefix]_[Eligibility Rule]_[Name of Requirement]
| Examples:
|
[Area Prefix]_[Level]_[Name of Requirement ([Effective Date])
| Examples:
|