Edit a ruleset

Update ruleset metadata and versions — grading schema, attempt limits, weights, credit points, deadlines, custom fields, and connections to programs, cohorts, and users.

Edit academic rulesets at Settings → OrgHub → Academic Rulesets. Select a ruleset to open its version list, then open a version to edit its configuration.

Editing is how you keep examination policy current: validity periods, rating schemas, attempt caps, grade weights, credit requirements, deadlines, and the connections that decide who is governed by which version. Treat active versions carefully — students may already be consuming attempt budgets under the previous numbers.

For how attempt limits behave across sittings — including permanent failure and the interaction with exam-type workflows — see How exam attempts work.

Why it matters

Academic regulations change on a calendar: new validity years, adjusted resit rights, revised credit thresholds, different rounding rules, or tighter withdrawal windows. If you overwrite a live version without a plan, attempt history and published grades can disagree with the policy students believed they were under. Fuxam’s ruleset → version → connections structure exists so you can adjust metadata, create successor versions, and re-point assignments with an audit-friendly trail.

How it fits

Editing sits between creating a ruleset and verifying behavior in the Exam Center. Changes on a version apply to students whose effective ruleset resolves to that version — see Assignment priority.

Edit ruleset metadata

From the rulesets list, open the action menu on a ruleset to:

Edit the ruleset name, description, or code
Create a new version when policy changes for a new academic year
Delete the ruleset (blocked when assignments exist — review impact first)

Edit a version

Open a version page to configure:

Basic information

Version name, description, and validity period (Valid from / Valid to)
Validity dates determine whether the version is currently active

Grading configuration

Grading schema — rating scale for graded exams (see Configure grading scale)
Maximum passed attempts and maximum failed attempts — module-level limits (see Configure attempt limits and How exam attempts work)
Module weight and final weight — must sum to 100% (see Grade weighting)
Required credit points — see Credit-point requirements
Exam appointment selection deadline — days before an alternative date becomes locked
Withdrawal deadline — days before exam withdrawal closes
Rounding behavior — generic decimal rounding or rating-schema-based rounding

Deep deadline guidance: Appointment and withdrawal deadlines.

Custom fields

Add institution-specific key-value fields (for example, attendance thresholds) under Custom Fields.

Connections

Assign or remove links to study programs, cohorts, and users on the version page. Replacing an existing assignment on an entity overwrites the previous ruleset link.

How to edit a ruleset version

Go to Settings → OrgHub → Academic Rulesets and select the ruleset.

Open the version you want to edit.

Update fields in Basic information, Grading configuration, or Custom fields.

Save the version. Changes apply to students whose effective ruleset resolves to this version.

Review Connections to confirm the version is assigned to the intended programs, cohorts, or users.

Key settings reference

Area	Fields that matter for assessment policy
Validity	Valid from / Valid to — whether the version is active
Attempts	Maximum passed / failed attempts — caps module attempt economy
Scale	Grading schema — which marks examiners may enter
Weights	Module weight and final weight — must total 100%
Progression	Required credit points
Deadlines	Exam appointment selection deadline; withdrawal deadline
Rounding	Generic decimal vs rating-schema-based rounding
Custom Fields	Institution-specific policy values

Worked examples

Example — lower failed attempts for a new PO year

The 2025 regulation allows only two failures before final failure. Instead of editing the 2024 version (where some students already used attempt 2 of 3):

Create a new version with validity from the new academic year.
Set Maximum failed attempts = 2 (range 0–10; empty would reset to 3).
Keep weights at 100% and set the withdrawal deadline to match the statute.
Re-point Connections for the affected study program or new cohort to the new version.
Leave the 2024 version assigned to cohorts still under the old regulation.

Example — mid-term limit change gone wrong

Staff change max failed from 3 to 2 on an active version mid-semester. Students who already failed twice may suddenly be treated as permanently failed, and attempt tabs shrink for everyone on that effective ruleset. Prefer a new version with a clear validity start date.

Example — tighten withdrawal window for a new intake

A regulation shortens Rücktritt from seven days to three days before the exam. Create a new version, set Withdrawal deadline to 3, assign it to the new cohort only, and leave older cohorts on the previous version so mid-program students keep the window they enrolled under. See Appointment and withdrawal deadlines.

Edge case — weights and attempts edited together

Changing attempt limits and module/final weights in one save is allowed, but verify both stories independently: weights must still sum to 100%, and attempt numbers must still match the exam-type workflow (auto reattempt vs reassessment period).

Best practices

Separate generations with versions — keep last year’s limits intact for students still governed by that validity window.
Keep weights at 100% — incomplete weight pairs undermine consistent final grade calculation. See Grade weighting.
Review connections after every save — replacing an assignment overwrites the previous ruleset link for that entity.
Align schema with exam types — ruleset grading schema and exam-type rating mode should tell the same story to examiners.
Use custom fields sparingly — reserve them for policy values your institution truly needs alongside core grading configuration.
After changing attempt fields — spot-check My Exams attempt usage for one student at each assignment level.
Document credit thresholds — set Required credit points from the progression clause, not from informal practice. See Credit-point requirements.

Common pitfalls

Pitfall	Impact	Mitigation
Mid-term limit changes on an active version	Attempt tabs and permanent-failure decisions shift under students	New version + validity dates
Deleting a ruleset with assignments	Delete is blocked — work is wasted if you did not check connections first	Remove or reassign connections, then delete
Forgetting cohort overrides	Program edit does not affect students with higher-priority cohort or user assignments	Check assignment priority
Changing limits without checking workflow	Reassessment period still blocks attempt 3+	Align exam types
Weights that do not sum to 100%	Inconsistent combined grades	Fix grade weighting before publishing

FAQ

Who is affected when I save a version?

Students whose effective ruleset resolves to this version. Resolution uses user, then cohort, then study program assignment — see Assignment priority.

Can I delete a ruleset that is still assigned?

Delete is blocked when assignments exist. Review impact, reassign or remove connections, then delete.

Where do module vs final weights show up in daily grading?

Weights are part of ruleset grading configuration for how module and final grades combine. Day-to-day entry of marks on a sitting still happens on the exam detail page — see Grade and manage an exam and Grade weighting.

Where is the deep guide to attempt behavior?

How exam attempts work covers counters, workflows, module completion, and permanent failure.

Who can edit rulesets?

Users with administrator permission to change settings.

How exam attempts work — attempt lifecycle and permanent failure
Create a ruleset — add a new ruleset
Configure attempt limits — module attempt limit details
Assignment priority — which assignment wins for each student
Configure grading scale — rating schemas used in grading configuration
Grade weighting — module and final weights in depth
Appointment and withdrawal deadlines — deadline fields on the version