Manage Ceremony Graduands - GRDF3200

Purpose

To list graduands at ceremony round, ceremony, award or unit set group level depending on access point, and to set the approval status and conferral date as single actions for the selected set of graduands

Subsystem

Graduation

Structure

Two blocks

Ceremony Round
Graduands

 

Navigation button invokes:

Process buttons initiate:

Maintain Graduand Details (GRDF4200)

Setting of Approval Status
Setting of Conferral Date

Image

 

 

Access to this form is via either GRDF2100 (Maintain Graduation Ceremonies), GRDF2110 (Maintain Award Ceremony) or GRDF2120 (Maintain Unit Set Ceremony). It cannot be accessed directly from a menu.

The range of graduands listed here will depend on which form was used to gain access.
Access form (context)
.. lists all graduands recorded:

GRDF2100
  • in a ceremony round, or for a particular ceremony, depending which of two buttons was used in the access form

GRDF2110
  • for a specific honorary or course award within a ceremony

GRDF2120
  • for a particular unit set group in a course award and ceremony.

Graduands are listed either:

  • according to the order number assigned to them, which indicates their place in the ceremony, or
  • in alphabetical sequence if they have not yet been assigned an order number.

If some graduands have an order number and some do not, those with a number are listed first. Order numbers are assigned by running the job GRDJ5200.

Set approval status and conferral date

Two processes can be run to update values 'en masse' for all the graduands listed, with the exception of those specifically excluded by setting an indicator. These processes, initiated from buttons on the form, are:

 

The Ceremony Round block carries context from the access form.

New queries can be entered in this block to list different graduands, but the range is still determined by the initial access method.

Notes/Rules:

  • Since data for new queries must be typed in, it is sometimes quicker to return to the calling form to make a new selection.

In the Graduand block, all graduands matching the context data shown in the block above are listed.

Excluding graduands

When using the Set Approval (All) or the Set Conferral Date (All) buttons, select the Exclude indicator to exclude particular graduands from the processing initiated via these buttons.

To set approval

All students listed with an approval status equivalent to the WAITING system status can automatically have this status set to an equivalent of APPROVED.

To process:

  • Select the Set Approval (All) button
  • If only one user defined value equates to APPROVED, this is shown by default. Otherwise, select the required user defined value to which these graduands should have their approval status set.
  • Select OK (or Cancel to discontinue the operation).
  • You are prompted to confirm your intentions. Select OK (or Cancel to discontinue the operation).

The process is run, after which a further message indicates the outcome (see notes opposite).

If necessary, the approval status can be reset manually in GRDF4200 after running this job.

To set conferral date and graduand status

All students listed with:

  • an ELIGIBLE graduand status
  • an APPROVED approval status, and
  • an ATTENDING or INABSENTIA graduand type

can have a conferral date and GRADUATED status set automatically.

To process:

  • Select the Set Conferral Date (All) button.
  • If only one user defined value equates to GRADUATED, this is shown by default. Otherwise, select the required user defined value to which these graduands should have their graduand status set.
  • Enter the conferral date if different from today's date (the default).
  • Select OK (or Cancel to discontinue the operation).
  • You are prompted to confirm your intentions. Select OK (or Cancel to discontinue the operation).
  • A warning is given if any records cannot be changed because of incorrect initial statuses.

The process is run, after which a further message indicates the outcome (see notes opposite).

Navigation button

Use the Edit Graduand button to navigate to GRDF4200, where statuses can be changed and other graduand details amended.

  • Students graduating in absentia are not given an order number.
  • Graduands are first sorted by order number, and then by surname. This means that when the context is a complete ceremony round, the order numbers for different ceremonies sort together - all graduands in the round with an order number of '1' appear first, then all '2' graduands and so on.
  • The system will not set approval for graduands with an GRAD_BLK (block graduation) encumbrance effect.
  • The information message shown after setting approval gives the number of records successfully updated with an APPROVED value, and those that could not be updated because
    • the graduand has an encumbrance blocking graduation
    • another process was accessing the same record (locking conflict).
  • The information message shown after recording conferral date and GRADUATED graduand status displays the number of records successfully updated and those that could not be updated because
    • original statuses for the graduand prevented the update (see next note)
    • another process was accessing the same record, or changes to a record in a form had not yet been saved (locking conflict).
  • The system will only set the conferral date and GRADUATED status for graduands with:
    • an ELIGIBLE graduand status
    • an APPROVED approval status
    • a system graduand type of ATTENDING or INABSENTIA.
  • When setting the conferral date, a message about an incorrect format might indicate an invalid date (i.e. 30 February).
  • Once APPROVED statuses and conferral dates have been recorded, this information can only be changed at individual graduand level, using GRDF4200 (Maintain Graduand Details).

The graduand type cannot currently be changed once students are recorded as having graduated. The implication is that graduands' intentions regarding graduation ceremonies must be finalised before setting conferral dates and GRADUATED statuses. It is anticipated that a future release will relax this restriction.

 

Last Modified on 8 May 1999