“This allows you to design the program course structure according to the accreditation model”
Once the Program and Course have been defined, we can now proceed to categorise and bundle our courses. Courses can be bundled into a program with the following setup:
- Program Group – This allows courses to be grouped under one or more categories. Example: Core, Elective or Core Selective
- Program Course – Once the groups have been defined, they can then be grouped by actual courses under each grouping
Before we start to bundle our Program and Courses, we will need to create program groups. We can group these courses as core, mandatory, elective or others, as well as defining the completion requirement of each of the groups created.
Let’s say we wish to categorise the courses into 3 common groupings:
- Core – Mandatory courses
- Core Selective – Optional accredited courses
- Elective – Optional courses that may or may not be accredited
These can be achieved by using Program Group. Program Group consists of the following fields:
Field Name Data Type Description Sample Data
Group Name Text The display name of the group Core, Mandatory, Elective, Core Selective
Group Criteria Picklist Specifies what is required for the group to be considered complete - The completion logic will be done for each student as they progress through the program
These are the behavior of different criteria:
Criteria Number Number 15
Program Master Detail The grouping's parent program Master of Leadership
These grouping will then be cloned to PE Group as part of the pathways during the program enrollment process.
Follow the steps below to create Program Groups under the selected Program
After you have defined the Program Groups, you can now group the courses into the Program
Follow the steps below to perform the configuration
Now, we can start defining the program and course completion requirements.
RIO Education supports the following requirement types:
Requirement Type Description
Pre-Requisite This requires the first level of the course to be completed, before the student can enrol into the second level. For example: To enrol into ICT21, it requires the Student to have PE Course’s Status = completed and PE Course’s Grade Result = Pass in BUS108. (BUS108 is the first level and ICT211 is the second level). If both requirement are met, the PE Course Requirement Status’s Requirement Met checkbox will be checked.
So every time when the student logs-in to the community, the code will check if the ‘Course Pre-Requisite met’ checkbox in PE Course is checked before it can show available in the community.
When the first level result is released, the completion engine will update PE Course
Co-Requisite Similar to Pre-Requisite just that the requirement is different. For example, IBS220 requires the Student have (PE Course’s Status = Completed/Enrolled) and (PE Course’s Grade Result = Pass/Failed) in BUS101. (***Currently this is not running, because the PE Course’s Grade Result is listed on the Release checkbox)
Credit Points The Credit Point is more straightforward. For example, COR109 requires the Student to have 14 Credit Points on the Program Enrollment’s Credits Earned. So the Trigger fires when the PE Course Requirement Status record is saved to update the ‘Requirement Met’ checkbox.
To setup the scenario above, we can proceed to group them under the 3 program groups we have created (assuming the courses have already been created)
In our example, there are 2 course pre-requisite requirements that need to be defined:
- The Student needs to complete Corporate Leadership 101, before he can enrol into Corporate Leadership 202
- The Student needs to complete Communication 101 OR Public Speaking 101 before he can enrol into Advance Corporate Communication
This can be done by defining the Course Requirements, let’s try to define the requirements