Purpose |
To define a progression rule outcome and link this to a progression rule application (at one of three levels). |
||||||
Subsystem |
Progression |
||||||
Structure |
Two Blocks |
Context Block (configured dynamically) |
|||||
|
Navigation Buttons invoke: |
Excluded Courses overlay Excluded Unit Sets overlay Excluded/Required Units overlay |
|||||
Image |
The Progression subsystem allows outcomes for failing a progression rule to be defined by an institution and linked to the rule at one of three levels in the rule application hierarchy. These are the Rule Category, Rule or Progression Rule Application levels. In all instances this form is used to define the outcome. The access form used determines the level at which the outcome is linked to a rule application. Where an outcome is defined and linked to a Rule Category, this form is accessed from PRGF1600. Where an outcome is defined and linked to a Progression Rule, this form is accessed through PRGF5100. An outcome linked to a Progression Rule Application is defined in this form accessed in context from PRGF5200. When a progression rule is applied and failed, the resulting outcome applied to the student course attempt is selected from those assigned to that failed rule. An outcome linked at the Rule Application level takes precedence over any 'parent' outcomes from the rule or rule category levels. If none exist at the 'child' application level, outcomes are inherited from the 'parent' Rule level or (where none exist at the rule level) from the Rule Category level. Any existing outcomes linked at preceding levels in the hierarchy can be viewed in the Rule Summary overlay accessed from the context form (PRGF1600, PRGF5100 or PRGF5200). These existing outcomes may be appropriate for use at the current level so consideration should be given to inheriting these instead of creating additional outcomes. The defining of an outcome in this form also determines its application. For example the number of times a rule has been failed by a student determines which outcome (of those linked to the failed rule) is applied. The concepts, underlying the rule application hierarchy and the inheritance of calendars & outcomes, are explained in the Progression Rules Overview. |
Context Block: This block is labelled and configured dynamically, based on the form from which this has been accessed. Examples: When accessed from PRGF1600, the block is labelled Progression Rule Category and displays a single field - the Rule Category. When accessed in the context of a progression rule application for a selected organisational unit (from ORGF0141 and PRGF5200), the block is labelled Organisational Unit. It displays identifying information about the Organisation Unit in the Org Unit Code field. In the Rule field, the rule category, code and text of the context rule is displayed in summary form. |
Notes/Rules:
|
Progression Rule Outcome Block: In this block an outcome is defined (and thus assigned to the context level in the rule application hierarchy). Failure : Enter a number to define the number of failures of the context rule to which this outcome applies.Repeat Failure Type : One of two values is allowed - REPEAT or CONSECRPT. CONSECRPT is used where the outcome is to apply for a 2nd or subsequent failure in consecutive progression periods. REPEAT is used where the outcome is to apply for a single or subsequent rule failure in non-consecutive progression periods.Rank : This field is used to rank alternative outcomes for the same rule failure (those with the same Failure / Repeat Failure Type values). The highest ranked outcome (where this value = 1) is the outcome either recommended or automatically applied by the system. Lower ranked outcomes are displayed and may be selected for application instead, when a student's failure to make progress is reviewed.Progression Outcome Type : Select/enter one of the institution-defined types. A selected type may require the entry of additional detail in the overflow area or on one of the overlays, because of an associated encumbrance effect type.Duration :These values are used in the system derivation of expiry dates for a progression outcome and an associated encumbrance. This is explained in a Special Topic. The Outcome Duration number entered determines the number of progression periods for which this outcome (and any associated encumbrance) is active, when applied to a student course attempt. If no value is entered, when applied the outcome is active indefinitely (and must be manually expired). An Outcome Duration Type of NORMAL or EFFECTIVE can be selected/entered. A NORMAL duration type means the expiry date of this outcome (when applied to a student course attempt) is derived based on the number of progression periods specified, irrespective of the student being enrolled. The expiry date for an EFFECTIVE duration is derived by including only those progression periods in which the student is effectively enrolled. Apply Automatically indicator: This should be selected for an outcome that is to be automatically added to a student course attempt (when the context rule is failed) as an APPROVED outcome. Outcomes without this indicator set are added to a student course attempt as recommendations (with a Decision Status of PENDING) which must be approved.The processes of approving and applying outcomes are described in Understanding Progression. |
|
Recording Restrictions :An outcome may require the recording or modification of default restrictions associated with the related encumbrance type. Attendance Type, Credit Point and Course Group restrictions are recorded in the overflow area of this form. Attendance Type or Credit Point restrictions may have default values (established as part of defining the outcome type) which enter automatically. These can be modified. The Comments text box can be used to record explanatory notes about the context progression rule outcome. |
|
Override Show Cause/Appeal indicators:These indicators allow the overriding of the default configuration settings applicable to a student, for this rule and outcome application. For example the configuration of an organisational unit may allow both a show cause and an appeal period. For this progression rule outcome, no show cause period is to be available (so the outcome can be applied as soon as it is approved). The Override Show Cause indicator on this form is set to Y. The lamp displayed indicates that, for this outcome, show cause is not allowed. When the system configuration does not allow one or either Show Cause or Appeal, the relevant indicator cannot be set. |
|
Overlay Screens :The navigation buttons to access these overlays are dynamic. The applicable button is active where the context outcome type has the appropriate Encumbrance Effect Type. In each overlay screen, multiple codes (for courses, unit sets or units) can be entered as required. Where no default course/unit set/unit codes are entered, these can be defined as the outcome is approved for application to a student course attempt (in PRGF6610). An outcome that has the effect of either exclusion from a unit set / unit or required enrolment in a unit can only be set to apply automatically where at least one unit or unit set code has been recorded. The Outcome Rule button allows access to PRGF5200, where a progression rule application can be created as part of this outcome. When this outcome is approved and applied to a student, a student course attempt progression rule application is created for those students. The rule is applied to those students in subsequent progression periods, until this outcome is expired. |
|
Last modified on 6 September, 1999