Communication Trigger Registry

Communication Trigger Registry

Communication Triggers initiate the creation and delivery of Correspondence items in response to certain events.
These events are updates to tables in the database, defined by SQL statements which are tested when these updates occur.
Each trigger calls a generic autonomous process to create the required correspondence record.
To activate the Correspondence Trigger, and therefore initiate correspondence the following must occur in CORW4000:

a). The System Correspondence Trigger corresponding to the table in which the change will occur, must be identified
b). The Type of communication appropriate for that event must be selected.
c). The Actual event must be defined. This is done in terms of a SQL statement
d). The Enabled checkbox for this trigger must be selected, to turn it on.

Delivery conditions can be defined for any database tables for which a System Communication trigger has been applied. (see Table below)
The delivery condition is a SQL statement (defined in CORW4000) that is executed at runtime when an event (insert, update, or delete) occurs on the underlying table. This statement must evaluate to the word “TRUE” (case sensitive) in order to allow the trigger to create a communication item. In CORW4000, a communication type is associated with the delivery condition to ensure that the Communication generated is appropriate for the event.

The following tables (and corresponding table triggers) are delivered as part of the Callista product:

Table	System Communication Trigger
ADM_COURSE_APPL_INSTANCE	TRG_ACAI_BR_IUD_COM
ADMISSION_APPL	TRG_AA_BR_IUD_COM
ADV_STND_UNIT	TRG_ASU_BR_IUD_COM
ADV_STND_UNIT_LEVEL	TRG_ASULE_BR_IUD_COM
ADVANCED_STANDING	TRG_AS_BR_IUD_COM
AP_APPLICANT	TRG_APA_BR_IUD_COM
AP_COURSE_APPLICATION	TRG_APCA_BR_IUD_COM
CAND_ABS_CLSFCTN	TRG_CAABSC_BR_IUD_COM
CAND_FIELD_OF_STUDY	TRG_CAFOS_BR_IUD_COM
CAND_SEO_CLASS	TRG_CSC_BR_IUD_COM
CANDIDATURE	TRG_CA_BR_IUD_COM
CANDIDATURE_ATT_HIST	TRG_CAH_BR_IUD_COM
FEE_ASS	TRG_FAS_BR_IUD_COM
GRADUAND	TRG_GR_BR_IUD_COM
MILESTONE	TRG_MIL_BR_IUD_COM
MILESTONE_HIST	TRG_MH_BR_IUD_COM
PERSON_PAYMENT_SCHEDULE	TRG PPS_BR_IUD_COM
PERSON_PRIZE	TRG_PPRZ_BR_IUD_COM
PERSON_SCH_MGT_PERIOD_ACTVTY	TRG_PSMPA_BR_IUD_COM
PERSON_SCH_PAYMENT_ACTVTY	TRG_PSPA_BR_IUD_COM
PERSON_SCHOLARSHIP	TRG_PSCH_BR_IUD_COM
PERSON_SMP_MANUAL_VRFCTN	TRG_PSMPMV_BR_IUD_COM
PERSON_SMP_RULE_VRFCTN	TRG_PSMPRV_BR_IUD_COM
RESEARCH_SUPERVISOR	TRG_RSUP_BR_IUD_COM
SCH_APPLICANT_ACTUAL_RESPONSE	TRG_SCHAAC_BR_IUD_COM
SCH_APPLICATION_ACTUAL_RESP	TRG_SCHAPAR_BR_IUD_COM
SCHOLARSHIP_APPLICATION	TRG_SCHAP_BR_IUD_COM
SPCL_CONSIDERATION_APPL	TRG_SCAP_BR_IUD_COM
STUDENT_COURSE_ATTEMPT	TRG_SCA_BR_IUD_COM
STUDENT_COURSE_INTERMISSION	TRG_SCI_BR_IUD_COM
STUDENT_PROGRESSION_OUTCOME	TRG_SPO_BR_IUD_COM
STUDENT_SCH_STATUS_ACTIVITY	TRG_SSCHSA_BR_IUD_COM
STUDENT_SCHOLARSHIP	TRG_SCH_BR_IUD_COM
STUDENT_SCHOLARSHIP_APPL	TRG_SSCHA_BR_IUD_COM
STUDENT_SCHOLARSHIP_APPL_RANK	TRG_SSCHAR_BR_IUD_COM
STUDENT_UNIT_ATTEMPT	TRG_SUA_BR_IUD_COM
STUDENT_UNIT_SET_ATTEMPT	TRG_SUSA_BR_IUD_COM
THESIS	TRG_THE_BR_IUD_COM
THESIS_EXAM	TRG_TEX_BR_IUD_COM
THESIS_EXAM_HIST	TRG_TEH_BR_IUD_COM
THESIS_HIST	TRG_TH_BR_IUD_COM
THESIS_PANEL_MEMBER	TRG_TPM_BR_IUD_COM
THESIS_PANEL_MEMBER_HIST	TRG_TPMH_BR_IUD_COM

Each of these tables can have several Communication triggers set up for it, each with its own associated communication type.
e.g. GRADUAND_APPR_STATUS changed to 'REJECTED' then a rejection email is generated.
e.g. GRADUAND_APPR_STATUS changed to 'APPROVED' then an approved email is generated.

Institutions may also add to this list of System Communication Triggers (and tables) - see Callista's Technical document - td_correspondence_and_communication.pdf for further details.

Last Modified on 6 July, 2010 1:24 PM

History Information

Release Version	Project	Change to Document
12.1.1.2	1580 - Correspondence	New Page