Versions in T24 – An Introduction
Conventions Used
Applications in T24 are represented in Bold Uppercase letters
The fields in the applications are mentioned in Uppercase letters
This learning unit is workshop based
Slide 2
Objectives
At the end of this learning unit you will be able to,
Explain what a Version is in T24
Create simple Versions in T24
Launch Versions in T24
Slide 3
What is a Version?
Version is a customised screen in T24
Version allows you to enter data in customised screens
Can be created for any application in T24
VERSION application is used to create versions
Versions work with all functions of T24
Slide 4
Task 1 – A simple Version
Create a version for the ACCOUNT application with the following fields
Customer Number, Mnemonic, Currency and Category
Version Heading “Temenos Training” to be displayed
Record needs to be authorised by an authoriser
Slide 5
Create The Version
Slide 6
Create The Version
Slide 7
Create The Version
Slide 8
Using the Version
Slide 9
Important Note – NO.OF.AUTH Field
Slide 10
Important Note – NO.OF.AUTH Field
In a VERSION when the field NO.OF.AUTH is set to zero , it becomes a auto-auth version.
Slide 11
Important Note – NO.OF.AUTH Field
1 3
Slide 12
When creating a Version - Remember
Unless ALL mandatory fields of an application are part of a version - it
will become useless for record input.
Field inter-dependencies exist. Must be considered while designing
version
Slide 13
Workshop 1
Create a version for the CUSTOMER application
Name of the version CUSTOMER,XXX (XXX is your initial)
Fields to be displayed
MNEMONIC
SHORT.NAME
NAME.1
STREET
SECTOR
Account Officer
INDUSTRY
TARGET
NATIONALITY
CUSTOMER.STATUS
RESIDENCE
LANGUAGE
Slide 14
Task 2 – Version with Multiple Fields Per Line
Create a version for the ACCOUNT application with the following fields
Mnemonic, Customer Number, Currency and Category
Mnemonic and Customer Number need to be displayed one beside the
other
Currency and Category need to be displayed one beside the other
All fields to have user defined field labels
Slide 15
Create The Version
Slide 16
Create The Version
Slide 17
Output
Version name can be suffixed with a valid T24 function to open the version in that
particular function
F3 auto generates the ID
Slide 18
Manipulating field Display in Version
Field Display - Before Formatting
Field Display - After Formatting
Slide 19
Workshop 2
Amend the version already created to display 2 fields in a row rather
than one
Slide 20
Task 3 – NOCHANGE,NOINPUT and MANDATORY Fields
Create a version for the ACCOUNT application with the following fields
Mnemonic, Customer Number, Currency, Category , Account Title.1 and
Short.Title
1 2,3&4
Slide 21
Create The Version
Actual Version Screen shot
Slide 22
Create The Version
Slide 23
Create The Version
Slide 24
Create The Version
Slide 25
Output
Slide 26
Workshop 3
Amend the previously created version so that
A value 1000 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.
Slide 27
T24 Naming Convention for Zero – Auth Versions
Sometimes referred to as ‘Comma’ versions
Some of the default comma Versions in T24,
ACCOUNT,
FUNDS.TRANSFER,
CUSTOMER,
Records created using comma versions are self authorised.
In all comma versions the NO.OF.AUTH field is set to 0(zero).
Use VERSION, from now on to create your versions .
Slide 28
Quiz
Version is a customised screen in T24 – True / False
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 – True /
False
If the value for the field FIELDS.PER.LINE is set to one in the version,
the COLUMN field becomes mandatory – True / False
In version values can be defaulted into fields using the field
AUT.NEW.CONTENT – True / False
The value of a NOCHANGE field can be amended for a LIVE record -
True / False
Slide 29
Rekey field in Version
Rekey in versions are triggerred on authorisation.
Can be used for sensitive data.
Specific important fields are re-entered by authoriser.
Rekey fields data are hidden during authorisation.
Slide 30
Task 1 - Rekey in Version
Create a version for FUNDS.TRANSFER application
Input the mandatory and required fields in your version.
Slide 31
Task 1 - Rekey in Version (contd…)
Enter the fields required in your version
Commit and authorise the record.
You can use the comma version.
Slide 32
Task 1 - Rekey in Version (contd…)
Input a funds transfer record using the newly created version.
A screen is opened as per the version with the header title
Click on the new deal icon
Slide 33
Task 1 - Rekey in Version (contd…)
Fill the data for the funds transfer record
Commit the record
Slide 34
Task 1 - Rekey in Version (contd…)
When the record is opened in the authorize mode, rekey fields are hidden
When the authorize button is hit, the
system prompts the user to re-enter value Try keying in values that do not
in the rekey fields match with the Inputter’s data
Slide 35
Task 1 - Rekey in Version (contd…)
Login as another user to authorise the record.
Click on the Authorise link and the rekey fields are displayed
Slide 36
REKEY Retries
The Rekey count is recorded in the application
EB.REKEY.RETRIES
Maximum number of incorrect rekeys allowed is set in SPF
Slide 37
REKEY Retries
When the max number of rekey retries exceeds, an error is
displayed.
And, a different user is required to authorize the record
Slide 38
Summary
Versions are user defined screens and can be created for any
application in T24.
A version should always compliment 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 authorisers can be set to 0,1 or 2 in a version
Special field properties like NOINPUT, NOCHANGE, MANDATORY can
be set using versions.
Values can be defaulted into version fields.
Version allows you to perform additional validations.
Rekey field in VERSION enables enhanced verification by the
authoriser in the Banking System
Slide 39
A review Versions in T24 – An Introduction
You have learnt Versions in T24. You can also create simple versions in
T24. You will now be able to,
Explain what a Version is in T24
Create simple Versions in T24
Launch Versions in T24
Slide 40
Thank You
