User Guide TEMENOS T24 Template Programming PDF

Preview

Summary

TEMENOS T24 Template Programming User Guide Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings N...

Description

TEMENOS T24 Template Programming

User Guide

Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV. Copyright 2005 TEMENOS Holdings NV. All rights reserved.

Template Programming

Table of Contents Introduction.............................................................................................................................................. 4 Application Overview ........................................................................................................................... 4 Application Environment ...................................................................................................................... 4 Terminology...................................................................................................................................... 4 The Structure.................................................................................................................................... 5 Screen Management ........................................................................................................................ 5 Data Entry Functions........................................................................................................................ 5 Security Management ...................................................................................................................... 6 Validation.......................................................................................................................................... 6 Main File Maintenance ..................................................................................................................... 6 History Maintenance......................................................................................................................... 6 Transaction Journaling and System Recovery ................................................................................ 7 Multi Level Processing ..................................................................................................................... 7 Multi Company Processing .............................................................................................................. 7 Audit Trail ......................................................................................................................................... 7 Close of Business Processing.......................................................................................................... 8 Writing an Application Program ........................................................................................................... 8 Defining the File ............................................................................................................................... 8 Create the file ................................................................................................................................... 9 Application Template...................................................................................................................... 10 Template Type ............................................................................................................................... 10 Description ..................................................................................................................................... 11 Modifications .................................................................................................................................. 11 Inserts............................................................................................................................................. 11 Program Flow ................................................................................................................................. 11 Tailoring the Application Program...................................................................................................... 15 Define Parameters ......................................................................................................................... 15 INITIALISE ..................................................................................................................................... 21 CHECK.FUNCTION ....................................................................................................................... 21 CHECK.ID ...................................................................................................................................... 22 CHECK.RECORD .......................................................................................................................... 22 CHECK.FIELDS ............................................................................................................................. 22 CHECK.DELETE............................................................................................................................ 23 CHECK.REVERSAL....................................................................................................................... 23 CROSS.VALIDATION .................................................................................................................... 23 BEFORE.UNAU.WRITE................................................................................................................. 24

TEMENOS T24 User Guide

Page 2 of 40

Template Programming

AFTER.UNAU.WRITE.................................................................................................................... 24 BEFORE.AUTH.WRITE ................................................................................................................. 24 AFTER.AUTH.WRITE .................................................................................................................... 25 Template Programs ........................................................................................................................... 25 TEMPLATE .................................................................................................................................... 25 TEMPLATE.L ................................................................................................................................. 31 TEMPLATE.T ................................................................................................................................. 33 TEMPLATE.W ................................................................................................................................ 35

TEMENOS T24 User Guide

Page 3 of 40

Template Programming

Introduction

Application Overview The T24 system for data entry is based on a one to one relationship between the data fields on the screen and the data fields in a file. The only way to enter data into T24 is via an APPLICATION PROGRAM which records the data entered and stores it in an associated file, field by field.

There are three types of application program:

Input allows the full functionality of T24: data entry, authorisation, deletion, history restore etc.

Display Only is used to simply view the data on a file maintained by the system rather than the user.

Utility allows data entry and a Verification function which initiates a process. An example of this would be ENQUIRY.REPORT which records the selection criteria for an enquiry and then on Verification builds a report and spools it.

This section describes the underlying systems which support this functionality and details the procedure to follow and develop a T24 application program.

Application Environment Terminology Term

Description

Product

The collective term for all programs and data files that constitute a T24 implementation. For example, Funds Transfer, Foreign Exchange.

Application

An program or subroutine that allows data entry into a T24 file, e.g. CUSTOMER, FOREX etc. A product will consist of many applications.

Subroutine

A routine invoked by an application program or close of business process, i.e. not directly executable by the user.

Structure

The main supporting sub-system for an application. It manages screen input, security (SMS), file updates etc.

TEMENOS T24 User Guide

Page 4 of 40

Template Programming

Live file

The file which holds authorised data.

Unauthorised file

The file which holds unauthorised data.

History file

The file which contains copies of previously authorised data.

Concat file

A file which is used as an alternate index to a live file.

Figure 1. - Terminology details

The Structure The application management system (the 'Structure') handles all screen display, data input, simple field validation and master file updates. Therefore applications can be written by just defining their specific file layouts, specialised validation and external file maintenance.

This is achieved by inserting field definitions, validation etc. into a coding TEMPLATE which contains the necessary triggers to invoke the core system.

Screen Management One of the most important aspects of the structure is its screen management capability. Once the application has defined the input fields for the transaction, the structure will present a standard screen for input, display, authorisation, history comparison etc. It will also handle field positioning, page manipulation, data formatting, input enrichment etc. which means that whilst the applications may differ dramatically, the user will always be presented with a standard mechanism for entry or data manipulation. However, this does not mean that the user is constrained to one design of entry screen. The structure also allows a 'version' of the screen to be defined without any coding changes necessary at the application end (see the Version System Administration Guide). The data is presented both in ‘classic’ text based screens and in T24 Browser: neither type of display requires modifications to the application program.

Data Entry Functions The structure provides all the necessary transaction processing functions necessary to complete an application.

•

Input a record

•

Modify an existing record

•

Display a record

•

Delete a record

•

Copy a record

•

Authorise a record

•

Reverse an authorised record

•

Compare history records

•

Restore a record from history

•

List all or a selection of records

TEMENOS T24 User Guide

Page 5 of 40

Template Programming

In the simplest case, to achieve this functionality the programmer would simply have to enter the field definitions. For more complicated processing the programmer inserts the specialised code necessary for authorisation, deletion etc. in the relevant position in the template.

Security Management The structure provides two important aspects of security management:

•

Access restriction

•

Activity logging

