Overview

This article covers how to create requirements for Courses that students need to fulfil, in order to be eligible to enroll to it.

For example:

• The student needs to take and pass Course A first, before they can enroll to Course B.
  
  
• The student needs to complete Course A first (grades do not matter), or at least enroll to Course A first, before they can enroll to Course B.
  
  
• Students need to achieve at least 160 credits before they can take their internship.

Use case

RIO University is offering a Program, which is the 'Bachelor of Business Information System'.

Some of the Courses have requirements that must be met first, before students can enroll to them.

For example, the Course BUS104 has a pre-requisite that must be met, in order to be available for students to enroll to it.

• The student will need to complete and pass the Course MGT310 first.

If the student has not completed and passed MGT310 yet, he/she will find that BUS104 will be unavailable for enrollment.

The 'Enroll' button will be missing, and the status will show 'Enrollment Requirements not met'.

Only when this pre-requisite is met, will the Course BUS104 be available for enrollment.

So, if the student has completed and passed MGT310, the Course Connection for MGT310 should have its:

• 'Enrollment Status' = Completed, and,
• 'Grade Result' = Passed.

This will then meet the requirement for BUS104, thus making it available for enrollment.

See the setup below for a guide on how to create these requirements, as well as the logic (automation triggers) behind them.

Setup

The Course BUS104 will need to have its requirements defined.

The following needs to be set up by the university:

1. The first thing to do is to set up a template.
   
   Create a Course for BUS104.
   This is the Course that has requirement(s) that must be met, in order to be available for students to enroll to.
   
   
   
2. Then, create a Course Requirement for that Course BUS104.
   
   
   
   Set the Requirement Type as 'Pre-Requisite'.
   
   Enter the Course for the Requirement Type to apply to, which in this case, is MGT310.
   
   
   Thus, the system will check if a student has completed and passed MGT310, before they can enroll to BUS104.
   
   - Student's Course Connection for MGT310 must have its 'Enrollment Status' = Completed, and 'Grade Result' = Pass.
   
   
   
   Also, make sure to set a unique Requirement ID, i.e. 'A'.
   
   
   
3. Then, head back to the parent Course BUS104 and populate the 'Requirement Logic' field with the same Requirement ID.
   
   This is to ensure that the Course can identify the Course Requirement made for it.
   
   
   
   (Note: The 'Requirement Logic' field also supports functions such as 'AND', 'OR', 'NOT', if there are multiple Course Requirements for a single Course.)
   
   
   At this stage, the Course and its requirements have been set up. But this is only a template.
   
   A Plan Requirement (Course) needs to be created.
   The Plan Requirement (Course) also needs to have the requirements copied over.
   
   
   
