If an R (Root) Cluster Code is used, the Group Relation Type automatically defaults to AND and the column becomes display only.
If a G (Group) Cluster Code is used, the Group Relation Type is editable.
A two-character cluster code is used to specify how each requirement will be evaluated within the Advising system. These codes are not configurable and every Advising Requirement Type must be associated with a cluster code. There are six pre-defined cluster codes with very specific purposes:
| Cluster Code | Description |
R |
A Root requirement is attached to student aims. It must also be associated with a Group Relation Type so that the relationship of the child requirements can be determined. |
G |
This is the parent of a Group of child requirements. It must also be associated with a Group Relation Type code so that the relationship of the child requirements can be determined. |
C |
A Course requirement is satisfied by the completion of course work. |
CC |
The Cumulative Credit requirement specifies that it may accumulate credit for each time that a course is successfully repeated. This is frequently used for music practice courses where a student may take the same one-credit hour course each semester for five semesters. A requirement with this Cluster Code reports five (5) credit hours for the repeated course. |
CT |
A Course Totals requirement reports an unduplicated total of all credits that a student has earned. |
O |
This Cluster Code specifies that a requirement is not automatically evaluated. It is satisfied by placing a record in the Student Advising Alterations table for the requirement with any credit or status information to be applied to the requirement. |
RBU |
Use the Rules Based Update code to set up non-course requirements. |
|
|
If an R (Root) Cluster Code is used, the Group Relation Type automatically defaults to AND and the column becomes display only. If a G (Group) Cluster Code is used, the Group Relation Type is editable. |