Customisation - local fields

In general, Core Banking applications provide the end user with the necessary fields to store
data pertaining to an application Certain banks may want to record some extra information
which is not catered for standard fields. So then, what would the bank do? Can it request
Temenos to add the new fields to the application to store the extra information? The answer is
No. Temenos might not do that, simply because not all the banks would need that field. Then
what is the solution?

To cater to such situations, Temenos has introduced Local Reference Fields which can be
created in the particular client environment to meet their requirements without affecting the
actual application code.
Local reference fields are
user defined fields and are totally customisable by the end user. Once these local fields are
created, they can be reused in various applications in Core Banking

What?
• Local Fields definition allow the entry of additional user defined fields in existing
• Core Banking applications without any core modification.

Why?
• Client might want to store additional information.
- Can be re-used in various applications.
• Client can define their own local field without a single line of code.

How?
• Local field attributes such as field name, data type, maximum and minimum characters etc.,
are defined in the application LOCAL.TABLE.
• Defined local fields are linked to an T24 application using LOCAL.REF.TABLE.
To create a local field in T24,.
LOCAL. TABLE and LOCAL.REF.TABLE are used

The application LOCAL. TABLE is used to create the user defined field and set properties of
that field.

LOCAL REF.TABLE is used to link the newly created field to any T24 application
The process of creating the field is stand alone and therefore a field created can be reused in
any application in T24.
--------------------------------------------------------------------------------------------------------------------------------------

VERSION
• Customized screens for any application
• Any number of versions per application
• Possible to display or hide the fields in any application depends on the type of contract
• Possible to default value in fields.
• Possible to add local sub routines for field, input authorization and validation
 – Fields used for General Information
• RECORDS.PER.PAGE
• FIELD.PER.LINE
• LANGUAGE.CODE
– Layout of fields to be arranged on the Screen
• FIELD.NO
• COLLUMN
• TEXT
– Operating Conditions
• NO.OF.AUTH
• NOINPUT.FIELD
• NOCHANGE.FIELD
– RECORDS.PER.PAGE
– Indicates whether more than one record may be shown on the same page or not
– Available values are 1 and MULTI
– FIELD.PER.LINE
– Define whether more than one field per line in the version
– Available values are 1 and MULTI
– LANGUAGE.CODE
– Defines the language in which various texts in the version to be displayed.
– HDR
– Used to specify the headings
– FIELD.NO
– Indicate the field name the user wants to define in the version
– For defining remark line use ‘*’ in the FIELD.NO
– Duplication of the field names and numbers not allowed
– ‘*’ value can be duplicated
– Field numbers will be translated to name automatically
– COLUMN
– Indicate in which column the field defined is to start
– If it is left blank , the system will calculate the value
– EXPANSION
– If the value is NO , user will not be able to expand the corresponding multi or sub value
field.
– If the value is NULL , fields can be expanded using ‘>’ symbol
– TEXT.CHAR.MAX
– Total number of characters available for the TEXT field
– TEXT
– Specifies the text, user wants to display for the field defined in FIELD.NO
– ENRICHM.CHAR
– Indicate the number of characters reserved for the display of enrichment
– RIGHT.ADJ.FIELD
– Indicate whether the input portion of the field must be right justified or not.
– REF.NO.IN.1ST.LINE
– Indicate in which line user wants to display the reference number
– ID.AUTOM.SEQU
 – Sequence of record ids which required to be automatically accessed when the version is
invoked
– NO.OF.AUTH
– Number of authorizers required for a contract
– NOINPUT.FIELD
– Specifies the fields that has to be non imputable or not amendable
– NOCHANGE.FIELD
– To define a field as fully protected
– REKEY.FIELD.NO
– Define the fields that has to be rekeyed at the time of authorization
– AUTOM.FIELD.NO
– In conjunction with auto new/old content
– AUTO.OLD.CONTENT
– Field content which is to be changed automatically with the new default value as in auto
new content
– AUTO.NEW.CONTENT
– Defines the new automatic default value
– MANDATORY.FIELD
– To make a field as mandatory
– VALIDATION.FLD
– Specifies the field name to which the validation routine has to be attached
– VALIDATION.RTN
– Name of the user defined sub routine
– D.SLIP.FORMAT
– Defines the deal slip format to be used by the version
– D.SLIP.FUNCTION
– Specifies the function point at which the deal slip has to be produced
– D.SLIP.TRIGGER
– OL – Generate deal slips at points specified by D.SLIP.FUNCTION
– RQ – Generate using a hot key
--------------------------------------------------------------------------------------------------------------------

