Sample Presentation

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 13

T24 L3 JAVA TRAINING

TEMENOS T24 / TRANSACT


1. Versions And Enquiries
 ACCOUNT
 CUSTOMER
 FUNDS.TRANSFER
We can create the Version for all the Customer, Account ,
Funds.transfer
CREATED AN VERSION FOR THE ACCOUNT AND FUNDS TRANSFER
WE CAN GIVE DEFAULT VALUES BY GIVING AUTM FIELD
,DEFAULT FIELD,NO CHANGE FIELD
 AND THE ENQUIRIES FOR ALL THE ROUTINES CAN BE CREATED TO FILTER THE DATA AND ALSO
BASED ON THE FIXED SELECTION FIELDS TO RETRIEVE THE DATA

QUERYING THE DATA BASED ON FILTER CRITERIA DISPLAYS THE LIVE DATA IF IT MATCHES THE SEARCH

FINDING ALL DISPLAYS ALL THE LIVE RECORDS

WE PASS THE ENQUIRY AND THE SELECTION CRITERIA TO SEE THE ENQUIRY
RECORD LIFE CYCLE
 Record Status (INAU,IHLD,RNAU, RNA2, INAO, HNAU, REVE)

 After the Authorize the record Status is live


 After Amending the curr.no changes and after commit the new one is live
and the Previous goes to History

 The live Record can be Reversed and goes to history and can be restored
from history to live.
ROUTINES AVAILABLE FOR VERSION AND ENQUIRY
 ID ROUTINE - checkId
 INPUT ROUTINE - validateRecord
 CHECK RECORD ROUTINE - defaultFieldValues
 FIELD VALIDATION ROUTINE - validateField
 BEFORE AUTH - updateCoreRecord,updateLookupTable,updateRecord
 AFTER UNAUTH - updateLookupTable
 AUTH ROUTINE - postUpdateRequest,getServiceControlDetail

Each version routine extends RecordLifeCycle and provides the


followingImplementation Methods
WE CREATE AN EB.API, WITH THE IMPLEMENTATION
METHOD AND CLASS AND USE THE
EB.API AS THE ROUTINE NAME
 Id routine – To ckeck the validation routine on id based on the condition
provided in java

 Input Routine – Used to validate Multiple input Fields if not SetError and return
getValidationresponse()

 Field Validation – This routine validates the fields and provides the Response

 Check routine – Provide the default input values

 Before Auth –before auth if we want to show any messages based on routine
 After Unauth –the record moves to live but shows the errors
 Auth routine – creates the duplicate with the given data
ENQUIRY ROUTINES
- BUILD ROUTINE
- CONVERSION ROUTINE
- NOFILE ENQUIRY

BELOW SHOWS THE NOFILE ENQUIRY


FINANCIAL FILES
 Customer Files
 These are Shared among The Branches
 Financial Files
 These are Not shared among the Companies
 Installation File
COMPOSITE SCREEN AND TABBED SCREEN
-- COMPOSITE SCREEN ALLOWS TO CUSTOMIZE AND CREATE OUR OWN DESIGN OF
SCREEN WITH MENU ,ENQUIRY AND VERSIONS

-- IN COMPOSITE SCREEN CHANGING THE TABS DATA WONT BE LOST COMPARED TO


TABBED SCREEN

-- IN TABBED SCREEN WE CREATE ASSOCIATED TABS

Composite Screen Tabbed Screen


CREATING OUR OWN TEMPLATE
 We have to Fetch by the Template Application by Name and Generate the
Jar
file for our User defined Application

 We Can Use the fields By creating our Application class And use the fields
to Edit the Data.
Multi Threaded Process
 We have three Different Process Load , Select and Process

 With Select we Implement getIds Method to fetch the Data from DB

 And InputRecord to read all the Individual data


 Create two EB.API for Select and Process
 And PGM.FILE ,BATCH and TSA.SERVICE to start and Stop the Service
TAFJEE
 Tdiag – System parameters
 Como – The logs that are gets stored when a service is
run

You might also like