Some programs have requirements that are not courses. Non-course requirements might include examples like these:
· Tests
· Life experiences
· Chapel requirements
· Service learning
· Writing across the curriculum
Rules Based Update helps you handle non-course program requirements.
To use Rules Based Update with non-course requirements, there is some setup to do.
· Create a non-course
advising requirement type.
· Create advising requirements of the non-course type.
· Place the advising requirement on an institutional requirement tree.
When the Compute Student Progress process runs, it evaluates the non-course requirement. If the criteria are satisfied, the requirement is marked as met for the student.
Use Rules Based Update (RBU) to create a non-course institutional requirement