Maintain Student Progression Rule Check

Maintain Student Progression Rule Check - PRGF6600

Purpose	To view details of progression rules checked for a Student Course Attempt. To execute a manual progression rules check for a Student Course Attempt. To allow access (in the context of a Student Course Attempt) to the form where progression outcomes may be added and maintained.
Subsystem	Progression
Structure	Three blocks	Student Course Attempt Student Progression Period Student Progression Rule Check
	Navigation buttons (in Student Progression Period block) invoke	Manual Rule Check process Maintain Student Progression Outcome form Progression Rule Application overlay Student Unit Attempt overlay
	Navigation buttons (in Student Progression Rule Check block) invoke	Rule Message text box Progression Rule Summary pop-up Maintain Student Progression Outcome form
Image

The process of evaluating student course attempts against applicable progression rules may be done in two ways — as a batch process (through scheduling the job PRGJ6100) or as a manual process for an individual student (using this form).

The complete configuration of the rules applied to an individual student course attempt can be displayed from this form. This includes the origin of the rule application - course type, organisational unit, course version or student course attempt. All progression calendars & outcomes linked to the rule, the level from which they have been inherited (rule category, rule or system element) and any limits on the rule application (such as attendance type, student start period or number of applications) can also be viewed.

Where progression rules have been evaluated for a student, the date and result of this evaluation can be viewed. Summary details of the student unit attempts included in the evaluation can also be displayed.

This form can be used for the following purposes.

To view the details of all progression rules checked for an individual Student Course Attempt.

To run a manual progression rule check against a Student Course Attempt.

To create a manual outcome against a Student Course Attempt (without this outcome having to be the result of failing a progression rule check). Note: The use of non-rule related outcomes should be in accordance with institution policy and provide transparent and equitable progression results for students.

To access PRGF6610 where existing student progression outcomes can be maintained.

