1

Customized Screens

T24 Versions Application

NOTICE
 
Copyright © 2010 - Present- Temenos Headquarters S.A. All rights reserved.
All content and images contain herein are copyright protected and are the property of Temenos Headquarters S.A. and/or its affiliates. You may
not reproduce, modify, distribute or republish materials contained in these materials (including by framing or similar means) without prior written
permission. You may not alter or remove any trademark, copyright or other notice from these materials.  Any rights not expressly granted herein
are reserved.
 Learning Objectives
2
Objectives

• Identify the T24 Customization Scope

• Understand the need for Versions

• Learn to create a version

• Apply the additional features of a version

• Tabbed Screens in versions

 Scenario - Need for Versions
3
Allen wants to deposit a Local Cheque in to his Cathy wants to deposit a foreign Cheque in to
account her account

The tellers have to fill in different

set of fields in the same application
- TELLER

A Customized Screen of TELLER

A Customized Screen of TELLER
application with fields specific
application with fields specific to
Foreign Cheques
Local Cheques
 Versions – Views of an application
4
Actual Table

Customer No Name Region No of Accounts in Transactions Account

the region Last Month Balance

100297 Harry SFO 2 189 $6000

178677 Tony NY 3 234 $7800

Customer No Customer No No of Accounts in Transactions Account

Name the region Last Month Balance

100297 Harry
100297 2 189 $6000
178677 Tony
178677 3 234 $7800

View created for a Call Centre Analyst View created for a Manager
Need for Version?
5

• To allow users to only input and view what they need for that
role

• Applications have a default view which displays all the fields

and may confuse the user

• To improve the look and feel of the system

• To Control the number of authorizers

What is a Version? • Version is a customised screen in T24
6
• Allows you to default values in fields

• Allows you to hide non mandatory information

• Can be created for any application in T24

• Catalogued in VERSION application

Task - 1
7

Create a version for the ACCOUNT application with the following fields
 Customer Number, Mnemonic, Currency and Category
 Version Heading “Temenos Training” must be displayed
 Records created using the version must be authorised by an authoriser
Step 1 - Create The Version
8
Step 2 – How do we invoke the version created?
9
Workshop
• Create a version for the CUSTOMER application 10

• Name of the version CUSTOMER,TRG

• Fields to be displayed in the version
• MNEMONIC
• SHORT.NAME
• NAME.1
• STREET
• SECTOR
• ACCOUNT.OFFICER
• INDUSTRY
• TARGET
• NATIONALITY
• CUSTOMER.STATUS
• RESIDENCE
• LANGUAGE
Task 2 – Version with Multiple Fields Per Line
11
 Task 2 – Version with Multiple Fields Per Line
12

• Specify Column in which Field must be displayed

• Specify the Text to be displayed beside the field

• Table Column – No Input field populated to show length and start-position of the field
being defined

• Table Line –Line in which this field will be displayed

Manipulating field Display in Version
13

Adding blank
lines

Field Display - Before Formatting

Field Display - After Formatting

Version – Additional Configuration
14
Set No of Authorizers

Set a field as No Input

Set a field as No Change

Default values in a field

Replace Old content of a field

Set a field as mandatory

Workshop
15

 Amend the previously created version so that

 A value 1001 is defaulted in the field SECTOR
 Make SECTOR a NOINPUT field
 A value IN is defaulted in the field NATIONALITY if the
previous available value is US
 Make CUSTOMER.STATUS a mandatory field
 Ensure that the value of ACCOUNT OFFICER is not
changed once the customer record is authorized.
Zero – Auth Versions
16

Create Record
 Referred to as ‘Comma’ versions
Commit / Save
 Some of the default comma Versions in T24,
 ACCOUNT,
 FUNDS.TRANSFER,
 CUSTOMER,

 Records created using comma versions are self authorized.

 In all comma versions the NO.OF.AUTH field is set to 0(zero).

 Use VERSION, from now on to create your versions .

Tabbed Screens in Versions
17
 A list of VERSIONs can be associated with the current VERSION in the form
of tabs

 These associated versions must relate to the same application as the version
being input
Rekey Field in Version
18

• Rekey is a feature which forces authorizer to rekey values during

authorization

• Rekey fields data are hidden during authorization

• The Rekey count is recorded in the application EB.REKEY.RETRIES

• Maximum number of incorrect rekeys allowed is set in SPF

Did you know that an

authorizer must
re-enter some values
during authorisation in a
version ?
Using Rekey Field Illustration
19

The Bank wants the Head Teller to re enter values of

Debit Amount and Debit A/C no when any transaction
is input using the version

The teller inputs a

transaction

The Head Teller opens

the transaction to
authorize . The Rekey
fields are hidden
Using Re-key field – Authorisation of a record
20
The Head Teller authorizes
the record . The Rekey fields
are hidden

During authorization, system prompts the HEAD Error will be shown if the values keyed during
TELLER to re-enter value in the rekey fields authorization do not match the values that were
input.
Workshop
21

 Amend CUSTOMER,TRG created in Workshop

 Add CUSTOMER,AUDIT and CUSTOMER,ADDRESS as TABS in

your version
 Ensure that NAME.1 is entered correctly by re-entering during the authorize

 Set the NO.OF.AUTH as 2 , authorize your record once and check the RECORD.STATUS

 What is the RECORD.STATUS when the record is authorized using the CUSTOMER application?
Workshop
22

Design a simple version for FUNDS TRANSFER application with the

following fields

Transaction Type

Debit Account Number

Debit Currency

Debit Amount

Debit Value Date

Credit Account Number

Credit Currency

Add Tool Tip and Enrichment for fields

 Quiz
23
True / False
Quiz

1. FUNDS.TRANSFER,INPUT can be given as the associated version for

CUSTOMER,INPUT

2. The field NO.OF.AUTH is set 2 in the version, now when you authorise a
record created using the version, it moves to LIVE status

3. In version values can be defaulted into fields using the field

AUT.NEW.CONTENT

4. The value of a NOCHANGE field can be amended for a LIVE record

 What Did We Learn?
24
Conclusion

• Versions are user defined screens and can be created for any
application in T24.

• A version should always complement the functionality provided by an

application and not overrule it.

• Using a version you can input records , only when all the mandatory
fields of the application are part of your version.

• The number of authorizers can be set to 0,1 or 2 in a version

• Special field properties like NOINPUT, NOCHANGE, MANDATORY can

be set using versions.

• Rekey field in VERSION enables enhanced verification by the authorizer

in the Banking System

 What Did We Learn?
25
Conclusion

You can now

• Appreciate the need for Versions in T24

• Create simple versions in T24

• Apply additional features in versions such as

NOINPUT, NOCHANGE, MANDATORY, AUTOM
FIEL, REKEY FIELD

• Create associated versions