System access can be controlled on four levels: system sign-on (including time restrictions), entry to applications and data records, restricting functionality (e.g. allowing display only) and defining the field values with can be entered (e.g. amount < 10,000).

Logging can be specified from simply recording sign on/off times to recording every access the user makes.

The application program requires no special code to achieve this functionality. See the Security Management System Administration Guide for more details.

Validation Input validation can be specified with the field definitions and hence the structure will check the data entered. The validation available is comprehensive, offering simple checks such as numeric/non-numeric input, to complicated date and amount edit checks. Input can also be verified against an existing table as well as being passed to an application specific routine.

To allow maximum flexibility, the structure can pass control back to the application for further validation at any stage. The template also contains sections for further validation on completion of input (crossvalidation), authorisation, deletion etc.

Main File Maintenance The structure in addition to controlling the transaction input also controls the update of the main transaction file. In this way it can maintain both authorised and unauthorised versions of a record and keep a log of the last user to input/change the data (this it stores in the data record itself).

History Maintenance As an extension of the main file update procedure, the structure will optionally maintain a history of all changes made to the application records. The user will then have the ability to 'walk through' the history file examining every change as it occurred and even restore the last record from history in the case of accidental reversal.

TEMENOS T24 User Guide

Page 6 of 40

Template Programming

Transaction Journaling and System Recovery The recovery system is based on jBASE transaction management. The physical updates to the database files do not take place until the end of the transaction, i.e. after the commit transaction is performed. It is possible to use the JOURNAL file to store information pertaining to all the writes that occur during transactions input. By default this information is not captured and has to be setup by using the SPF application and setting the field INFO.JOURNAL to Y. To roll back logically within a transaction, due to a program bug or operator override, the procedure has to abort the current transaction and return to the start of the transaction (id input or whatever). This is possible because no updates have actually taken place. This is done automatically; special coding is not required for it. Another advantage of this mechanism is any application errors that cause a program to abort and would normally involve a system restore/roll forward, can be ignored in terms of data integrity.

See the Backup, Restore and Recovery System Administration Guide.

Multi Level Processing A unique feature within the structure enables the user to leave the current transaction, invoke a table lookup or similar process, and then return to the original transaction at the exact point of departure. Additionally the data that was being examined in the table can be inserted into the transaction input field. When operating under T24 Browser this mechanism is used extensively allowing the user to run enquiries, view reports, browse help etc. whilst still in data entry mode.

Multi Company Processing The structure incorporates the concept of multi-company processing whereby branches (or any 'legal vehicle') operating on the system can share certain data files (customer files, tables etc.) whilst still controlling their own financial files. The rules to determine which files can be shared are defined by the application programmer when creating the application, the user can determine the company structure i.e. who shares what.

All files accessed by the system are opened by a standard procedure which, using the rules and existing company structure, determines which disk file should be opened. Hence multiple companies can be set up without modifications to the application code.

Audit Trail All main file updates are 'stamped' by the structure with the name of the inputter and authoriser, date-time, terminal number, company code etc. to provide a comprehensive audit trail. If history is maintained then the audit trail will be carried in the history records as well, providing a log of every update performed.

TEMENOS T24 User Guide

Page 7 of 40

Template Programming

Close of Business Processing A batch system is provided to control all Close of Business processing. It provides the operator with a controlled environment which handles job scheduling/frequency/ dependency, report routing etc.

Applications can define Close of Business processes (routines and/or operating system commands), which are incorporated into a ‘command stream’, executed by the operator. The environments (company processing details etc.) are initialised by the batch control system so that application programs can be written independently of site configuration.

Writing an Application Program This section describes the necessary steps to writing an application program.

Defining the File Determine the name of the file. It must be meaningful; the name of your file will be the same as the name of your application program, hence do not call it FILE001 or SC007. It should give some indication as to its purpose e.g. CUSTOMER, FUNDS.TRANSFER etc. Note: The file name cannot exceed 25 characters, to allow for the addition of the company mnemonic and the $NAU or $HIS suffix.

Enter the details of the file into the application FILE.CONTROL (in T24). NOTE: Currently this program is only available to the Temenos Development group – other programmers must create the records using the jBASE editor (JED).

Field

Details

DESCRIPTION

What the file will be used for.

PRODUCT

The product code to which it belongs. Use EB until a product code is allocated for client specific developments.

SUFFIXES

Dependent on the application type, for standard applications that require authorisation and have a history the field should be multi-valued and contain $NAU & $HIS. For live files, which have no user input, the field should be blank.

FILE TYPE

jBASE file type.

FILE MODULO

jBASE file modulo.

CLASSIFICATION

File classification; INT – Installation CUS – Customer CST – Customer table FIN – Financial FTD – Financial Table Descriptive FTF – Financial Table Financial CCY – Currency

TEMENOS T24 User Guide

Page 8 of 40

Template Programming

NOS – Nostro SYS.CLEAR.FILES

Y if the file is to be cleared when financial data is cleared.

CUS.CLEAR.FILES

Y if the file is to be cleared when customer data is cleared.

Figure 2. - Field details Select one of the following (the others are for T24 CORE use only).

Classification

Details

INT

Installation - This covers files like COMPANY, USER, LANGUAGE, where only one version of the file will exist regardless of the number of companies

CUS

Customer - for files where the data can be shared between companies. Primarily static information and tables.

FIN

Financial - for files that hold financial level details (amounts, balances etc.) where the data cannot be shared with other companies.

Figure 1. - Classification details

Create the file To create the file run CREATE.FILES at the awaiting application prompt in T24. It will prompt you for:

1.

The company you wish to create the file in (use the current company for installation level files). Use the COMPANY mnemonic as from the correct COMPANY record.

2.

The name of a select list. If you have a number of files to create you may have a select list containing the name of the files, just return...