| Top of COR | Index | Table of Contents | Feedback | |
CORINTR5 - Correspondence Special Topics
This section provides specialist users such as System Administrators and Subsystem Specialists with the information required to set up and maintain special areas within the Correspondence Subsystem.
The Special Topics include:
Incoming Email
Overview
With the introduction of emails as a form of correspondence between students and institutions, and the desire to load emails into Callista for Tracking and processing, the email infrastructure was created to enhance the existing messaging infrastructure to support incoming emails. The following graphic shows the process between Callista SMS and Java.
The follwing graphic expands on the previous graphic and looks at the Callista SMS files required to support Incoming Email.
Maintain Email Account - CORF2650
This form allows institutions to register the Email Accounts that should be read. Once an Email has been read from the registered account, the Correspondence Type, Provider, Server and Username cannot be changed . This will allow historial references later on. Information is stored in the MESSAGE_MAILBOX table.
Initiate Read of Email - DBMS JOB
This process checks the MESSAGE_MAILBOX table from CORF2650 to determine which registered account information needs to be forwarded onto the Advanced Queue (1).
Initiate Read of Email - Advanced Queue 1
When there are any open user account details that exist in the ‘Initiate Read of Email’ Advanced Queue (1), email details like username, password etc., are passed to this process. This process looks for any new Email in the inbox of the corresponding user account.
Read Email Account - JAVA
When there are any open user account details exists in the ‘Read Email Account’ advanced queue, email details like username, password etc., are passed to this process. This process looks for any new Email in the inbox of the corresponding user account.
This process opens the users Email Inbox folder with the given Username and Password and get the actual Email messages. These messages are passed to ‘Email Account Details’ Advanced Queue (2) and stored until another Callista job picks them up. If the delete flag is marked as 'TRUE', the actual Email message in the Inbox will be deleted, otherwise mark the Email as ‘Read’.
This queue that contains the email objects will hold the following data regarding the email:
Queue Email Account - Advanced Queue 2
This function checks whether any open mail boxes are waiting to be processed. The check is done on the open email accounts that have been registered by the institution in Maintain Email Account (CORF2650).
When open mail boxes are found, the job selects the Email details and places them into a queue for further processing. This process stores the actual Email message in the ‘Email Details’ Advanced Queue. ‘Record Incoming Correspondence’ (DBMS JOB) functionality will get these details from the queue and store in the corresponding Callista tables. An institution will be able to define the frequency that the function checks whether any messages exist. For example, the institution may want a check done every 10 minutes.
Record Incoming Correspondence - DBMS JOB
When there are new email messages existing in the queue, this function (Record Incoming Correspondence - DBMS JOB) selects those messages and creates the required correspondence records.
Following are the list of data elements that will be stored in correspondence tables:
This process has to find out the corresponding Person ID and store in the Incoming Correspondence table. If multiple matches are found then store all possible Person ID’s.
Callista SMS
Callista SMS forms that are linked to the Incoming Email system are:
Last Modified on 29 June, 2005