T24 Versions - R19 F-1

Allen and Cathy want to deposit cheques in bank ABC. Allen wants to
deposit a local cheque ,whereas Cathy has a foreign cheque . The teller
has to fill these details in TELLER application. There are some fields that
are required for a foreign cheque but not for a local cheque. Example :
Currency . How can we make things easier ?
T24 gives us the luxury of designing our own screens from a base
application. Here, TELLER is the base application. We cull out fields
required for a local cheque and design a screen .Similarly we can design
another one for foreign cheques. Now the tellers can invoke the screen
they want ! Simple, isn’t it?

T24 Versions - R17 F-4

Versions can be compared to the concept of “Views“ in Database
Management system . A table may consist of several columns(fields) that
might not be required for all users. So the users can create views, consisting of
the columns that they need . When we use a spreadsheet with multiple
columns, we hide the columns that might not be necessary and project those
we need. Versions help us in creating screens with the fields we want.
 Imagine that you have to input a funds transfer transaction in T24. You
will use the FUNDS.TRANSFER application, and the input function to
do so. The screen that is displayed to you contains all the fields in the
FUNDS.TRANSFER application some of which may not be relevant for
the transaction that is being input. A first time user may not be able to
figure out which fields to use and which not to. What if you had a
customized screen that showed you only the fields that you require to
input?

You can create customized application screens in T24. They are called
versions. The VERSION application is used to create customized
application screens. Your version you can have the mandatory fields of
the FUNDS.TRANSFER application.

Can you view data using versions? Versions behave like the
application, but only look different. All functions can be used with a
version.

T24 Versions - R17 F-6

 What is a VERSION?
• Version is a customised screen in T24

• 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

T24 Versions - R17 F-7

 VERSION can be created in two ways.

For the old browser or the BrowserWeb UI, we can create VERSION by
creating a record in the VERSION application. The utility to create the VERSION
record is SCREEN.DESIGNER. SCREEN.DESIGNER is launched by the command
COS SCREEN.DESIGNER. We will use the SCREEN.DESIGNER to create VERSION
in this lesson.

For the new browser UXP Browser

T24 Versions - R17 F-8

Design Studio separates the run time and design time
It has intuitive graphical tools to create/modify VERSION
VERSIONs can be imported from T24 into Design Studio, modified and
deployed back to T24
VERSIONS can also be created in Design Studio and the required VERSION
records are created automatically in T24
Design Studio can also generate the files required for displaying the VERSION
in the UXP Browser
T24 Versions - R19 F-10
 The above screenshot shows the design studio workbench

T24 Versions - R19 F-11

 In a Model Bank workspace, some projects are available by default. The
projects we will be using are
BRP-models
all the Design Studio artifacts will be stored here
BRP-models-gen
Contains all the generated artifacts from the model project
These artifacts are deployed on the server
t24-localhost-tafj-server
To connect to T24

T24 Versions - R17 F-12

To connect to a T24 area, we need a T24 server project. For the workshops,
we will use the t24-localhost-tafj-server project.

Under the config folder, click on server.properties. Give Username and

password. Password will be encrypted. The protocol is ws(webservice),
Hostname is the IP address of system where jBoss is running and port is the
jBoss port.

The –models-gen project must be shown in deployed projects. Check that the
*-models-gen project is added to Deployed Projects. If not, in the Server view
pane, right-click the line T24 Connection ([server name]) and choose
Add/Remove project(s)... A dialog box is displayed with a list of all -gen
projects in the workspace. Check each –gen project to deploy and click OK to
validate the selection

The Servers tab displays the server projects that are available. The required
server must be “Active”
Ideally, the VERSION must be created in the required folder under the
appropriate component. For training purposes, we will create a folder called
training under BRP-models and create our VERSIONs in that folder
Information about T24 applications( information from STANDARD.SELECTION,
etc.) is available in the domain folder. Domain information must be available
before T24 artefacts can be created. Domain naming convention is
ModuleName_Application name (e.g. ST_Customer.domain,
AC_AccountOpening.domain)
T24 Versions - R17 F-16
T24 Versions - R19 F-17
 The file name extension for a VERSION/SCREEN in Design Studio is .version

T24 Versions - R19 F-18

 In the Fields Selection area, click on Mandatory Fields and choose the >> to
move them to the selected Fields List. The Primary Key should not be
selected. Click on the Primary Key and < to un-select it. Remove
CURRENCY.MARKET as it is not required

T24 Versions - R17 F-19

 Add the other required fields MNEMONIC and CUSTOMER

T24 Versions - R17 F-20

 Click on a field and use translation tab to set the label that will be displayed
next to the field

T24 Versions - R19 F-21

 Press Ctrl-G to Generate Code. Design Studio will generate the required
IRIS files – for communication between UXP Browser and T24,
EDGE files – for the UI
T24 VERSION record

T24 Versions - R17 F-22

 Press Ctrl-G to Generate Code. Design Studio will generate the required
IRIS files – for communication between UXP Browser and T24,
EDGE files – for the UI
T24 VERSION record

T24 Versions - R17 F-23

 We can see the VERSION record that was generated from Design Studio in T24
VERSION application. The DS.TELNET in the Inputter field indicates that the
record was created from design Studio

T24 Versions - R17 F-24

 The VERSION is launched from the command line using ACCOUNT,TRG I F3

T24 Versions - R19 F-25

 The record that is committed using the VERSION is stored in ACCOUNT$NAU
as the no.of.authorisers in the ACCOUNT,TRG version is set as 1. when a
record is committed, T24 defaults some fields, we can see this in the
ACCOUNT record.
We can use the VERSION just like the APPLICATION
Any function that we can use in the APPLICATION can be used with the
VERSION also

T24 Versions - R17 F-26

T24 Versions - R17 F-27
 T24 allows a maximum of 2 levels of authorisation. The default number of
authorisers is 1 for any application
Number of Approvers(NO.OF.AUTH) - enables the user to specify the number
of authorisers required when using this version.
When it is set to 0 your version becomes an Auto Auth or self-authorisation
version. The record is authorised on commit.
When Number of approvers is set to two, two different users must authorise
the record. When the record is authorised for the first time, it moves to INA2
status. In order to make it as a LIVE record, the record has to be authorised by
a different user again

T24 Versions - R17 F-28

 The number of approvers for this record is set to zero. Hence, When a record
is created using this VERSION, it will be authorized.

T24 Versions - R19 F-29

 Row column position is defaulted as the layout is chosen as
twocolumnhorizontal. Other layouts are available and required layout can be
chosen. The row column positions for the fields will be set automatically

T24 Versions - R17 F-30

 When the Input Behavior is set as NoInput, the user will not be able to modify
the content. In the above screenshot, CATEGORY is made a NOINPUT field

T24 Versions - R17 F-31

 When the Input Behavior is set as NoChange, the user will not be able to
modify the content once the record is authorised. In the above screenshot,
CUSTOMER is made a NOCHANGE field

T24 Versions - R19 F-32

 We can specify a value to be displayed in the field, using the Defaulting tab.
The multivalue(MV) and the subvalue(SV) position must be specified. We can
also specify an Existing value. Only if the existing value is equal to this value,
the New value will be defaulted.

T24 Versions - R17 F-33

 MNEMONIC is not a mandatory field in the ACCOUNT table. But a bank may
choose to make it mandatory in the VERSION

T24 Versions - R17 F-34

 Generate code to reflect the modifications

T24 Versions - R17 F-35

 The modified version is launched by giving the command ACCOUNT,TRG. The
additional features like the defaulted value, noinput field can be seen

T24 Versions - R19 F-36

 The record is authorized on commit as the number of authorisers is zero.
CUSTOMER field cannot be modified as the record is now authorised.

T24 Versions - R19 F-37

T24 Versions - R17 F-38
 Other VERSIONs of the same application can be associated with the current
VERSION in the form of tabs
Add ACCOUNT,JOINT as associated VERSION
ACCOUNT,AUDIT is already added as associated VERSION

T24 Versions - R19 F-39

T24 Versions - R19 F-40
 In the CUSTOMER,AUDIT tab we can see that the
RECORD.STATUS will be INA2 when the record is authorized using
the CUSTOMER,TRG VERSION. When the record is authorized
using the application, the RECORD.STATUS is LIVE. Any
customization we do using the VERSION like Mandatory field,
Noinput field, no.of.approvers is applicable ONLY when the
VERSION is used

T24 Versions - R17 F-41

 Existing VERSIONS can be imported into Design Studio. We can modify the
same if required and redeploy to T24

T24 Versions - R19 F-42

 Right click on folder and choose import screen. Specify the name of the
application and version and click on finish. In some time, the VERSION will be
imported in to Design Studio and can be modified if required.

T24 Versions - R19 F-43

In this lesson we saw, Screen Designer in Design Studio, generating required
artefacts and launching the same in the UXP Browser. We also saw some
additional features of versions such as noinput, nochange, mandatory,
defaulting values and associated versions.