Alerts Processing
Release: R19 AMR
May 2019
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means, for any purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.
© 2019 Temenos Headquarters SA - all rights reserved.
Alerts Processing
Table of Contents
Introduction 3
Purpose of this Guide 3
Intended Audience 3
Overview 4
Setup 5
Deal Processing 6
2
Alerts Processing
Introduction
Purpose of this Guide
This document provides the details about subscribing Alerts and generating Events
based on customer role.
Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.
3 Introduction
Alerts Processing
Overview
During Alert subscription, if the customer role is eligible for the Event inputted then
subscription is allowed. After the Alert subscription, if the customer has undergone
a role change then during the Event generation; the system again verifies if the cus-
tomer role is eligible for the Event.
Overview 4
Alerts Processing
Setup
Map the role APPLICANT for the Event LARGE.DEPOSIT.
The customer 10 is mapped the role as APPLICANT in the below Arrangement.
Also, the Alert request can be subscribed successfully for customer 10 as shown in
the below.
5 Setup
Alerts Processing
Deal Processing
The same Event is configured for multiple customers with different conditions.
If the FT amount is posted as 2000, then both Event conditions are satisfied.
The AA.ARRANGEMENT.ACTIVITY is triggered for above FT (as shown in the below
screen shot).
Deal Processing 6
Alerts Processing
The Event list file is updated with two Events under the FT transaction reference.
Event log is updated with both the Alert request references.
After running the EVENT service. The Event status is changed to HANDOFF and also
the delivery references are generated for both the Events.
7 Deal Processing
Alerts Processing
The Alert is now generated for the customer 300840
The Alert generated for the customer 10 is as shown in the below screen shot.
Deal Processing 8
Alerts Processing
Now the Arrangement is updated with one customer 300840 with allowed role after
the Alert subscription.
The Arrangement record is updated with the customer details.
Post the FT as shown in the below screen shot.
As result, only one Event for the customer 300840 alone is triggered. And the Event
for customer 10 is not triggered.
9 Deal Processing
Alerts Processing
Deal Processing 10
