More on TWS Part 2

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law. Information in this
document is subject to change without notice

Objectives

In this learning unit you will learn, how TWS handles,

Overrides
Hook Routines
Arrangements

Slide 2

TWS and Overrides

Slide 3

TWS and Overrides

You have seen how to expose FT transaction using TWS in the

previous session.

What happens to Overrides? How does TWS handle them?

Slide 4

TWS and Overrides

Slide 5

GTS Control values

Value

Status of OFS Response

Null

Error - Reject record & return error response

Override Approve automatically and commit

Error $NAU file with status hold

Override Approve automatically and commit

Error - Reject record & return error response

Override $NAU file with status hold

Error $NAU file with status hold

Override $NAU file with status hold

All transactions Write all transactions into $NAU file with status HOLD

Slide 6

Take a look into some of the Account Records

Slide 7

Do a FT transaction using TWS Project

Slide 8

Same FT record in T24

Slide 9

TWS and Overrides

Slide 10

TWS and Hook routines

Slide 11

TWS and Hook Routines

You can customize a T24 application using Version routines.

Let us now see how Version routines work with TWS

Slide 12

Input Routine

Slide 13

Input Routine

Slide 14

Input Routine

Slide 15

Workshop 1

Create a TWS project for the Account application and test the same.

The version used,

Should contain all the mandatory fields
Should have an Input Routine that will check whether the currency is left
blank and if currency is left blank,
Value USD to be to the currency field.

Slide 16

TWS and AA

Slide 17

Arrangement Architecture Quick Overview

T24 Arrangement Architecture (AA) is a comprehensive, component

based product definition and servicing framework.
The foundation of the T24 Arrangement Architecture (AA) is the
Product Builder which enables the design, proofing, and publishing of
products and services to the Product Catalogue.
The published Products are used to create and control the individual
customer Arrangements which are serviced by T24.
Servicing of T24 Arrangements is accomplished through Arrangement
Activities.
Unlike most other T24 applications, an Arrangement Activity is first
explicitly selected and any necessary input is restricted to the
appropriate attributes.
Each Activity is comprised of one or more Actions which are the
specific units of processing performed by a Property Class

Slide 18

AA Terms
Product: A Product is a saleable unit made up of properties and conditions.
For example: PERSONAL.LOAN.
Where,
Property is an instance of product class that contains attributes and activity.
Ex: ACCOUNT.
Conditions define default values and negotiable rules.
Ex: PERSONAL.LOAN.

In an arrangement, negotiable properties can take input from the users while
others will have conditions in default.

Activity is a Business function which is triggered by a user, the close of

business, or another T24 application like Funds Transfer or Teller.
Ex: LENDING-NEW-ARRANGEMENT.

Slide 19

How to launch an Arrangement Activity in T24

Launch a new Arrangement Activity.

Based on the product selected, key in the values like Customer number,
currency or effective date to validate the eligibility of the Customer for the
product.
PRODUCT and ACTIVITY get populated automatically.
When the validation is successful, T24 will automatically load the various
properties of the arrangement.
Key in the negotiable values.
Submit the arrangement for authorisation.
You can also create an arrangement activity using
AA.ARRANGEMENT.ACTIVITY, but you have to specify the PRODUCT and
ACTIVITY manually.

Slide 20

How To Expose AA as TWS Web Service

Create a version for AA.ARRANGEMENT.ACTIVITY.

Why? Because AA.ARRANGEMENT.ACTIVITY holds the arrangement

activities.

While creating the version, auto populate ACTIVITY and PRODUCT.

Why ? Failing to supply this information will result in an error when

creating web services.

Create PW.ACTIVITY and EB.SERVICE record as usual.

Slide 21

TWS and AA

PRODUCT and ACTIVITY fields are auto populated in the VERSION record.
Once the version is created, PW.ACTIVITY and EB.SERVICE records has to be
created as usual.
Create the TWS project.

Slide 22

PW.ACTIVITY and EB.SERVICE records

Slide 23

Test the TWS project

Slide 24

AA Record

Slide 25

Workshop 2

Create and test a TWS Project, using an existing

AA.ARRANGEMENT.ACTIVITY Version.

Slide 26

Quiz

An FT raises the override DEBIT VALUE DATE LESS THAN

MINIMUM BACK VALUE DATE . What will happen if this FT
transaction was put through using TWS?

An input validation routine has been attached to a LD version. What will

happen to the transaction record if the validation fails?

Transaction on hold
Transaction error in TWS
Transaction result depends on GTS.CONTROL Value

The record will be put on hold

Transaction error is thrown
Transaction in INAU status

You wish to call the activity INTERNET.SERVICES-UPDATEDAILYLIMITS through TWS. Which applications version will you use?

AA.ARRANGEMENT
AA.ARRANGEMENT.ACTIVITY
AA.ACTIVITY

Slide 27

Summary

In this learning unit you learnt, how TWS handles

Overrides
Hook routines
Arrangements

Slide 29