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 limiting courses and requirements based on their grades or test scores. The constraints are listed at the top and bottom of the article, with the bottom of the article containing more details about each constraint.

This secondary constraint is most often used for Pass or CR grades, which most institutions do not permit to count freely throughout audits but do permit in specific requirements. (Such settings are determined via the institution's Configuration settings.) For example, a major audit may include core courses, for which only letter grades are permitted, but then an electives section for which students can take courses with a P grade. Using this "Non-letter grade passed courses can satisfy this requirement" constraint would allow a P to count only within that section of the audit.

Additional context: This constraint was formerly and is equivalent in behavior to: "Ungraded passed courses can satisfy this requirement." While the "ungraded" language is no longer included in our requirement editor, you may still see the constraint functioning in audits that were built in prior years.

This secondary constraint is the same as the constraint above, but limits ungraded passed courses to count only for specific terms. A common use for this constraint were the extenuating grading circumstances that happened for many universities in Spring 2020 with COVID 19 changes.

This secondary constraint will enforce that a requirement must have a minimum grade. Stellic will use the grade order set in the configuration in order to determine which grades fall above or below the grade specified.

Note that only passing grades can count toward requirements by default.

This secondary constraint allows you to dictate how many courses above or below a certain grade, or how many transfer courses, can be allowed to count for the requirement. To make sure that no courses of a certain grade or no transfer courses would fill the requirement, set the count to ‘0’.

You can select the scope of the "defined grades" to be:

or

This secondary constraint checks for if the grade of a course is marked as a transfer grade within the backend of the system (this would have been established during initial Stellic set up - contact your campus Stellic admin for more information), and then limits the number of units of courses with transfer grades. There can be multiple grades that fall within this constraint (for example, if your institution used all of these for various types of transfer credit, they would all fall under this constraint: T, TA, TR, etc.)

This secondary constraint allows you to specify a grade criteria for specific courses (or courses with attributes, course range, or a course pattern) that are exceptional to the rules. In the example below, C- is the standard grade for the courses in the program, but we want computer science courses to have a higher grade standard than the other courses.

This primary constraint allows you to specify that a test score can count toward a requirement. This constraint can only be used if you are sending test scores within your institution's data - if you are sending test score data but do not see this constraint, please reach out to your Stellic representative.

The constraint also has a number of variants that can be selected within the first dropdown - less than or equal to, less than, exactly, or greater than or equal to.

This primary constraint is similar to the one above, but with the difference that this constraint is for tests that are pass/fail only - so they do not have a score. This constraint can only be used if you are sending test scores within your institution's data - if you are sending test score data but do not see this constraint, please reach out to your Stellic representative.