Maintain Progression Rule Application

Maintain Progression Rule Application - PRGF5200

Purpose	To link a general application progression rule to the system element (Course Type, Organisational Unit, Course Version, Student Course Attempt) to which it is to be applied. To create 'application-specific' rules for application to the system element.
Subsystem	Progression
Structure	Two Blocks:	Context Block (dynamically labelled) Progression Rule Application
	Navigation Buttons invoke:	Maintain Rule form Progression Rule Calendar overlay Maintain Progression Rule Outcome form Rule Summary pop-up
Image

Progression rules are applied to a student through his/her 'membership' of the following groups within the institution:

as a member of the student body, studying a particular Course Type
as a member of the student body, studying within a particular Organisational Unit
as a member of the student body, studying a particular Course Version
as an individual student, studying a particular Student Course Attempt.

In this form, the progression rules are linked to the 'groups' (or system elements) within the institution. This linking controls the application of rules to a Student Course Attempt.

The form can only be accessed in the context of the system element within which it is to be applied. The context block is dynamic and displays block and field labels and data applicable to the element from which it was entered. The context forms which allow access to this form are:

Course Type (CRSF1110)

Organisational Unit (ORGF0141)

Course Version (CRSF1210)

Student Course Attempt (access using PRGF6600/6610 & the Student Rule button)

Student Progression Outcome (access using PRGF6600/6610 & Student Outcome Rule button)

A Progression rule may be:

an institution-defined general application progression rule that can be used in many progression applications, i.e. at one or more levels of the institution (e.g. for more than one organisational unit). This set of rules is created using forms PRGF1600 and PRGF5100.
In this form, a rule can be selected from this pre-existing set, for application to all students enrolled within the context 'group'.

an 'application-specific' rule. Where a rule is required for application to the context element, but not required for use against another system element, an 'application-specific' rule can be created, using this form.

Student Course Attempts cannot be evaluated against any progression rule until the rule is linked to the appropriate application element, using this form. The rule application must also be complete in that it has both progression calendars and outcomes assigned to it. These may be assigned at this application level or inherited from the rule or rule category.

The concepts, underlying the rule application hierarchy and the inheritance of calendars & outcomes, are explained in the Progression Rules Overview.

