Student Progression Outcomes are added to a Student Course Attempt in one of two ways:

1. When a Progression Rule Check is run (either through the scheduling of job PRGJ6100 or as a Manual Rule Check from PRGF6600) and one or more rules are failed, Progression Outcomes are added automatically, to the Course Attempt. These Outcomes are those that the institution has linked (through PRGF5214) to the Progression Rule application. The settings inherited from that link determine whether the outcome is added with a Decision Status of PENDING or APPROVED and whether the outcome is automatically applied.

2. Secondly, there may be circumstances where a Progression committee decides a Progression Outcome should be applied to this Student Course Attempt, even though the student has not failed a Progression Rule Check. A non-rule related Progression Outcome may be added to a Student Course Attempt using this form, accessed from PRGF6600 using the Manual Outcome button.

This form is used to maintain both types of Progression Outcomes for a single Student Course Attempt. This maintenance can include:

• Adding an alternative outcome for this student's failing of the Progression Rule.
• Updating the Decision Status of the outcome.
• Applying the outcome to the Student Course Attempt, once it has been approved.
• Varying details of the outcome for this student, for example extending the duration of the outcome.
• Maintaining information relating to any Show Cause or Appeal available to and/or submitted by the student.

Two of these maintenance tasks can be done as bulk processes:

• Changing the Decision Status for a group of students can be done using the form PRGF6700 (Maintain Progression Outcome Decision).
• The job PRGJ6800 (Apply Progression Outcomes) can be run to apply all approved Progression Outcomes to Student Course Attempts.

The Student Progression Rule Check block contains:

• Person ID
• Course Version
• Acacemic/Progression Period
• Rule

The Student Progression Outcome block contains:

• Failure/Failure Type
• Rank
• Outcome Type
• Decision Status
• Duration
• Duration Type

  T-List

  • Decision
    • Decision Org Unit
    • Decision Date
    • Varied check box
  • Application
    • Applied Date
    • Expiry Date
    • Discontinuation Date
    • Reason Code
    • Apply button
  • Restrictions
    • Encumbrance Course Group
    • Restricted Attendance Type
    • Restricted Enrolment CP
  • Show Cause
    • Expiry Date
    • Show Cause check box
    • Outcome Type
    • Outcome Date
    • Comments
  • Appeal
    • Expiry Date
    • Show appeal check box
    • Outcome Type
    • Outcome Date
    • Comments
  • Comments
    • Comments

  Buttons

  • Excluded/Suspended Courses (overlay)
  • Student Outcome Rule (PRGF5200)
  • Excluded Unit Sets (overlay)
  • Encumbrance
  • Excluded/Required Units (overlay)
  • Student Rule (PRGF5200)
  • Student Appeal (ENRF3210)

Rules/Notes:

The Decision Org Unit LOV displays the committee hierarchy organisational units for both the Org Unit defined at course version and course ownership level.

Student Progression Rule Check block:

Information which identifies the context person & course, the status of the Course Attempt, the Student's Progression Status and the Academic / Progression Period is displayed in this block. The remainder of the context information is dynamic and determined by the method used to access this form.

When the form is entered in the context of a failed Progression Rule (using the Student Outcome button on PRGF6600), the rule details and date of the Rule Check are displayed.

When the form is accessed using the Manual Outcome button on PRGF6600 there is no information identifying Rules and Check Dates.

Rules/Notes:

Queries cannot be performed in this block. Return to PRGF6600 to retrieve a different context record.

A lamp may also display if a student is an ESOS SVH (Education Services For Overseas Student Visa Holder) student. This lamp is derived from the configurable PRG_STUDENT_IND_V view for the context person and course.

Student Progression Outcome block:

