8/13/2021 Alerts

 > Temenos Transact >

Home

Alerts
The Alerts Property Class is used in several product lines and results in the generation of Alerts for a particular activity on an Arrangement; provided
it is subscribed either by the customer or by the Account officers (DAO Alerts).

The Alerts Property Class manages the descriptive and classification details of the Alert and it is used to create and maintain the Alert record that is
related to the arrangement.

Customer and account officers can subscribe and unsubscribe the alerts at any time during the life of the arrangement.

Product lines

The following Product Lines use the Alerts Property Class:

Accounts
Agent
Deposits
Facility
Lending
Rewards
Safe Deposit Box

Property Class type

The Alerts Property Class uses the following Property Class types:

Dated
Enable External
Enable External Financial
Enabled For Memo
Non Tracking

Balance Prefix and Suffix

The Alerts Property Class does not hold any balance as it is not financial in nature. This implies that there is no associated Balance Prefix.

Attributes

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Alert.htm 1/3
8/13/2021 Alerts

The events for which the alert is required (provided customer has subscribed) must be input against the Event field. The conditions based on
which the system decides to generate alerts are provided in the associated sub-value fields namely Field and Value. These fields can be updated
only when Inherit is set to Yes in the respective TEC.ITEMS record.

EB.EVENT.TYPE
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:

AGE.OVERDUE CHANGE.CHARGE CHANGE.INTEREST

CHANGE.PRODUCT DISBURSE.ARRANGEMENT ISSUE.BILL

ISSUE.CHASER MATURE.ARRANGEMENT NEW.ARRANGEMENT

NEW.ARRANGEMENT.DAO NEW.ARRANGEMENT.DAO PAYOFF.ARRANGEMENT

RESET.ARRANGEMENT ROLLOVER.ARRANGEMENT

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

TEC.ITEMS
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 Specific Alerts

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.

NOTE: The alert conditions based on role is applicable only for arrangements and not for Portfolios. Alert subscriptions for account officer is
possible irrespective of permissions and restrictions for roles.

EB.ALERT.REQUEST
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.

Field and Operand

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Alert.htm 2/3
8/13/2021 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.

AA.ARR.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.

UNSUBSCRIBE
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.

Periodic Attribute Classes

There are no periodic Attribute Classes associated with Alerts Property Class.

Actions

The Alerts Property Class is associated with the following actions:

Action Description

EVALUATE This action is initiated automatically as part of any activity processed by the system.

SUBSCRIBE Used to subscribe to the Alerts.

Accounting Events

The Alerts Property Class does not perform actions that generate accounting events.

Limits Interaction

Actions associated with the Alerts Property Class does not have an impact on the Limits.

Published on :
Copyright © 2020-2021 Temenos Headquarters SA Monday, July 19, 2021 7:37:19 PM IST

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Alert.htm 3/3