Unit Rule Validation

For VET Sector information, select the hyperlink below.

VET Information

The System is able to apply institution defined rules to validate the Enrolment of Student Unit Attempts. A rule may have one or more Rule Sets associated with it. Rule Sets further refine some rules and permit the recording of units that form part of the rule. The rules, and their Rule Sets, that may be applied to the subject Unit Attempt are:

These rules are checked when changes to a Student Unit Attempt are saved and at least one of the following has occurred:

This rule checking is carried out on-line where an Enrolment Category with unit checking specified as one of its Enrolment Steps is being used.

When on-line rule checking is not specified as an Enrolment Step (i.e. Rule Checking switched off), Student Unit Attempts where one of the above changes has occurred are checked by an off-line batch process. This batch process provides appropriate reports and, depending on the circumstances, can change the status of Unit Attempts which pass or fail a rule test. The ability to change the status of a Unit Attempt is subject to the following cutoff dates:

Cut-off dates are maintained by the System, or Enrolments, Administrator using the Maintain Enrolment Calendar Configuration form (ENRF01F0).

Previously INVALID Unit Attempts are re-checked when one of the above changes occur, either on-line where this is a current Enrolment Step or by the batch process.

Note: If a subordinate Unit Attempt is validated and can be enrolled, its status will remain INVALID if its Superior's Status is INVALID.

 

Creation/Maintenance of Unit Rules

Unit Rules are created and maintained using the form RULF2000. To create/maintain Unit Rules, RULF2000 must be entered from the Maintain Unit Version Rules form (CRSF2700). Entering from CRSF2700 allows a rule from the context Unit Version to be edited using only those rule components relevant to unit version rules.

Understanding Rules provides further information on the Rules facility.

Unit Version Rules provides information on Rule Syntax.

 

Unit Rule Batch Checking Scenarios

In Scenario 1 and 2, the activities are taking place prior to the Enrolled and Invalid Rule Cutoff dates.

Scenario  Outcome
1 A number of students are enrolled in units during an Enrolment session for which the Enrolment Category procedure detail does not include the Enrolment Step CHKVALIDITY (check that a Student Unit Attempt satisfies Unit Rules). Some of these Student Unit Attempts breach pre-requisite, co-requisite and incompatible rules. All units were successfully enrolled at time of data entry including those which breached Unit Rules. The Bulk Rule checking process ran at a time specified in Job Scheduler. It identified the Unit Attempts which were in breach of Unit Rules and so converted the status of applicable units from ENROLLED to INVALID.
2

Some Student Unit Attempts which have been through the bulk rule checking process are changed by:

  • Waiving the rules for an INVALID Unit Attempt.
  • Granting advanced standing to students with INVALID Unit Attempts, for units which are pre-requisites or co-requisites of those Unit Attempts.
  • Discontinuing pre-requisites or co-requisites of Unit Attempts with status ENROLLED.
  • Revoking previously granted advanced standing in a unit which is a pre-requisite of an ENROLLED Unit Attempt.
  • The Unit Attempts are immediately changed to ENROLLED.
  • The Unit Attempts change from INVALID to ENROLLED where the rules applying to each Unit Attempt have now been satisfied.
  • The Unit Attempts change from ENROLLED to INVALID.
  • The status of the Unit Attempt changes from ENROLLED to INVALID.
3 The events described in scenarios 1 and 2 are repeated, but after the Enrolled and Invalid Rule Cutoff dates. The System is unable to change the status of Unit Attempts because this is prevented after the cutoff dates. The Bulk Unit Rules Check Exception Report (ENRR08C0) is automatically produced and provides details of units identified by the rule check process whose statuses are unable to be changed. In each case a message explains why the attempted transaction is an exception.

 

Last modified on 08 December, 2004