Scribd
Upload
2K views45 pages

T24 NOFILE Enquiry and Service Guide

This document discusses creating and using nofile enquiries and local applications in T24. It describes how to create a nofile enquiry to display consolidated balance for a customer by accumulating balances from multiple accounts. It also shows how to create a local table definition to define a new "walk-in customer" table and generate APIs to access it. Finally, it provides an example of creating a local application to hold consolidated account balances, and writing a service to update the balances in this local table on a periodic basis.

Uploaded by

cesar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2K views45 pages

T24 NOFILE Enquiry and Service Guide

This document discusses creating and using nofile enquiries and local applications in T24. It describes how to create a nofile enquiry to display consolidated balance for a customer by accumulating balances from multiple accounts. It also shows how to create a local table definition to define a new "walk-in customer" table and generate APIs to access it. Finally, it provides an example of creating a local application to hold consolidated account balances, and writing a service to update the balances in this local table on a periodic basis.

Uploaded by

cesar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Practice – Enquiry Conversion hook

 Create an ENQUIRY TO LIST the LD records that are in foreign currency.


List the ID, CUSTOMER, AMOUNT and Equivalent amount in LCCY.
 Use conversion hook to convert the amount in foreign currency to
LCCY
 Expected output
NOFILE Enquiry
 What if there are multiple files involved in creation of an enquiry?

 What if the record ID of another application is not part of the base


application?

 This can be achieved using NOFILE enquiries

 Since more than one file might be required to extract data, it is a NOFILE
enquiry. We can extract data from any number of T24 applications

 Subroutine is written to extract all required data and form the record

 ENQUIRY application is used to display extracted data


DEMO – NOFILE enquiry
 Create an ENQUIRY to display the consolidated balance for a
CUSTOMER.
 Hint : Accumulate all the balance from all the accounts available in
[Link].
 Expected Output
Step 1 – Create the class
Step 1 – Create the class
Step 2 – Create JAR and update [Link]
Step 3 – [Link]
Creating the ENQUIRY Record
 A valid application name should be given in the field
[Link] which is checked against [Link]
 A NOFILE enquiry does not have a single associated file
 Create a record in [Link] with NOFILE
prefix for the ID e.g. [Link]
 This ID should be given in [Link] in the ENQUIRY
application
NOFILE Enquiry - [Link]

Selection
Field

Field
created by ID of the
the routine [Link]
NoFile Enquiry - ENQUIRY
NoFile Enquiry – Execution
NoFile Enquiry – OUTPUT
Lesson 4. SERVICE Hooks in
Java

T24 Extensibility in Java


Services in T24
 Multithreaded processes
 Can be run independently or as part of COB

LOAD SELECT RECORD

 Must implement [Link]


 Equivalent of
LOAD – initialize()
SELECT – getIds() or getTableName()
RECORD – inputRecord() or process()
DEMO- Service
 Simple service that updates the [Link] of CUSTOMERS in SECTOR
1001 as TEST + existing MNEMONIC

 EXPECTED OUTPUT
1. Create the class

Export JAR and


restart jBoss
2. Create the [Link] records
3. Create the [Link], BATCH & [Link] records
4. Run the TSM and TSA
 When the
service is run,
we can see the
[Link] is
updated
Lesson 5. Local APPLICATION

T24 Extensibility in Java


DEMO Creating Local Application
 We can create a new application using [Link]. OVERRIDE
must be raised if the phone / email is used by existing customer
[Link] [Link]

PRODUCT ST @ID, OVERRIDE, AUDIT


[Link] H fields are added
automatically
CLASSIFICATION CUS

Field Name Data Type Remarks


NAME A
Raise override if this PHONE is
PHONE
available in CUSTOMER
Raise override if this EMAIL is
EMAIL available in CUSTOMER
1. Creating the TABLE – [Link]
 Create the table using
[Link]
 ETD creates the required
artefacts – [Link],
[Link],
[Link], DATA
FILES
2. Generate the API for the new Table
 Using Design Studio, we can generate the API for the APPLICATION
created using [Link]
 we need a server project – to establish connection with T24
 We need a models project – to import the application from T24
2a. Create the –DataTool project
 Creating the server project
 FileNewProject
2b. Create the DS-DataTool Project
 Create the DS-DataTool project
2c. Import the Local Application
2d. Generate the API for the new Table
 Toggle the DS project as a TAFJ project
 Right click on projectDesign StudioGenerate T24 API
