Program Plan
Table of Contents
Program Plan
Note: This is a part of master data objects that will be created and maintained by admin users for an academic program.
Program Plan is an EDA object that is used for versioning for a Program. It also acts as a program structure template for admin to define the related Courses and pathways available. A Program Plan consists of the following child objects:
-
Plan Requirement (Record Type = Group).
Plan Requirement (Record Type = Course).
-
Pathway Unit.
-
-
Discipline Requirement (Record Type = Group).
Discipline Requirement (Record Type = Course).
-
Note: As of v3.10, the RIO Ed - Program Structure Overview component will now display the Program Structure with all the Plan Requirement Groups and Courses under it.
Also take note that Plan Requirement is an EDA object. We have extended it with record types (Group and Course) and additional fields to track information required in RIO Education. Program Pathway, Pathway Unit, Program Discipline, and Discipline Requirement are RIO Education objects.
Application and Deposit Fee Generation
In v3.5, the checkboxes "Auto Generate Application Student Fee" and "Auto Generate Deposit Student Fee" have been added to Program Plan.
Both checkboxes will automatically create Application and Deposit Student Fees in a Program Enrollment after the Program Application (or EDA Application) has been approved.
As of v3.9, those Application and Deposit Student Fees in the Program Enrollment can take the amount of the child Application and Deposit Fees, if the child fees are labelled.
For example:
-
Application and Deposit Fees are created, and their child fees are labelled 'Online'.
- The Application and Deposit Fees are linked to a Program Plan, and the checkboxes 'Auto Generate Application/Deposit Student Fee' are checked.
- That Program Plan is linked to a Program Application (also works the same for EDA Application object), which has the same label 'Online'.
- The Program Application is approved, and the resulting Program Enrollment's student fees will use the amount of the child fees from step 1.
Is Primary Flag
Since a Program can have multiple active Program Plans, the “Is Primary” field is important to identify the default Program Plan that will be used by automations in EDA and RIO Education.
Important fields
| Field | Description |
| Next Starting Term | Default starting Term. This will be inherited by Program Application if none is defined. |
| Fee Method |
Default fee method. This will be inherited by Program Application if none is defined. |
| Pay Upfront |
Default pay upfront. This will be inherited by Program Application if none is defined. |
| Fee |
Default fee (Fee Unit = Program) for a full program. This will be used when the “Fee Method” = Program or Fixed Term is set in Program Enrollment. |
| Use Default Fee |
For “Fee Method” = Program only. A flag to indicate that a Program Enrollment should use the default fee defined in Program Plan. Otherwise, the child fee that matches the fee label defined in Program Application will be used. |
| Current Fee (Domestic & International) |
For display purpose only. The value is rolled up from a child fee schedule record if the child fee schedule is marked as “Current” = checked. |
Non Tuition Fee |
(v3.3) The obsolete "Current Non Tuition Fee Domestic" and "Current Non Tuition Fee International" formula fields on the Program Plan object have been updated to refer to the Non Tuition Fee lookup field on Program Plan. You may need to update the Program Plan record with "Non Tuition Fee" if you are using the formula fields. |
| Application Fee | Application Fee to be charged when the student submits the application. |
| Deposit Fee | Deposit Fee to be charged when the student's application is approved. |
| Auto Generate Application Student Fee |
(v3.5) Tick this to create student application student fee and fee line for new Program Enrollment. |
| Auto Generate Deposit Student Fee |
(v3.5) Tick this to create deposit student fee and fee line for new Program Enrollment. |
| Dual Qualification |
Indicates a double qualification Program Plan. It should have Primary Program and Secondary Program specified. |
| Auto Credit Transfer |
Indicates any Program Enrollments for the Program Plan will contribute or receive any credit transfers. |
| Total Required Credits |
Specifies the total number of credits a student must complete to satisfy this Program Plan. |
| EFTSL (Credit Points) |
Used to override educational institution/university department/academic program EFTSL. Set this if you would like to track different EFTSL for different Program Plan. See also: EFTSL - Credit Points |
| Default Program Pathway |
Lookup to a child Program Pathway record. This will be the Program Pathway applied to enrolled Program Enrollments if none is defined. |
| Non Tuition Fee |
The non tuition fee for the Program Plan, applied if the fee method = Program or Fixed Term. As of v3.5, the Non-Tuition Fee on Program Plan can now be used in "Term - Course" fee method, creating a non-tuition fee each Term after the student enrolls into a Course. |
| Support Pre-Acceptance Enrollment |
Allows Program Applications to create Program Enrollments for this Program Plan before the application is completely finalized. For details on setting this up, head here. |
Dual Qualification
(See also: How does RIO Support Dual Qualifications)
User is able to indicate whether a Program Plan has double qualifications by ticking the checkbox 'Dual Qualification' and filling in both Primary Program and Secondary Program.
Plan Requirements are populated based on the Plan Requirements in Primary and Secondary Program.
-
Courses from Primary Program will be marked with:
- Reporting Program = Primary.
- Reporting Program = Primary.
- Courses from Secondary Program will be marked with:
- Reporting Program = Secondary.
- Reporting Program = Secondary.
- Courses in both Primary and Secondary Program will be marked with:
- Reporting Program = Both, and lookup to Primary Group.
- Reporting Program = Both, and lookup to Primary Group.
Developer note: For this "Dual Qualification" feature to work, ensure that the trigger handler, rio_ed.PECC_DualQualification_TDTM is activated.