For definitions on some of the terms below or refreshers on constraint basics, please visit our Constraints article!
This article contains constraints that deal with tags or attributes on either students, courses, or programs. Stellic uses tags or attributes interchangeably. Not all institutions use tags, or may use them only on some of the data they send (for instance, students have tags (such as cohort or financial aid status) but no tags are associated with courses or programs). The constraints are listed at the top and bottom of the article, with the bottom of the article containing more details about each constraint.
Constraints at a Glance
At least [x] courses/units from a given course set [Primary Constraint]
Take [x] courses from the following attributes: [attributes] [Primary Constraint]
Do not count courses from a given set [Secondary Constraint]
Student must have [x] attributes/tags [Primary Constraint]
Take at least one program with tag [x] [Primary Constraint]
For students without [x] student tags, any of the following subrequirements can be used except [y] [Secondary Constraint]
For students without [x] student tags, only the following [y] requirements can be used [Secondary Constraint]
For students with [x] student tags, any of the following subrequirements can be used except [y] [Secondary Constraint]
For students with [x] student tags, only the following [y] subrequirements can be used [Secondary Constraint]
The requirement is waived for students with any/all of these tags: [x] [Secondary Constraint]
The requirement is waived for students who do not have any/all of these tags: [x] [Secondary Constraint]
Constraint Details
At least [x] courses/units from a given course set [Primary Constraint]
This constraint should be used when students must choose multiple options from an identified group of courses. These could be specific courses, courses with attributes, a range of courses, or courses with topics. This constraint is one of the most versatile within the requirement editor and can be applied to many requirements.
Take [x] courses from the following attributes: [attributes] [primary constraint]
This constraint could be used interchangeably with the one above, but only allows you to select courses with attributes.
Student must have [x] attributes/tags [Primary Constraint]
This constraint requires the student to have a particular attribute in order to satisfy the requirement. You can use multiple attributes in this constraint - note that adding multiple attributes to the same constraint creates an "AND" relationship, meaning that the student must have all of the attributes in order for the requirement to be satisfied.
Take at least one program with tag [x] [primary constraint]
This constraint requires students to take a program with a specific tag.
Do not count courses from a given set [Secondary Constraint]
This constraint should be used if you don’t want to count a course or a specific list of courses from a requirement. This also utilizes the course set behavior, so you can also limit courses based on ranges, attributes, or patterns.
For students with [x] student tags, only the following [y] subrequirements can be used [secondary constraint]
This constraint filters students with a specific tag into a certain subrequirement. In the example below, undergraduate students (meaning any student with an undergraduate tag attached to them) can only use the EM or ENP requirement to fulfill the breadth elective.
For students without [x] student tags, only the following [y] requirements can be used [secondary constraint]
This constraint is very similar to the one above, but instead filters students without a specific tag into a certain subrequirement.
For students with [x] student tags, any of the following subrequirements can be used except [y] [secondary constraint]
This constraint filters students with a specific tag into any subrequirement except for the one specified. In the example below, students with a "Requirements completed (ECON)" tag can take any requirement except for Macroeconomics/International to fulfill their Thesis requirement. In other words, students with this tag can only take Business or Microeconomics in order to fulfill their Thesis requirement.
For students without [x] student tags, any of the following subrequirements can be used except [y] [secondary constraint]
This constraint is very similar to the one above, but instead filters students without a specific tag into any subrequirement except for the one specified.
The requirement is waived for students with any/all of these tags: [x] [secondary constraint]
This constraint waives the requirement for students with a particular tag. An important characteristic of this constraint is that it can only be used when the requirement has subrequirements beneath it - in other words, this constraint should be used with a primary constraint of fulfill all/fulfill any.
Users can toggle between students needing any of the listed tags, or all of the listed tags.
The requirement is waived for students who do not have any/all of these tags: [x] [secondary constraint]
Similar to above, this constraint waives the requirement for students without a particular tag. An important characteristic of this constraint is that it can only be used when the requirement has subrequirements beneath it - in other words, this constraint should be used with a primary constraint of fulfill all/fulfill any.
Users can toggle between students not having any of the listed tags, or all of the listed tags.