Implicit Behavior

The CPS Block, (which is the container for instructor creation and enrollment customizations) relies heavily on the UES enrollment module events that are being fired for injecting specialized manifests, referred to in this document as settings.

While there are many settings, the purpose this document is to discuss the implicit control the CPS Block has over the enrollment module.

Controlling Creation / Enrollment

The UES enrollment module will begin processing sections that meet the following conditions:

1. The section has an instructor that is processed to be enrolled.
2. The section itself is marked as processed.

The latter overrides the former. There are settings that control specifically when a section is eligible for creation or enrollment. The block manipulates what actually happens by handling the

• ues_section_process for creation
• ues_student_process for enrollment

Creation settings reference the semester and course the teacher owns, so it applies to all sections underneath. Of course, if there are no user defined settings, the system will return to its default behavior.

Controlling Unwanted / Removal

The UES enrollment module will begin processing sections to remove that meet the following condition:

1. The section is marked as pending at the end of the enrollment process.

To check whether or not a section is unwanted, it must be validated during the ues_section_process.

Before manifestation, this means the section is simply skipped. Otherwise, the course is unenrolled, which might fire the ues_course_severed or ues_group_emptied events.

Customizing Creation

The UES enrollment process is simple for a reason: injecting customized manifests is extremely easy.

There are three settings that involve very specialized creation of courses: Splitting, Cross-listing, and Team-Teaching.

The CPS enrollment module will fill courses based on the following condition:

1. The processed section has an idnumber, it will use that or...
2. It will create the idnumber based on an assumption.

If it finds the Moodle course, it will use it, otherwise it will create the course with defaults and fire ues_course_create. It is imperative that this is handled correctly, otherwise you may experience undesirable database writing errors.

By handling cps_course_create, the CPS setting can correctly and easily change the fullname and shortname of the course to be created.