23.version Routines R16

1

Version Routines

Objectives

Objectives Learning Objectives 2



Understand the T24 Customization Scope



Understand the need for Versions



Need for Version routines



Types of Version Routines

What is a Version? 3

What

Customised screen for any application in T24

Why

Helps encapsulate information based on roles

Allows to customize for a role rather than everything for everybody

Helps setup security for data

Allows to simplify input by defaulting values

Helps improve the look and feel of the system

Catalogued in VERSION application

Helps banks customize the system without raising change requests to Temenos.

Allows to specify levels of authorization for a transaction. Allows banks to define their own validation rules.

Versions – Views of an application 4

CUSTOMER

@ID

NAME.1

REGION

NO.OF ACCOUNTS

TRANSACTIONS. LAST.MONTH

100297

HARRY

SFO

2

189

6000

178677

TONY

NY

3

234

7800

View created for a Teller

ACCOUNT. BALANCE

View created for a Relationship Manager

@ID

NAME.1

@ID

REGION

NO.OF ACCOUNTS

TRANSACTIONS ACCOUNT .LAST.MONTH .BALANCE

100297

HARRY

100297

SFO

2

189

6000

178677

TONY

178677

NY

3

234

7800

T24 Extensibility 5 ID ROUTINE.

CHECK RECORD ROUTINE, AUTO FIELD ROUTINE VALIDATION ROUTINE INPUT ROUTINE

AFTER UNAUTH ROUTINE

BEFORE AUTH ROUTINE

AUTHORISATION ROUTINE

Routine Invocation Stages in the Template Life Cycle 6

.ID

.RECORD

ID Routine

Check Record & Auto Field Routine

.AUTHORISE

.VALIDATE

Validation & Input Routine

.PROCESS

After Unauth Routine

Before Auth and Authorisation Routine

7

VERSION routines in Unauthorized Stage

Scenario 1 8



A version for the ENQUIRY application is created



You have been assigned the task of ensuring that, ID of records created using the above version should be automatically prefixed with text ‘TEM.TRG’



The ID length should not exceed 30 characters. Display Error “Temenos Trg restricts ID length to 30 Characters” if condition not met



Default enquiries should not be modified using this version



How will you cater to this requirement

ID Level Validation 9

ID routines manipulate the id of the record.

Invoked as soon as the id of the record is entered by the user.

New errors can be generated on further checks

ID Routine

ID Routine – Task 1 - Steps 10

Create the version for the ENQUIRY application. Create a subroutine that does not allow 

modification of default enquiries in T24 ,



prefixes the id of the enquiry with ‘TEM.TRG’ and validates the length of ID.

Make an entry in EB.API.

Attach the routine to your version record using the field ID.RTN.

The subroutine & Output 11

Scenario 2 12

A version for the ACCOUNT application is created. Any

user of this version should be allowed to open only account records that belong to

CATEGORY 6001

Check Record routine

Record validation 13

Alters field attributes or default values into fields Invoked after the id is entered and validated.

Gets invoked when the functions I(Input), D(Delete), A(Authorize) and R(Reverse) are used

Attached to the field CHECK.REC.RTN of the version

Check Record Routine

The CHECK.REC.RTN 14

Scenario - 3 15

A version for the Account Application is available. User wants to display the total number of USD accounts created till date in a Local Reference field, when the record is displayed.

Auto Field routine

Auto Field Routines 16

Manipulate the content of a field before display Invoked after the id of the record is supplied and the corresponding record is fetched from the file, but before the record can be displayed.

Routines are to be attached to the field ‘Aut New Content’ in the Version Application

Auto Field Routine

The AUTO.FLD routine 17

Gets the position of the LOCAL.REF field

GET the number of accounts

Scenario 4 18

For a FUNDS.TRANSFER transaction, when

Validation routine

the user enters a value in DEBIT.ACCT.NO and tabs out, the DEBIT.CURRENCY field should

be auto populated with the

currency of the specified account.

Also validate that the Debit Account

Currency and Credit Account Currency are the same. Otherwise, generate an error message “Debit and Credit Currency are not equal”

Input routine

Field Level Validation 19

Perform field level validation

Default values into fields

Validation Routine

Existing validations cannot be changed Input Routine Invoked on committing the record.

The Validation routine 20

The Input routine 21

Difference between Validation and Input Routine 22

Input Routine

Validation Routine 

Invoked on committing the record or



also after you tab out of field. 



Routine name must be specified in

Invoked on committing/validating a transaction after validation routine.



Input routines are attached in the

the field VALIDATION.RTN in VERSION

field INPUT.ROUTINE in the VERSION

application.

application.

Values can be extracted from R.NEW or COMI.



Values are extracted from R.NEW .

Scenario - 5 23

A

version

for

the

account

application is available. Whenever a user commits the record, if the category is 5999 (NOSTRO) you

want to write the Customer No, Account No and currency in a flat file

After UnAuth routine

After Unauth Routine 24

After Unauth Routine is used to edit a record written to the $NAU file.

invoked when record is committed.

Any changes made to R.NEW will not be reflected as it has already been written to the $NAU file Attached to the field AFTER.UNAU.RTN in the version and make an entry in EB.API

After Unauth Routine

The code for AFTER.UNAUTH routine 25

26

VERSION routines in Authorised Stage

Scenario - 6 27

Whenever a user authorises a new account for a particular customer, the total number of accounts held by the particular

customer should be stored in a Local Reference field attached to the version.

Before Auth routine

Before Auth Routine 28

Before Auth Routine allows you to do some processing before writing the record to the live file. Invoked during the authorization stage of an INAU record

Invoked before a F.WRITE is made to the live file

Invoked before Authorization Routine.

Before Auth Routine

The code for Before Auth routine 29

Scenario - 7 30 

Once a record in a version of the FUNDS.TRANSFER application is

authorized, the following details must be extracted from the transaction and written on to a flat file named TEMENOS.TRAINING (for interface purposes )delimited with a single space

DEBIT.ACCT.NO CREDIT.ACCT.NO DEBIT.VALUE.DATE

DEBIT.AMOUNT DEBIT.CURRENCY 

ID of the record in the flat file should

be the ID of the FT record.

Authorisation routine

Authorization Routine 31

Invoked at the authorization stage

Used to update local files

Invoked after a write is made to the buffer

Authorization Routine

VERSION.CONTROL 32

• VERSION.CONTROL is a T24 application that allows users to group VERSION records and to control field attributes based on defined conditions. • The routines to be executed can be attached to this record, and commonly

applied across the group of VERSION records of the application. • If the id of VERSION.CONTROL record is the application name itself, then the routines specified here, are applied to the application • VERSION.CONTROL is an addition to the VERSION application. It does not replace the VERSION application.

Workshop

Workshop Workshop 1 33



Create a version for the DEBIT CARD application with all the mandatory fields



Every time this version is used to issue a new debit card, it should populate the STATUS field as “CURRENT”

Workshop

Workshop Workshop 2 34



Create a TESTCASE for the Input Routine that checks if the DEBIT.CURRENCY and

CREDIT.CURRENCY for an FT are matching

The Input Routine 35

Steps to create a .TUT 36

INPUT.RTN does not take any parameters

Set the DEBIT.CURRENCY Set the ACCOUNT record

Steps to create a .TUT 37

The TESTCASE 38

Conclusion

Summary What Did We

Learn? 39

In this learning unit/course, you learnt about the basic version routines in T24 • You will now be able to: • Explain what a Version is in T24 • Explain the need for version routines • Create different version routines