Set Student Unit Attempt Override Outcome Date - ENRJ0100

Subsystem

Enrolments (Cohort related)

Purpose

This job is used to set or remove a date that delays the access of particular cohorts of students to their results.

Normally Run By

A system administrator or Callista Connect specialist

Anticipated Frequency

As required for specific circumstances

Update Process(es)

Updates the Outcome Override Date for affected student unit attempts

Parameter Sample

 

   

Update Process

When a student attempts to access their on-line results for a unit via Callista Connect, the time during which they can access those results can be controlled by access window(s) for the particular cohort of students to which their unit attempt belongs. If, for any reason, it is required to delay the access of a particular cohort to results, the following practise can be used:

  • If the student unit attempts (SUAs) are represented by an existing cohort, use that cohort. Otherwise, create a new cohort (in GENF1000) to represent the group of unit attempts.
  • In GENF1100, create a cohort process window (for the appropriate calendar instance), making the start date value of the window the date that result access is to be delayed until.
  • Run this job (ENRJ0100) using the calendar instance and cohort as parameters to set the Student Unit Attempt Outcome Override Date for SUA members of the cohort.

Similarly, if Student Unit Attempt Outcome Override Dates have been set for SUA members of a cohort, these dates can be deleted, effectively re-opening access to results for those student unit attempts.

For more detail refer to the process type SET-OUTCME in the Cohort Process Windows special topic.

 

 

Run Details

This process is run in batch mode only when specifically required. This is usually when access to results for a particular group of student unit attempts must be delayed or when a delay in access applied previously is to be altered or removed.

Note: A student unit attempt that satisfies multiple cohort process windows (CPWs) will have its unit attempt override outcome date set to the CPW start date for the last occasion this job is run. For example, a unit being studied by Bob Burns satisfies the cohort for surname between A and C and the CPW start date is 01/06/2000. Bob's unit also satisfies the cohort for course code M300, with a CPW start date of 15/06/2000. If this job is run twice, for each of the cohorts, the date applied will be the CPW start date of the latest run.

This job should be used with caution, with extreme care being taken in the set up of cohorts. It is not easily possible to identify those student unit attempts affected by the running of this job.

Refer to the Job Control and Scheduling subsystem for details on scheduling and running jobs.

 

 

Job Parameters

The Assessment Period and Cohort parameters define the cohort of student unit attempts to be processed by this job, and indirectly the date to be inserted as the Student Unit Attempt Outcome Override Date.

The Set or Delete Access Dates parameter is set to SET when adding or amending Student Unit Attempt Outcome Override Dates or to DELETE when removing Student Unit Attempt Outcome Override Dates.

 

 

Logic

 If the Set or Delete Access dates parameter is set to SET:

The records to be processed are determined from the assessment period and cohort values specified as parameters to this job. These parameters also allow the job to determine the date value to be inserted as the Student Unit Attempt Outcome Override Date for each of the records processed. The date used is the earliest start date value for any cohort process window(s) matching the specified parameters.

 If the Set or Delete Access dates parameter is set to DELETE:

The records to be processed are determined from the assessment period and cohort values specified as parameters to this job and the Student Unit Attempt Outcome Override Date for each of the records processed is set to 'NULL'.

 

Last modified on 3 August 2000