VERSION ROUTINES

• VALIDATION ROUTINE
– The routine get executed after Enter is pressed from the field where validation routine is
attached.
– Routine attached to VALIDATION.RTN
– PGM.FILE type is ‘S’
• INPUT ROUTINE
– The routine get executed when committing the record in unauthorized stage
– Routine attached to the field INPUT.ROUTINE
– No need to mention in PGM.FILE
• AUTHORIZATION ROUTINE
– Invoked at Authorization stage and normally used to update files.
– Attached to the field AUTH.ROUTINE
– Use Explicit write instead of R.NEW
– AUTO NEW CONTENT ROUTINE
 – Get executed after the ID is entered and records are fetched but before display
– Attached to the field AUTO.NEW.CONTENT
– PGM.FILE type ‘S’
• ID ROUTINE
– The routine is get executed before the record is opened
– Used to do any manipulation to ID
– Attached to the field ID.RTN
– Use COMI instead of ID.NEW
– CHECK RECORD ROUTINE
– The Routine get invoked after the ID is passed but before the record is opened
– Normally used to check the content of records
– Attached to the field CHECK.REC.RTN
• AFTER UNAUTH ROUTINE
– Get executed after the record is written to the $NAU file
– Attached to the field AFTER.UNAU.RTN
– Use F.WRITE instead of R.NEW
– BEFORE UNAUTH ROUTINE
– Get invoked while authorizing an INAU record
– Attached to the field BEFORE.AUTH.RTN
– Don’t use F.WRITE inside the routine, use R.NEW
• Allows more flexibility in creating screens
• Allows user to group a versions of same kind and add functionality to all of them at once.
• The field VERSION.TYPE in the version used to link versions with VERSION.CONTROL
• Id of the VERSION.CONTROL contains the VERSION.TYPE
-------------------------------------------------------------------------------------------
MENUS
• We can launch application, versions or enquiry from MENU
• Menus can be defined in the table HELPTEXT.MENU
• HELPTEXT.MAIN.MENU is similar to HELPTEXT.MENU but used for main menu creation
• It is possible to attach a Menu item in any other menu
• Drop down Menu and Menu explorer
IMPORTANT FIELDS IN MENU
• APPLICATION
– Specifies the Item user want to get invoked while selecting the corresponding option
– Specify the name of the application, version or enquiry
• DESCRIPT
– The field specifies the text to displayed
– Multi value field , display based on the language of the user
• DISPL.APPLICATION
– Value can be ‘N’ or null
– Allows the user to display/suppress the application name against the menu text.
-----------------------------------------------------------------------------------------------------------------------

ENQUIRIES
What can yo do
 Display and sort the data in a number of formats
 Launch an ENQUIRY as context sensitive while working with a related application
 Export ENQUIRY result into a Windows applications.
FIELDS

The basic fields to fill in for an Enquiry are as follows:

File Name
- Main Details tab.
 This is the main file from which most of the data is to be extracted.
 Data can be extracted from each record and presented with data from related
files.

Page Size
- Full View tab.
– This sets the page co-ordinates of the screen.
– As a guide this should be set to 4,19.

Field names - Fixed and Variable

- Data Columns tab.
 This is the name you give for the field you are defining in the Enquiry (Variable name).
 It can be the same name as the field name in the file from which you are extracting the
data, but you can change it if you need to.

Operation

 This defines the Enquiry instruction for this field.

 In a simple example it will be a field name from the file you have selected (Permanent
name).
 However other instructions are also supported.
 A field name will be defaulted into Operation if the Name is a field name on the File.

Column

 This determines the column and optionally the line to display the data.
 If this is not specified the data will not be displayed (used for working fields).
 Columns 0,1 and 2 are used for Drilldown functions (see later) so the first Column
should start at 3.

Mask/Length

This defines the output length and mask, for example 10L for 10 characters, left aligned.
 Make sure that the Column co-ordinates and Lengths add up so that fields do not
overlap.