1. Messaging User Guide
  2. Process Outgoing Messages

5 Process Outgoing Messages

This topic provides an overview of the process of generating an outgoing message.

In each module, while defining products indicate the messages that should be associated with an event in the life cycle of a contract involving the product. A contract goes through several events during its life cycle. A message for an event is triggered for a generation when the event is authorized. For example, While defining a product to cater to short-term loans, the following messages should be generated when events take place:

Table 5-1 Messages for Short-term Loans Product

Event Message
INITIATION Initiation Advice
LIQUIDATION Liquidation Advice
To initiate a short-term loan involving the product an Initiation Advice will be triggered for a generation. Similarly, To make a repayment on the loan, the liquidation advice defined for the event will be triggered for a generation.

Note:

In this context advices and messages are commonly referred to as messages.
Depending on the product - message - customer details, the address and the media through which the message should be transmitted. If a message is to be transmitted through Mail, it has to be printed. If the message is to be transmitted through Telex, enter the testword (if it is required for the message). The messages that are to be transmitted through media like Telex and SWIFT will be sent by the Media Control System (MCS) which is connected to the node in which the database of branch is installed. A message that is triggered for generation can be sent in the background or can be generated on-line. An outgoing message will be processed based on the preference that are set.

Note:

The messages that are triggered by an automatic event will be put in the Outgoing Browser by the automatic function itself. This is because events triggered by an automatic function do not require authorization.

This topic contains the following sub-topics: