Click to edit Master text styles

Second level
VERSIONS
Third level
OBJECTIVE

Objectives of the course are to

• Introduce the concept of Versions
• Version application and the use of important fields
• Version Designer
• Version Control

2
COURSE AGENDA

SESSION I SESSION II
• Introduction to Versions • Version Designer
• VERSION application

BREAK

SESSION III SESSION IV

• Version.Control • Work shop
• Review and Summary

3
INTRODUCTION

4
INTRODUCTION

• It is rare for any client to use the main screen input for all T24
applications as it contains many fields.
• It is necessary to customize screens as per requirement.
• VERSION is a standard T24 application allows creation of
customised screens for input, display etc.
• T24 is supplied with some standard Versions also.

5
FEATURES

• To customize the screens as per the client requirement 

• Each application can have multiple versions.
• Example: Customer Application has so many fields which the Client
would not require. In that case we would give only the required
fields to the Client so as to make it very easy and meaningful to the
client.
• Facility provided to attach user defined subroutines to add more
functionality.
• Versions can be created in two different ways
– Screen Designer
– Version Application

6
VERSION

7
VERSION

• Customised screens can be created using ‘VERSION’ application.

• Record id to this application contains two elements separated by ‘,’

APPLICATION , VERSION NAME

• Example:
– CUSTOMER,LOCAL
– CUSTOMER,FOREIGN

• Multiple versions can be created for each application

8
VERSION FIELDS

• (1)PRINT ONLY :
– indicates whether the version created is for printing purpose or for
online screen.
– Not used in Desktop. It is used only in Classic mode. 
• (2)RECORDS PER PAGE :
– indicates how many records are to be displayed in a page.
– The default is set to 1. 
• (3)FIELDS PER LINE :
– Single:
• allows only one field in a line
– Multi:
• allows multiple fields to be displayed in a line. 

9
VERSION FIELDS

 (5-12)HEADER:
 5 – 12 fields are used for headers.
 Heading can be given in two lines.
 Each line is divided into four sections. 1 – 39, 40 – 78, 79 – 117, 118 –
132.

10
VERSION FIELDS

• (13.1)FIELD NO:
– Field number or field name from the actual application or the field name can be
entered.
– For eg. If MNEMONIC from Customer Application is to be entered then the user
can type 1 in this field.
– Add text or blank lines by entering the ‘*’ symbol

• (14.1)COLUMN:
– Indicates the column starting position of this field .

• (15.1)EXPANSION:
– Indicate whether the field multi value field or not.
– Default value is ‘YES’ if a field is a Multi valued field which allows expansion.
– If set to ‘NO’ expansion not allowed.

11
VERSION FIELDS

• (16.1)TEXT CHAR MAX:

– Maximum Characters allowed for that particular field.
• (17-20)TEXT FIELDS:
– Field label text
– Sub values for different languages
• (21)ENRICHM.CHAR:
– Number of characters of enrichment to be displayed
• (46)NO.OF. AUTH:
– 0 Then inputter and authoriser can be the same.
– 1 Inputter and authoriser cannot be the same.
– 2 second level authorisation required.

12
VERSION FIELDS

• (67)GB DESCRIPTION :
– Used For The Description for the version
• (68)ASSOC VERSION :
– Allows data to be split across different screens:
– i.e. deal details, settlement instructions, audit information
– Different version of the same application can be attached into a single
one.
– Control can be switched using ALT C
• (69)NEXT VERSION:
– Initiating another application into one application on authorization.
– Account,TEST1 I F3 which launches Account application on
authorization of customer.

13
 VERSION - LAYOUT

Version Title Associated Version

Field Label Enrichment

14
VERSION FIELDS

• Multi-value set of fields 50-52 allow automatic field content to be

defaulted
• (50)AUTOM.FIELD.NO :
– Field to be controlled

• (51)AUT.OLD.CONTENT : (optional)
– Old value to be changed.
– Remains blank for default input on a new record of value defined in
field 52

• (52)AUT.NEW.CONTENT :
– New value to be swapped for old value or default if field 51 is blank

15
VERSION FIELDS

• (47)NO INPUT.FIELD :
– Prevents input to data fields

• (48)NO CHANGE.FIELD :
– Prevents Users changing values

• (49)RE-KEY.FIELD.NO :
– Forces re-input of a field at authorisation
– Original and Re-Key values validated

16
VERSIONS FOR AUTHORISING

• To use a Version for Authorisation, the field “OVERRIDE” must be

included, if access to the Full Application is not given.
• This ensures that an Authoriser has viewed all override messages
that are generated

17
VERSION DESIGNER

18
GRAPHICAL SCREEN DESIGNER

SCREEN DESIGNER
• Select ‘Tools’ and choose ‘Screen Designer’ from the Menu
• Enter the name of the Version to be created and then press Enter.
• Click the Button ’Toggle Screen Designer’ from the TOOL BAR so that
the blank screen will be displayed
• Click ‘Show a list of fields’ button from the TOOL BAR so that all the
fields of that particular application will be listed which will enable us to
design the screen easier by dragging all the necessary fields from the lists
• Once the fields has been selected the user can resize the fields, change
field descriptions or the enrichments.
• To change the field description, right click on the field and select properties.
• Press F5 to commit.

19
USER PROFILE

• We can restrict the user to use only version

• The screenshot shows that user is allowed Input Customer record
thro CUSTOMER,CLIENT version only

20
VERSION.CONTROL

21
VERSION.CONTROL

• Application allows default properties (routines) to be applied for

Multiple versions.
• Record id is a Valid application.
– Example : CUSTOMER

• Field EXC.INC.RTN (Field no 73) in Version application should be set

to ‘YES’ to enable this facility for the particular version.

22
WORK SHOP

• Create New CUSTOMER Version with all Mandatory Fields with Zero
authorisation.
• Default the Nationality and Residence as ‘Nigeria’ and make these
fields as No inputtable.
• Create a new ACCOUNT version with all Mandatory fields using
Designer.
• Default value of Category with a value ‘1001’ and Currency ‘USD’
and make these fields as No Change field
• Launch created Account version whenever a record is authorised
through created Customer version.

23
SUMMARY

Now you should understand,

• How to create GLOBUS Versions using the Version application
• To create a Version the Screen Designer
• Importance of Version.Control application

24
 THANKS

© 2006 Datasoft Systems Bangladesh Limited. All rights reserved.

25