Configure Validation Rules

Configure Validation Rules

Validation rules are your institution’s own submission checks. With nothing
configured, every proposal can be submitted. Go to Curriculum Settings
to configure them (the Validation section is the only section on this
screen).

Every rule has a severity:

• Blocking: prevents submission until the issue is fixed.
• Advisory: warns, but lets submission continue.

Start from a preset instead of entering values by hand

If a preset matching your state or accreditor is available, apply it as a
starting point:

1. Choose a preset from the Preset dropdown (for example, “North
   Carolina, NCCCS envelopes and SACSCOC thresholds”).
2. Click Apply preset. This fills in credential envelopes and
   substantive-change thresholds from the preset, but does not save them yet.
3. Review the values it filled in (see “Credential envelopes” and
   “Substantive-change thresholds” below), then click Save Rules.

A preset is a starting point, not a lock. Everything it fills in, including the
substantive-change thresholds, is yours to edit afterward.

Require fields per proposal type

1. In Required fields, each proposal type (New Course, Revise Course,
   Discontinue Course) has its own checklist of fields.
2. Check the fields that must be filled in before that type can be
   submitted.
3. Use Require all or Clear to check or uncheck every field for a
   type at once.

Enforce a credit-hour range

1. In Credit hours, turn on Check credit hours.
2. If you want, turn on Require a credit-hours value to flag proposals
   that leave it empty or non-numeric.
3. Set Minimum credit hours and/or Maximum credit hours.
4. Set the Severity.

Set credential envelopes

A credential envelope is the total credit-hour range your institution
expects for a credential type (for example, an AAS between 64 and 76 credit
hours).

1. In Credential envelopes, click Add envelope.
2. Set Credential type (must match the credential type text used
   elsewhere in your catalog), Minimum credit hours, Maximum credit
   hours, and Severity.
3. Click Remove on an envelope to delete it.

Envelopes only apply to proposals whose payload includes a credential type
and total credit-hour value.

Require a target catalog year

In Effective dating, turn on Require a target catalog year and set
its Severity to flag any proposal submitted without one.

Check proposed course codes against the catalog

In Catalog checks:

• Turn on Flag duplicate course codes on new courses to warn when a New
  Course proposal reuses a code that already exists in the catalog.
• Turn on Flag revisions of courses that don’t exist to warn when a
  Revise Course proposal names a code with no matching catalog course.

Each has its own Severity.

Substantive-change thresholds

The thresholds that drive substantive-change flagging have their own editable
fields in the Substantive-change thresholds section:

• Credit-hour change (%), New content (%), and Delivery-mode share (%):
  how large a change has to be before it’s flagged.
• Flag program closures as substantive: whether discontinuing a program always
  counts.
• Policy effective date: the date your thresholds reflect.

Set these to your own accreditor’s standards. Applying a preset (above) prefills them
as a starting point, but they stay fully editable afterward. If you never touch them,
they keep sensible built-in defaults. See
About substantive change flagging
for what each signal measures.

Save

Click Save Rules. This persists every section on the screen together;
there is no per-section save.