Alerts

This table contains the list of all identified event types and the associated source table. The various events that trigger alerts for an arrangement and the associated records table are available in EB.EVENT.TYPE.

Sample event types release by Temenos Transact:

A sample record of EB.EVENT.TYPE is given below.

It defines the metrics based on which the alerts are triggered for an arrangement. For each TEC.ITEM record, the Event Type field holds the subscribed event and the associated activity that trigger an alert provided the condition given in Field Type and Value fields are met.

• Role is a valid record from AA Customer Role. It specifies the roles that can request for alerts for a corresponding event.

• Different customers of the arrangement can request for alert to the same event with same or different threshold values.

• During run-time, the system evaluates if each request qualifies for the event and generates an alert.

• Activities in arrangements like Change Customer, Change Role, and Change Product raise an override warning the user that this might affect active subscription. During runtime, before delivering the message, the system checks if the customer in their current role is allowed to the message.

• The list of events for which a customer can subscribe to an alert, the system decides it based on the customers’ role in the arrangement.

This application is used to subscribe to an alert. When the customer subscribes for an alert, then the respective arrangement is given in the Contract Reference field.

When an account officer subscribes to an alert, then user must specify the account officer ID in the Account Officer field. To subscribe to an alert, the Subscribe field must be set to Yes. A valid record in this application creates a corresponding record in AA.ARR.ALERTS.

The Field and Operand attributes define the conditions to be met so that the system generates an alert. Populating these fields can be either at the product or arrangement level and is based on the TEC.ITEMS that requires or uses a metrics evaluation for generation of alerts.

The system updates AA.ARR.ALERTS with the following details:

• Event – This field has the event subscribed by the user and it should be a valid record from TEC.ITEMS.
• Field and Operand – These two fields define the conditions to be met so that the system generates an alert.
• Request ID – This field can be updated the ID of EB.ALERT.REQUEST.
• Subscribed – This field can be set to Yes when an alert is subscribed and No if it is unsubscribed.

The user can unsubscribe an alert using the UNSUBSCRIBE enquiry. On selecting the respective alert request, the system opens EB.ALERT.REQUEST in input mode and uncheck the Subscribe field. On committing, this the system updates the Subscribed field with a value of NO in the AA.ARR.ALERTS application.