Progression Outcomes (resulting from Rule Checking in the context period) display in this block. When entered in context of a Failed Rule (from PRGF6600 only those outcomes added because of that Rule Failure display.

When accessed using the Manual Outcome button, all outcomes added in the context period are displayed. These may be related to various rules or not rule-related (i.e. manually added).

Rules/Notes:

The method of accessing this form determines which student Progression Outcomes are displayed.

An Outcome that is part of a rule application displays both Failure/Failure Type values.

An outcome added manually will not display any Failure/Failure Type or Rank values.

To Manually add a Student Progression Outcome:

There are two different purposes in manually adding a student Progression Outcome.

One may be as an alternative to the System-added Outcomes resulting from a Rule Check. Entering this form via the Student Outcome button allows the insertion of a new alternative outcome in addition to those the System added as the result of failing a Progression Rule check.

Secondly a Progression Outcome may be added that is unrelated to failing a Progression Rule. Accessing this form via the Manual Outcome button allows the addition of a non-rule related outcome.

To add a Student Progression Outcome, enter/select a Progression Outcome Type. The Decision Status defaults to PENDING.

The Progression Outcome Type selected determines whether any duration details can be entered.

Rules/Notes:

Failure/Failure Type and Rank cannot be entered for a manually added outcome.

A System Progression Rule Outcome Type of EXCLUSION, EXPULSION or NOPENALTY cannot have any Duration values.

A System Progression Rule Outcome Type of SUSPENSION must have both Duration values.

An EFFECTIVE Duration Type can only be used for a System Progression Rule Outcome Type of PROBATION.

Where Duration values are entered, both must exist.

To Maintain an Existing Student Progression Outcome:

For all student Progression Outcomes, possible maintenance tasks are:

• Updating the Decision Status.
• Modifying any of the Student Progression Outcome settings, e.g. Duration values.
• Recording / modifying any restrictions (on student enrolment to be applied through Discontinuation or Encumbrances).
• Applying an approved Outcome (so it takes effect).
• Updating show cause and/or appeal details.
• Creating an outcome-related Progression Rule to apply to this student.

To maintain Progression Outcomes use the appropriate access method to ensure display of the outcome/s required.

Rules/Notes:

The T-List in this block is dynamic. Where configuration settings applicable to this Student Course Attempt do not provide a Show Cause or an Appeal period, those items are not available in this list.

Bulk processes can update the Decision Status (PRGF6700) and apply approved Outcomes (PRGJ6800). Using this form, these tasks can be done for a single Student Course Attempt only.

Updating the Decision Status:

Decisions taken about this student Progression Outcome by a Progression Review Panel (or an authorised individual) are recorded by updating the Decision Status and recording the required details against the Decision T-List item.

When changing the Decision Status to any status other than PENDING, the Organisational Unit responsible for this decision and the date of the change must be recorded. The Org Unit Code entered (or selected from the List of Values) can be either that which owns the course or a parent Organisational Unit. The decision date is automatically inserted but can be backdated.

The changing of the Decision Status may trigger a change in the Progression Status. A Student Course Attempt may have multiple Outcomes. Where a decision is taken to approve only one, the remaining outcomes should be waived to ensure that the Student's Progression Status correctly reflects this decision. Any remaining PENDING outcomes result in a Progression Status of UNDCONSID.

This check box is set by the system. This occurs when any of the values, inserted into this student Progression Outcome from an existing Progression Rule Outcome (defined in PRGF5214), are modified. These changes may be made to:

• Duration/Duration Type
• Encumbrance Course Group
• Restricted Attendance Type
• Restricted Enrolment Credit Points

Where Course, Unit Set or Unit Codes have been added or deleted to the Outcome.
An Outcome Rule is modified.

The Progression Outcome may have default duration values (entered when defining this outcome in PRGF5214). These defaults can be modified, for this specific student Progression Outcome.

Where duration values are required, but none exist an error is triggered and the values must be recorded before the outcome can be committed.

Rules/Notes:

Decision Status changes allowed:

PENDING to APPROVED (where this outcome resulted from the most recent check of this rule in this Progression Period. Outcomes pending as a result of an earlier Rule Check in the same Progression Period must be waived).

PENDING to WAIVED.

APPROVED to WAIVED (when the Outcome has not yet been applied).

APPROVED to PENDING (when the Outcome has not yet been applied. Existing decision details are deleted).

APPROVED to CANCELLED (after an Outcome has been applied and before the Outcome's Expiry Date).

WAIVED to PENDING or APPROVED (the Outcome must be one added as the consequence of the most recent Rule Check in this Progression Period. Waived Outcomes from earlier checks of this rule in this period cannot be reset. Decision details must be deleted when updating status to PENDING; inserted when updating status to APPROVED.)

CANCELLED to APPROVED.

Recording/Amending Restrictions associated with the outcome:

Some Outcomes are linked to Encumbrance effects that require recording of restriction values.

The Restrictions T-List item is used to display these fields. The required restriction may be an Encumbrance Course Group code, Restricted Attendance Type or Restricted Enrolment Credit Point value.

The value may have been defined as part of the Progression Outcome Type and this default value can be modified for this Student Progression Outcome.

Where the Progression Outcome Type definition did not include this required value, the required value must be entered before the Outcome can be committed.

Rules/Notes:

Restrictions T-List fields are disabled where the Progression Outcome Type does not require entry of a restriction.

A Progression Outcome Type with one of the following encumbrance type effects requires a restriction entry.

RSTR_LE_CP or RSTR_GE_CP requires a Restricted Enrolment Credit Point value.

RSTR_AT_TY requires a Restricted Attendance Type value.

EXC_CRS_GP requires an Encumbrance Course Group Code value.

Applying the Progression Outcome to the Student Course Attempt:

The Application T-List item allows this student Progression Outcome to be applied. The Apply command button executes the same process for one Student Course Attempt as that executed by the job PRGJ6800 for a group of students. (The process is fully explained in the job documentation.)

An Outcome must have a Decision Status of APPROVED before it can be applied. An Outcome can be approved then immediately applied.

The application of the Outcome triggers application of any associated Encumbrance effect to the Student Course Attempt. This may be Course, Unit Set and/or Unit Discontinuation or an Enrolment restriction.

The Student's Progression Status may be updated, where this applied Outcome requires a change to the existing status value. For example, a student with a Progression Status of GOODSTAND who has a suspension applied has his status automatically updated to SUSPENSION. A second student, currently on probation with a restriction on her Enrolment to a maximum of 2 credit points (and with a status of PROBATION) may have a second Outcome applied. This Outcome requires this student to enrol in a specified unit. Because this is an Outcome with a System Progression Rule Outcome Type of PROBATION, it does not trigger any change to this Student's Progression Status.

Rules/Notes:

An Outcome cannot be applied where the applicable configuration allows a Show Cause / Appeal Period but does not allow the application of an outcome before the period is complete.

An OUTCOME APPLIED Lamp indicates the context Outcome has already been applied.

Multiple Outcomes may be approved and applied to a Student Course Attempt.

Attempting to apply an Outcome where the effects conflict with an existing Outcome triggers 1 of 3 possible actions:

• The existing outcome may be automatically expired,
• A warning may display, or
• The current application may be blocked until the conflicting outcome is manually expired.

If required, an Expiry Date can be manually back-dated (from this form, PRGF6610) to a date that is greater than or equal to the Encumbrance Start date and less than or equal to the current date.

If the Expiry Date of a Student Progression Outcome Application is updated and applied (via the Apply button in PRGF6610), any associated Person Encumbrance and Encumbrance Effect Expiry Dates in ENRF6320 (for Academic Encumbrances) are automatically set to the same value as the Expiry Date in PRGF6610 for the Outcome application.

Note: An Expiry Date that was manually applied to an Outcome (in this form) can subsequently be deleted (ie. set to NULL); for example, if you want to make the Encumbrance ACTIVE.

Recording Show Cause details:

An Expiry Date for the Show Cause Period is entered automatically if it can be derived by the System. It can be entered manually (or modified) up until a decision has been made on any submission from the student.

Set the Show Cause check box when a student makes his/her submission. The current date is automatically entered as the Show Cause Date, but can be backdated.

When the Student's Show Cause Submission has been reviewed and a decision on it made, the decision is entered against the (show cause) Outcome Type. There are two System-defined options - UPHELD or DISMISSED. The Outcome Date defaults to the current date. Notes about the decision and the submission can be recorded in the Comments text box.

Where a Show Cause submission is upheld, the Decision Status for this Progression Outcome should be updated to WAIVED. Progression Status (for this Student Course Attempt) reverts to the status that existed prior to this Progression Outcome's approval. (That may have been GOODSTAND or another status resulting from a different Progression Outcome.)

If the submission is dismissed, the Progression Outcome can now be applied and the Decision Status remains APPROVED. The Progression Status (for this Student Course Attempt) may update to reflect this approved Progression Outcome. (Note: it may not change as the existing status may reflect another 'more severe' Progression Outcome also in force.)

Rules/Notes:

This T-List item is available only where the configuration applicable to this Student Course Attempt and rule application allows a Show Cause Period. A SHOW CAUSE AVAILABLE lamp signifies this.

Where a Show Cause Period is allowed, the Progression Status (for this approved student Progression Outcome) is SHOWCAUSE until the period expires or a decision on a submission is recorded.

A warning is displayed if an entered Expiry Date is later than the applicable Cut-off Date (see configuration).

The Show Cause check box can only be set where the Decision Status is APPROVED.

A SHOW CAUSE SUBMITTED lamp illuminates when the Show Cause check box is set.

Recording Appeal Details:

An Expiry Date for the appeal period is entered automatically if it can be derived by the System. It can be entered manually (or modified) up until a decision has been recorded about any appeal lodged by the student.

Set the Appeal check box when the student lodges his/her appeal. The current date is automatically entered as the Appeal Date. This date can be backdated.

When the student's appeal has been heard and a decision on it made, the decision is entered against the (appeal) Outcome Type. As for Show Cause, there are two System-defined Outcome Types available. The Outcome Date defaults to the current date. Notes about the decision and the submission can be recorded in the Comments text box.

Appeal outcome details can be recorded, via the Student Appeal button, on the Maintain Student Appeal form (ENRF3210). Supporting documentation can also be uploaded on form ENRF3210.

If the appeal is upheld, the Decision Status for this Progression Outcome should be updated to CANCELLED. This change in Decision Status may be applied immediately in this form or through the subsequent running of PRGJ6800. When the change is applied, the process automatically deletes any associated Encumbrances or lifts any discontinuations that had been applied to the Student Course Attempt. It may also alter the Progression Status for this Student Course Attempt.

If the appeal is dismissed, the Decision Status of APPROVED remains, with any associated Encumbrances or Discontinuations in effect. The existing Progression Status remains.

Rules/Notes:

This T-List item is available only where the configuration applicable to this Student Course Attempt and rule application allows an appeal period. An APPEAL AVAILABLE lamp signifies this.

A warning is displayed if an entered Expiry Date is later than the applicable Cut-off Date (see configuration).

The Appeal check box can only be set where the Decision Status is APPROVED.

An APPEAL SUBMITTED lamp illuminates when the Appeal check box is set.

The Appeal date cannot be earlier than an existing show cause date.

Recording Notes Relating to this Student Progression Outcome:

Notes can be recorded about both the Show Cause and Appeal in the Comments text boxes available against each of those T-List items. An additional Comments T-List item provides another means for recording notes.

Certain Progression Outcome Types may require a student be excluded or suspended from one or more Courses or Units Sets. Other Progression Outcome Types may require a student be either excluded from or required to enrol in one or more units.

The overlays available allow the recording of the required Course Codes (Excluded/Suspended Courses overlay), unit set codes (Excluded Unit Sets overlay) or unit codes (Excluded/Required Units overlay).

Where an Outcome (resulting in a Course Exclusion or Suspension) has been added automatically after Rule Failure, because the outcome was defined as part of the rule application (in PRGF5214), Course Codes may have been defined. Those codes default to this student Progression Outcome. Where no codes were recorded as part of the Rule Application Outcome, the current course is the one to which the Encumbrance is applied for this Student Progression Outcome.

Additional Course Codes may be recorded or existing default codes deleted from those automatically recorded for this student Progression Outcome.

A manually added outcome requires the entry of all required Course Codes, including the current course when the exclusion/suspension is to apply to that course.

Rules/Notes:

If no codes are entered where an APPROVED Progression Outcome requires entry of Course, Unit Set or Unit Codes, an error message is displayed and the outcome cannot be committed.

The buttons are disabled where no Course, Unit Set or Unit Codes need to be entered for the context student Progression Outcome, in these overlay screens.

If the Include all versions of the Unit Set when assigning to a SCA check box is selected, all versions of the Unit Set are excluded and a version cannot be entered for the Unit Set.
If the Include all versions of the Unit Set when assigning to a SCA code is not selected, then a version must be recorded for the Unit Set and only that version of the Unit Set will be excluded.

If the Apply to all courses for student check box is selected, then the Unit Set will be excluded from all courses that the student undertakes.
If the Apply to all courses for student check box is not selected, then the Unit Set is only excluded from the context course attempt.

A Progression Rule application for this student can be created as an outcome of an existing Rule Failure. This rule can only be applied for this student, when the outcome is approved and applied.

Use the Student Outcome Rule button to navigate to PRGF5200 to create this Progression Rule application with the Student Course Attempt and Progression Outcome as the context.

Use the Student Rule button to navigate to PRGF5200 to create a specific rule application for this Student Course Attempt, unrelated to a student Progression Outcome.

A rule application created in this way is applied to the context Student Course Attempt in the applicable Progression Period (determined by associated calendars). Its application is not reliant on the approval of any existing outcomes.