4. Create a Plan Requirement (Course) for BUS104.
   
   The Plan Requirement (Course) will inherit values from the Course, such as the 'Requirement Logic' field.
   
   
   
   This is to help the Plan Requirement (Course) identify its Program Course Requirement.
   
   The Program Course Requirement is automatically created, which inherits the values from the Course Requirement (created in step #2).
   
   In other words, the requirements for the Course, are carried over to the Plan Requirement (Course) as a Program Course Requirement.
   
   
   
   
   • The 'PREQ_CourseRequirements_TDTM' trigger creates Program Course Requirements from the related Course's Course Requirements.
     
     
   • This only occurs the first time the Plan Requirement (Course) is created.
     Subsequent edits to the Course Requirement will not be reflected in the Program Course Requirement.
     
     
     
5. If the student has met the requirements (passed MGT310), he/she will be able to enroll to this Course BUS104, via the enrollment wizard.
   
   A Course Connection will be automatically created, which is copied over from the Plan Requirement (Course).
   
   The 'Requirement Met' checkbox will be checked, since the student has passed MGT310. Thus, the 'Enrollment Status' will be 'Enrolled', since the student can enroll to BUS104. 
   
   
   
   The Course Connection will inherit the 'Requirement Logic' from the Plan Requirement (Course).
   
   The Course Connection Requirement is copied from the Program Course Requirement, thus providing the Course Connection with its requirements for the system to verify.
   
   
   
   
   • The 'CSENRQ_CSENRequirement_TDTM' trigger will create a Course Connection Requirement from the related Plan Requirement'sProgram Course Requirement.
     
     
   • The Course Connection Requirement only inherits the values from the Program Course Requirement the first time the Course Connection is created.
     Subsequent edits to the Program Course Requirement will not be reflected in the Course Connection Requirement.
     
     
   • The 'PECRS_RequirementMet_TDTM' trigger will then check if the student has met the requirements (whether the student has completed and passed MGT310).
     Once this is satisfied, the 'Requirement Met' checkbox will be checked.

Differences in where Electives and Mandatory Courses get their requirements from

From the student enrollment point of view (before enrolling to any Course):

The requirements for Electives will come from the Program Course Requirement.

This is because an elective Plan Requirement (Course) will not generate a Course Connection (and thus Course Connection Requirement) if the student has not enrolled to it yet, as seen in the enrollment wizard view above.

On the other hand, the requirements for Mandatory Courses will come from the Course Connection Requirement.

This is because a required Plan Requirement (Course) will generate a Course Connection the moment the student enrolls to the Program itself, even if the student has not enrolled to that Course yet.

Other use cases

Can only choose one out of two Courses

Students can choose either to enroll to BUS104, or enroll to MGT310.

Once the students have enrolled to one of those Courses, they cannot enroll to the other Course.

Just as the first use case above, the university will need to set up the Course Requirement for the Course BUS104.

The Requirement Type will be 'Pre-Requisite' as well.

However, the Requirement Logic in the Course record should be NOT(A).

This will ensure that if the student has already enrolled to MGT310, then, BUS104 will not be available for enrollment.

Need to complete or at least enroll to a Course first

The Course BUS104 has a requirement that must be met, in order to be available for students to enroll to it.

• The student needs to have completed and passed the Course MGT310 first,
  OR,
• The student needs to at least enroll to MGT310 first.

Just as the first use case, the university will need to set up the Course Requirement for the Course BUS104.

But for this scenario, the Requirement Type will be 'Pre-Requisite (Enrolled or Completed)'.

This will check if the student has completed and passed MGT310.

• Student's Course Connection for MGT310 must have its "Enrollment Status" field as either:
  • Completed (along with "Grade Result" = Pass), or,
  • Enrolled.
    
    
• The 'PECRS_RequirementMet_TDTM' trigger will then check the 'Requirement Met' checkbox on the Course Connection for BUS104.
  
  
• Note: If a Course Connection Requirement is updated or deleted, the 'PECS_RequirementLogic_TDTM' trigger will determine if the 'Requirement Met' field on the related Course Connection needs to be updated accordingly.

Only when the requirement is met, will BUS104 be available for enrollment.

Need to have a minimum amount of credit points

Students are required to complete an internship (INT401), which is part of their Program (the 'Bachelor of Business Information System').

However, INT401 can only be taken once a student has earned at least 160 credit points from other Courses in the Program.

Just as the first use case, the university will need to set up the Course Requirement for the Course BUS104.

But for this scenario, the Requirement Type will be 'Credit Points', and the 'Credit Points' field is populated with 160.

This will check if the student has achieved at least 160 credit for his/her Program.

• Student's Program Enrollment must have at least 160 credits in the 'Credits Earned' field.
  
  
• The 'PECRS_RequirementMet_TDTM' trigger will find all "Credit Point" Course Connection Requirements for that Program Enrollment and update its 'Requirement Met' checkbox as needed.
  
  
• Note: If a Course Connection Requirement is updated or deleted, the 'PECS_RequirementLogic_TDTM' trigger will determine if the 'Requirement Met' field on the related Course Connection needs to be updated accordingly.

Only when the requirement is met, will BUS104 be available for enrollment.