| Top of GSFF | Index | Table of Contents | Feedback | |
GENJ0100 - Send Scheduled Emails
| Purpose |
This job generates Proposal and Graduand emails |
|
| SubSystem |
System |
|
| Normally Run By | System Specialist | |
| Anticipated Frequency | This job should be scheduled to run daily. |
|
| Structure | No Parameters | |
This job is not initiated by any buttons or parameter forms. It is scheduled using the Callista Job Scheduler to deliver the email messages that have been scheduled for delivery to Proposals users and graduands. For information relating to the Callista Job Scheduler see JBSF5210. Once an email is processed , its corresponding record in the EMAIL_NOTIFICATION table is deleted and a new record is inserted into the EMAIL_LOG table. If processing fails for any email, then it's record it isn't deleted from the EMAIL_NOTIFICATION table, and no entry is made in the EMAIL_LOG table. During processing, a count is kept of all records processed, the number of records that were successfully transferred into the EMAIL_LOG and the number of records that failed. This information is recorded in the RUN_LOG table. |
For Proposals, the emails generated have a generic subject line that informs the recipient that it is Proposals emails for the day, including the range of days that the email applies to. The range of days that the email applies to refers to the number of days that the email notifications span (e.g.. …sent on Monday (13/07/2009) for emails from prior 2 days).
An email is sent for all emails that form part of the same email group, and each group will have a separate email. Email groups are defined in CORF2690 and are used to link similar types of emails so that administrators can make a conscious decision to send out those emails in a single correspondence.
The email body will contain the emails grouped in days, with the subject and body of each email being recorded together.
This job generates emails for EMAIL_NOTIFICATION records using the Email address for each recipient as determined by CORW0100). If no email address can be found for an individual then an error is logged in the S_ERROR_LOG table and the process continues.
Emails contain communications grouped together by email group name.
The Reply To address is determined by the Reply To Address value set for the Email Group in CORF2690.
The content of the message is a concatenated string of messages that are grouped together.
Each message lists the subject on a separate line to the body of the email. The emails are listed in order of days (ascending), with each day having a heading on a separate line to the rest of the content. i.e. Structure as shown below:
<email subject 1>
<email body 1>
<email subject 2>
<email body 2>
Thursday 16/07/2009:
----------------------------------------------------------------------------------------
The timing of Proposal emails for a person is set up in their Proposal Person Configuration (SECW0066), where the proposals user can decide what days they should receive communication emails, or if they should even receive emails. These settings are very important in the running of this job and will impact the frequency of emails received.
Last Modified on 30 May, 2012 11:36 AM
History Information
| Release Version | Project | Change to Document |
| 12.1 | 1455 - Online Eligibility to Graduate | Extended to include Graduand emails |
| 12.0.0.2 | 1574 - CAPS -Pt 2 | New Help page |