Student Course Attempt Context Block: This form may be accessed from the Student Course Attempt form (ENRF3000) or directly. When accessed from ENRF3000 applicable Student Course Attempt details, including Course Attempt and Progression Statuses, are displayed. When accessed directly, the required Student Course Attempt should be retrieved using a query or the Find Person button. In this block, a Lamp displays where: the student has a Show Cause or Appeal period available e.g. SHOW CAUSE AVAILABLE the student has shown cause or submitted an appeal and is awaiting a decision on that application e.g. APPEAL SUBMITTED.	Notes/Rules: A query can be performed on these fields (alone or in combination): Person ID, Course Code, Version number, Course Attempt Status or Progression Status.
Student Progression Period Block: All progression periods in which the context Student Course Attempt has enrolled units or those within an academic period for which the student course attempt is pre-enrolled, are displayed in this block. Where the configuration applicable to the context Student Course Attempt allows the calculation and display of current course and period Grade Point Average (GPA) or Weighted Average Mark (WAM) values, these are displayed beside the progression period for which they have been calculated. The latest calculated and stored value for that period is displayed. (For calculation details refer to the Special Topic.) A NON-RULE OUTCOME lamp displays where one exists for the Student Course Attempt, beside the progression period in which it was created. The creation of these outcomes is described below.	The display of GPA and WAM fields is dynamic and depends on the configuration applicable. There may be an apparent discrepancy between the GPA/WAM value displayed and the result for a GPA/WAM rule in the next block. The GPA or WAM value displayed here may have been calculated at a different point in time from any GPA/WAM calculation performed as part of a rule check. Thus the values are not necessarily the same even though they have been calculated in the same progression period.
Manual Rule Check command button: Use this button to execute rule checking of all applicable rules for this Student Course Attempt and progression period. This performs the same rule checking process as the batch job PRGJ6100, but for the context student only. This process is fully described in the documentation for PRGJ6100. Where this manual rule check results in a different pass/fail status for any rule, the changed result and any changes to outcomes are recorded in the database and displayed in the next block (with a check type of MANUAL). The recalculated GPA/WAM values are updated and displayed.	Previous rule checks for the same progression period may have been done (either as a SYSTEM, TODO or MANUAL check type) and details of these display in the next block.
To create a Manual Outcome: Use the navigation button to access PRGF6610. A manual outcome, unrelated to a progression rule check can be created for this Student Course Attempt in that form.	When PRGF6610 is accessed using this button all existing outcomes (rule and non-rule related), for the context progression period, are displayed and can be maintained.
Rule Application Detail overlay: This overlay screen displays all rules applicable to this Student Course Attempt in this Progression Period. The details displayed here have been defined in the rule application (using PRGF5200). Relation Type describes the system element in the progression application hierarchy from which this application derives. It may be course type, organisational unit, course version or student. The Rule Summary button can be used to access a pop-up screen displaying additional information about the context rule (described below).	Data displayed in this overlay cannot be edited.
Student Unit Attempt overlay: This displays summary details for those Student Unit Attempts that contributed to the rule evaluations for the context progression period. This information can aid understanding the progression rule evaluation results as the mark, grade and result for each unit is displayed.	Data displayed in this overlay cannot be edited. Where a student unit attempt result is unfinalised no mark or grade is displayed and the Result field contains UNFINALISED.
Student Progression Rule Check block: Summary information is displayed for each progression rule checked in the context progression period, against this Student Course Attempt. For each rule the most recent evaluation performed and earlier evaluations with existing PENDING or APPROVED outcomes are displayed, unless the Show All indicator is set. Setting the Show All indicator allows the display of the details of all checks of each rule that resulted in different pass/fail evaluations. For each rule, the rule category and rule/reference code is listed. Where this rule check was failed, a FAILED lamp displays. The outcome details displayed (Outcome Type and Decision Status) are a subset of the full information relating to the student progression outcome added as a result of failing this rule. This outcome can be maintained in PRGF6610 accessed using the Student Outcome button in this block. This may display the value The Check Type is a system-defined type and describes the method used to initiate the rule check. The Rule Message button opens a text box overlay where an explanation about why this student failed this rule can be viewed. This message is returned from the rule checking process, for failing rule evaluations only. The Rule Summary button can be used to access more information about the context rule.	Details displayed in this block cannot be edited here. To display a history of all rule checks for the context period, select the Show All indicator and re-query the block. The Outcome Type and Decision Status fields may display the value MULTIPLE, where more than one outcome has been added as the result of this failed rule A SYSTEM check type is displayed where the rule check was an initial automatic check applied by the system. A MANUAL check type is displayed where a manually applied check was initiated from this form. A TODO check type is displayed where this check was an automatic check applied as a result of a Student ToDo entry. The execution of automatic rule checking is described fully in PRGJ6100.
Rule Summary pop-up: This pop-up screen displays a summary of information relating to the context progression rule application. The Progression Rule Summary block displays the rule category and code, along with their descriptions. The rule text displayed is the actual rule constructed in RULF2000. The user-defined message displayed is inherited from one stored against either the rule application, rule or rule category (inherited in that order, where different messages have been stored at more than one level). A Lamp displays in the top right corner of this block indicating to which system element this rule has been linked, in creating this rule application. It will be CRS TYPE, COURSE, ORG UNIT or STUDENT. The lower blocks display summary information for all calendar types and outcomes currently assigned to this rule application. A lamp displays in each of these blocks to indicate where the calendars and outcomes have been inherited from - one of the system elements (Course Type, Course Version, Organisational Unit or Student Course Attempt), the rule or the rule category.	Rule, calendar and outcome details displayed in this overlay cannot be edited here. Calendars displayed here are assigned using one of PRGF1600, PRGF5100 or PRGF5200. Outcomes displayed here are defined using PRGF5214, accessed from the appropriate application level form (PRGF1600, PRGF5100 or PRGF5200).

Last modified on 9 September, 1999