US English (US)
ES Spanish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Log in
English (US)
US English (US)
ES Spanish
  • Home
  • Help & Support
  • Support
  • Deep Dive
  • RIO Education Modules
  • Module - Enrollment
  • V3 Data Dictionary: Enrollment

Course Connection Requirement

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • RIO Certification
    RIO Certification Program RIO Academy RIO Challenge RIO Recipe Training
  • Releases
    Release Notes
  • Help & Support
    Install RIO Education RIO Insights RIO Recipe Support
  • About Us
    Who is RIO Education? Start Your RIO Journey Housekeeping
  • Experience RIO in action
+ More

Table of Contents

Course Connection Requirement Requirement Types Important fields

Course Connection Requirement


Note: For use cases, see here: Pre-requisites (and other requirements) for Courses‍.


The Course Connection Requirement object is located under the Course Connection.

It outlines the requirements (pre-requisites, co-requisites, etc.) for said Course Connection.


For example, this Course Connection for 'BUS104' has a requirement.


Whereby the Course 'MGT310' is a pre-requisite that needs to be either enrolled or completed, in order for the Course Connection to be available for students to enroll.

  • The 'Requirement Met' checkbox will be automatically checked when this happens.


If a mandatory Plan Requirement (Course) has its Program Course Requirements defined, creating a Program Enrollment will automatically create a Course Connection and its Course Connection Requirements.

The Course Connection Requirement will inherit the values from the Program Course Requirement.

  • This will only happen the first time the Course Connection is created.
  • Subsequent edits to the Program Course Requirement will not be reflected in the Course Connection Requirement.



Requirement Types

The Requirement Types are as follows:


Pre-Requisite

  • This requires a first level Course to be completed before the student can enroll into the second level.

  • For example: To enroll into ICT21, it requires the Student to have Course Connection's “Enrollment Status” = completed and “Grade Result” = Pass in BUS108. (BUS108 is the first level and ICT211 is the second level).
    If both requirements are met, the Course Connection Requirement’s “Requirement Met” checkbox will be checked.

  • So every time when the student logs into the Community, the code will check if the ‘Requirement Met’ checkbox in Course Connection is checked before it can show available for enrollment.

  • When the first level result is released, the completion engine will update Course Connection.

  • For a use case example on setting prerequisite Courses, head here.


Pre-Requisite (Enrolled or Completed)

  • Similar to Pre-Requisite, just that the requirement is different.

  • For example, IBS220 requires the student to have (Course Connection’s “Enrollment Status” = Completed/Enrolled) in BUS101. It does not need a Pass grade result.

  • This allows students to start the enrollment for a new Term before the Courses grade for the current Term is released, so that you don't have to set the "Allow Pre-Enrollment" at Course Connection to allow the enrollment manually.


Co-Requisite

  • Used for linking two or more Courses as co-requisites.

  • For example, if Course A is to be taken, Course B must also be taken.

  • As of v3.8.3, the Co-Requisite requirements are now always set as met.

  • An additional info message will also be shown on the enrollment confirmation in the Student Enrollment Wizard, to inform students about the required Co-Requisite Courses.


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 Course Connection Requirement record is saved to update the “Requirement Met” checkbox.


Other

  • This will be for other miscellaneous requirements.

  • Unlike the other Requirement Types, the system will not be able to verify whether this 'Other' requirement has been met.
    The admin will have to manually verify it and check the 'Requirement Met' checkbox themselves.




Important fields

Field Description
Course Connection Requirement Name The name of this requirement.
Recommended to be a descriptive name, e.g. BUS104 - MGT310, so that users will know that this record is BUS104 's requirement for MGT310.
Course Connection Lookup to the parent Course Connection that this Course Connection Requirement belongs to.
Requirement ID A unique ID to identify each specific Course Connection Requirement (e.g. 'A', 'B', etc.).
The Requirement Logic field in the Course Connection will use the Requirement ID of its Course Connection Requirements (e.g. 'A' OR 'B').
Requirement Type Picklist options:
  • Pre-requisite.
  • Pre-requisite (Enrolled or Completed).
  • Co-requisite.
  • Credit Points.
  • Other.
Requirement Met Checkbox to indicate whether this Course Connection Requirement is met.
If checked, the parent Course Connection will be available for students to enroll to.
Credit Points The required amount of credit points for this requirement (if the Requirement Type is 'Credit Points').
Other Optional text field for adding description, notes, etc. (if the Requirement Type is 'Other').
Related Course The target Course that has to be completed as part of the requirement (e.g. Course 'MGT310' is the pre-requisite for this Course Connection).



Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Session
  • Program Application - Auto Program Enrollment Mapping
  • Course Offering
  • Term
RIO Education

RIO Education, a WDCi Company. This information is proprietary, confidential and protected by copyright ©2024.

CONTACT

Get in touch

  • Privacy
  • Terms of service

Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
Expand