Purpose

This form will allow the institution to create Email Types and define their content

This function will allow the institution to create Email Types and define their content.

The function will allow the creation of an institution-defined email type. For each email type, the following information will be defined:

• Reply-to email address
• Description
• Subject
• Body
• System Message Content Type
• The set of Email Substitution Tags that can be used within the body and subject of the email

When adding institution-defined tags, remember not to make the tag like normal text as blocks of text could be replaced that you don't want replaced. Instead, consider unique tags not found in normal text. For example, ##PROMPT-ST## as a beginning tag is unique and would never be seen in normal text.

This form is accessed from the main menu.

The Email Account block contains:

• Email Type
• Closed check box
• Reply to Address
• Description
• Subject
• Message Content Type (LOV)
• Body
• File Name

Button

• Edit

The Email Substitution Tag block contains:

• Substitution Tag (LOV)
• Description

Rules/Notes:

The Edit Button

This form utilise the webutil feature. The ’Edit’ button opens the content column in a default editor (Notepad). This allows the user to edit and save data exceeding 32000 characters outside the form. The results can be saved back to the database.

Validations include:

• Email Substitution Tag is closed
• System Message Content Type must be TEXT/PLAIN or TEXT/HTML
• System Message Content Type must not be closed
• Reply To Email Address must be a valid email address
• The Receipt body tag can not be used in the subject line of an Email Type

It is possible to use an institution defined substitution variable that maps to the same system substitution variable as another institution defined variable. See an example of a diagram of the Receipt Email with a Connect Application Receipt Tag below

The last validation means one institution defined mapped variable at a time in a document. When an email type has multiple institution substitution tags that map to a single system tag the above validation will fire.

A Receipt BODY Tag. When the function that issues the email encounters the RECEIPT-BD tag (<REC-BD>), it will go to the Connect Receipt Application and collect the applicable part of the receipt template, then format the body of the email from the receipt template. See Receipt Application for more details.

The Connect Transaction Application and the Self-Serve Application Transaction Log Substitution Tags, PROMPT, OLD (Value) and NEW (Value) have both a start and end tag:

• PROMPT-ST and PROMPT-END
• OLD-VL-ST and OLD-VL-END
• NEW-VL-ST and NEW-VL-END

Using the start and end tags allow the Administrator to include within the email definition a call to a Connect Receipt Application with effect of the tag being substituted by the Connect Application.

For example, using the start tag #PROMPT-ST#; the end tag #PROMPT-END# and a parameter sequence for a specific prompt of 3 would look like:

• #PROMPT-ST#3#PROMPT-END#

Email Type:

EMAIL_TYPE.EMAIL_TYPE

Text

VARCHAR2 (10)

.

Closed

EMAIL_TYPE.CLOSED_IND

Check box

VARCHAR2 (1)

.

Reply To Address:

EMAIL_TYPE.REPLY_TO

Text

VARCHAR2 (100)

.

Description:

EMAIL_TYPE.DESCRIPTION

Text

VARCHAR2 (60)

.

Subject:

EMAIL_TYPE.SUBJECT

Text

VARCHAR2 (500)

.

Message Content Type:

EMAIL_TYPE.S_MESSAGE_CONTENT_TYPE

Text (with LOV)

VARCHAR2 (10)

.

N/A

S_MESSAGE_CONTENT_TYPE.DESCRIPTION

Display Field

VARCHAR2 (60)

Not Updateable. Message Content Type Description

Body:

EMAIL_TYPE.CONTENT

Text

CLOB

.

Substitution Tag

EMAIL_TYPE_SUBSTITUTION_TAG.EMAIL_SUBSTITUTION_TAG

Text (with LOV)

VARCHAR2 (10)

.

Description

EMAIL_SUBSTITUTION_TAG.DESCRIPTION

Display Field

VARCHAR2 (60)

Not Updateable