Context Block: The form is entered in context and displays the applicable Course Type / Organisational Unit / Course Version / Student Course Attempt / Student Progression Outcome details.	Notes/Rules: A rule cannot be applied to: an INACTIVE Organisational Unit a CLOSED Course Type a PLANNED or INACTIVE Course Version.
Progression Rule Application Block: This block is used to nominate the progression rules that are to be applied to all students who fit within the context 'group'. The nominated rules can be one of two types (as described above). In both cases, a Rule Category must be selected. To view all rules, including those which have been previously deleted, select the Include Deleted Items indicator and re-query. To select a general application rule: From the nominated Rule Category, select the Rule Code for the required rule. Enter an Attendance Type, if required. Where entered, the rule is applied only to students of the specified attendance type, within the context 'group'. General application rules cannot be modified in this form. This applies to the Rule Code, Rule Description and Rule Text fields. Editing these rules can only be done from PRGF5100 (or RULF2000 via PRGF5100). The Message field can be used to fully describe the context Rule Application - where it is intended to apply; the progression calendars and outcomes linked to it, the group of student to which it is to apply.	Rule Categories cannot be modified in this form. Rule Code and Reference Code cannot both be entered. Rule Code is relevant only to existing general application rules; Reference Code is used only for 'application-specific' rules. Attendance Type is not a required field. Attempting to use the Edit Rule button (against a general application rule) triggers an error.
To create an 'application-specific' rule: The Rule Category entered determines the available rule options that can be used in constructing the rule text. Enter a Reference code (up to 10 characters long), which can be used to identify this rule application in reports. Use the Edit Rule navigation button to access RULF2000. The rule to be applied can be constructed in that form. Enter an Attendance Type where the rule is to be applied only to students of a specified (derived) attendance type, within the context 'group'. The Message field can be used for the same purpose as for a standard rule.	A Rule Code cannot be entered for an 'application-specific' rule. A Rule Description cannot be entered for an 'application-specific' rule.
Assigning a Progression Calendar / Outcomes to A Rule Application: Progression calendars and/or outcomes can be assigned to a Progression Rule Application. This means that in this application of the progression rule, the assigned progression periods / dates (identified through the selected calendar/s) and outcomes are used. These settings override any existing calendars / outcomes assigned to the rule, at either rule or rule category level. There may be calendars or outcomes already assigned at the Rule or Rule Category level. Use the Rule Summary overlay to view these settings. Any existing calendars or outcomes can be inherited by this application.	Calendars or outcomes selected here override settings at the Progression Rule (in PRGF5100) and Progression Rule Category level (in PRGF1600). An INCOMPLETE Lamp displays when a progression rule application has neither assigned nor inherited calendars or outcomes. For more detailed explanation about the levels of application, refer to Progression Rules Overview.
To assign a calendar to the context rule application: Select or enter a progression Calendar Type, in the Progression Rule Calendar overlay. The following limits on the application of the rule, within that calendar, can be applied: Start Period - can be nominated where this rule application is to start at a point in the future. Without this limit, the application of a rule begins when the rule is linked to an application element. The List of Values displays the available Start Periods as a concatenation of the year of the calendar instance and the Alternate Code for the Progression Calendar Type e.g. 2001/P1. End Period - can be nominated (at any time after the defining of the rule) to end-date this rule application, within the given calendar type. The rule may still be active under other rule applications. The List of Values displays End Periods in the same way as Start Periods, e.g. 2002/P1 Student Start Period - enter a number to represent the progression period at which, for a given student, this rule application can begin. Applications - nominated to restrict the number of times this rule can be applied to a particular student - e.g. if 2 is entered, this rule can be applied to a student for 2 progression periods only.	A calendar type can be assigned to a rule application, with no additional values entered to further define the timing of the application. Calendars inherited from the rule or rule category may have limits that are not required for this rule application. Re-assign the calendar to the rule application, without those limits (enter new limits if required). A calendar type assigned to a Rule Application cannot be deleted once application of the rule has begun. End the link by entering an End Period value. Where calendar instances are entered in the Start / End Period fields, they must be ACTIVE instances. Any entry in the Student Start Period or Applications field must be a number >=1. A Start Period value cannot be modified once application has begun.
To assign an outcome to the context rule application: Navigate to the Maintain Progression Rule Outcome form (PRGF5214), using the Progression Outcomes button.
To view a summary of the assigned calendars & outcomes for this Rule Application: The Rule Summary overlay can be opened using the navigation button. This displays a summary of the rule and all calendar types and outcomes currently assigned to this rule application. A Lamp displays in each block on this pop-up screen to indicate the origin of the link to the rule, calendars and outcomes. A RULE or CATEGORY lamp notifies inheritance from rule or category. Where the link was created as part of the rule application, a lamp identifies the context system element (STUDENT, COURSE, ORG UNIT or CRS TYPE). Calendar Type, Student Start Period and Applications are displayed for each assigned calendar type. For each assigned outcome, the following details are displayed. Failures - displays the number of rule failures and the Repeat Failure Type to which the outcome is to apply e.g. 2/REPEAT. Outcome Type. Duration - where applicable (not all outcomes have duration values) displays both the number and type of duration periods for which the outcome is to apply e.g. 2/NORMAL.	The assigned calendars and outcomes cannot be altered in this overlay. Modify the assigned calendars using the Progression Rule Calendar overlay. Modify the assigned outcomes using the Maintain Progression Rule Outcome form. WARNING! After initial implementation, modifications to the configuration of the progression subsystem should be made with care and after thorough examination of the implications of the planned change.

Last Modified on 3 September, 1999