Give the location and name
of the jar
2e. Update [Link] and Build path

 Update [Link] and restart jBoss

 Add jar to the java Build path in DS


3. Create the class
4. Create the [Link], VERSION
5. Launch the VERSION
Using [Link]
Using [Link]
Practice – Service and Local Application
 Create a local application to hold the consolidated account balance
of CUSTOMERS.
 Write a service to update the balance
Local Table

Lesson - 6
DEMO Creating Local Table
 Create a local field called [Link]
 Attach field to CUSTOMER
 The local field gets its values from a LOCAL APPLICATION
 Use version to input hobbies for authorized CUSTOMER
 Minimum of 3 hobbies must be input
1. Creating the Local Application
 Create local application [Link] and input few records
2. Create [Link] called [Link]
3. Add the [Link] to CUSTOMER
4. Create the class

Create class , Export


JAR and restart jBoss
5. Create the [Link] records
6. Create/Modify version
 Create the version CUSTOMER,HOBBY in DS and generate code. Modify
the VERSION and add the hooks
Launching the VERSION
Course Summary
 We have seen
 Need for T24 Extensibility
 T types
 How to attach VERSION hooks
 Attaching Enquiry hooks
 Creating and executing a multi threaded SERVICE
 Creating a local table using [Link] and customizing the
application
 How to debug the Java code
[Link] [Link]

Common questions

Powered by AI

EB.TABLE.DEFINITION in T24 is crucial for creating new applications as it automates the creation of artefacts needed for the application, such as PGM.FILE, FILE.CONTROL, and DATA FILES. It also facilitates integrating new applications with T24 by allowing API generation through Design Studio, ensuring consistent application behavior and integration .

Creating and using a local table in T24 involves several steps: first, create the table using EB.TABLE.DEFINITION, which generates necessary artefacts like PGM.FILE and STANDARD.SELECTION. Next, generate the API using Design Studio and set up a server project to connect with T24. Create a class and EB.API records, then create or modify a VERSION to include the local table in the application. Finally, launch the version to manage customer data with features like adding hobbies fields .

To handle multiple file extraction in T24 without associating a single application file, a NOFILE enquiry can be used. This approach allows data extraction from any number of T24 applications. A subroutine is written to extract the required data and form the record, which the ENQUIRY application then displays .

Updating a customer's local application field in T24 requires creating a local application (e.g., CUS.HOBBIES) and inputting data records. This involves adding the local table to the CUSTOMER application, creating a class, exporting JAR, and configuring EB.API records. A VERSION for inputting the fields must be modified with hooks to manage data entry. These configurations facilitate the management and update of customer-specific fields .

The NOFILE enquiry application enhances data extraction capabilities in T24 by allowing the extraction of data from multiple T24 applications without being tied to a single file. This flexibility is achieved by writing a subroutine to gather the needed data across different applications and displaying the results through the ENQUIRY application. This approach supports complex data requirements and system integration .

Generating the API for a new table in T24 involves creating a server project in Design Studio to connect with T24 and a models project to import the application. Next, toggle the DS project as a TAFJ project, generate the T24 API, and provide the location and jar name. Finally, update the module.xml and build path, and restart jBoss to complete the setup .

A challenge in T24 is creating enquiries involving record IDs not part of the base application. The solution is using a NOFILE enquiry, which doesn't rely on a single file and allows data retrieval from multiple applications. This flexibility is supported by creating a subroutine to extract and format data, enabling comprehensive data enquiries across various records .

When creating a version for customer hobby entries in T24, considerations include ensuring that the local field, such as CUS.HOBBIES, is attached to the CUSTOMER application. The version must allow for the input of a minimum of three hobbies to authorize a customer. Proper hooks should be added for validation and processing, and the API and JAR configurations should be up-to-date for seamless integration and functionality .

T24 supports multithreaded processes through the implementation of ServiceLifecycle functions like initialize(), getIds(), and process(). This allows services to run independently or as part of COB services in T24. Benefits include improved processing efficiency, faster execution times, and the ability to handle multiple tasks concurrently, enhancing overall system performance .

In T24, updating customer information using a service hook involves implementing the ServiceLifecycle interface from com.temenos.t24.api.hook.system. A simple service updates the SHORT.NAME of customers in SECTOR 1001 by appending 'TEST' to the existing mnemonic. This involves creating a class, exporting a JAR, and restarting jBoss. EB.API records, PGM.FILE, BATCH, and TSA.SERVICE records are also created to run the TSM and TSA .

You might also like