Correspondence - for the Subsystem Specialist

This section of the user manual provides specialist users such as system administrators and subsystem specialists with the information required to set up and maintain the reference data used by the Correspondence subsystem and the setup data required for correspondence system letters generated from other subsystems.

Documentation for correspondence type security is accessed through field help in form SECF0033.

An overview of the day to day operation of the subsystem is provided in Understanding Correspondence.

Steps in setting up Correspondence reference data

There are four main steps in setting up Correspondence reference data:

 

Recording Correspondence Types

Institution defined correspondence types are recorded in the Maintain Correspondence Types form (CORF2110).

Linking correspondence types to the outputs from System jobs

When a System job which produces correspondence is run, the correspondence is registered against each student who is due to receive it. The System determines which students are to receive a correspondence item by checking that their correspondence category is associated with a correspondence type which is also related to the output from the job.

CORF2110 is used to associate the output from a correspondence generating job with a correspondence type.

Recording a new correspondence category

Correspondence Category

An institution defined name for a group of correspondence items which are produced for and sent to a particular group of students.

For example, students in correspondence category STANDARD are sent a defined set of correspondence. Students in another correspondence category, COMMERCIAL, are sent a different set of correspondence which, for instance, does not include an institution supplied enrolment form.

Correspondence categories are recorded in the Maintain Correspondence Categories form (CORF2200). Establishment of correspondence categories is carried out at the time of setting up the System. Addition of new categories is an infrequent event but can occur to cater for a new type of student with non standard needs, such as may be the case for a new commercial client.

Each student is either assigned or defaulted a correspondence category in either the Admissions or Enrolments subsystems.

Associating correspondence types with correspondence categories

Correspondence types are associated with a correspondence category using CORF2200.

cor01

Students only receive correspondence when their course attempt's correspondence category indicates they should. The System determines this by checking that a correspondence type related to a job output is also related to the student. The association with the student is not a direct one. It is achieved via the correspondence category. Hence the creation of relationships between correspondence category and correspondence types.

CORF2200 is also used to block the issue of correspondence to encumbered students.

Steps in setting up Correspondence System Letters.

Creating Letter Phrases

When a system letter is produced, it is possible to insert appropriate phrases, to personalise the letter for the individual. These phrases may be set up as a standard set by the institution or can be added as phrase text, prior to producing the letter. For phrases to appear on a letter, the appropriate letter parameter of type PHRASE must be included in the system letter definition and the template.

Institution defined phrases are recorded in the Letter Phrase form (CORF2550).

Creating Letter Parameters

When a system letter is produced, it is possible for data, text and phrases to be inserted either from Callista or the Rules engine. For items to appear on a letter, the associated letter parameters must be included in the system letter definition and the template.

Institution defined letter parameters are recorded in the Letter Parameter Types form (CORF2510)

Creating System Lettters

System Letters can be created for a range of correspondence items. System Letters contain definitions of the template to be used, and the associated letter parameters to include in the letter.

Institution defined system letters are recorded in the System Letter form (CORF2520)

Creating System Rules

System rules can be created for individual correspondence items, within subsystems. System Rules generally return text to be included in the letter.

Insitution defined system rules are recorded in the Maintain Group Rules form (RULF2001)

Creating Letter Templates

Letter templates are used by institutions to determine the layout of information, and the formatting of the information. Letter templates are created using Microsoft Word and must be stored in the directory specified in control.doc. The file 'control.doc' must be in the c:\tmp directory of the client machine(s) being used to produce letters. This file contains Word macros and is supplied with Callista. Letter templates are designed for particular instances of correspondence types.

Individual letter templates are created for specific subsystems. See the links below for particular subsystems;

Admission Correspondence Template design

Producing system letters

System letters can be produced either singularly (within each subsystems 'produce letter' functionality), or as a batch job. Each subsystem has its own batch job, that extracts the data to be used for producing system letters. All system letters can be produced as batch jobs via the Batch Letter Production form (CORF2540).

See below for links to subsystem letter production .

 

Last modified on 22 September 1999