Welcome to T24 Deal Slip Course

1
2
3
4
An important aspect of all banking transactions is the proof that it happened. To a lay
man this proof could be a simple print out that gives him details of his last transaction.
Deal Slip
-Peter decides to open an account in the bank. He has submitted all the documents
required to open an account and wants a status update.
-Once the account has been created, Peter will be issued with a Deal slip as a
confirmation.
Therefore a deal slip
1.1 Can be generated for any application
1.2 Can be generated during any of the functions i.e., Input, Authorise, Copy, Delete
etc)
1.3 Can be generated only online
.4 Is normally printed and handed over to the customer across the counter

5
Deal slips can be generated for any application in T24.

Usually printed over the counter and given to the customers

They act as a confirmation for a banking transaction that was performed

6
A Deal can be triggered during any of the following functions in T24:

Authorize
Copy
Delete
History Restore
Input
Reverse

FINISH ( This keyword is Application specific and is not triggered for all
applications. The Application that currently uses it is TELLER )

7
8
PRINTER.ID, DE.FORM.TYPE, REPORT.CONTROL and DEAL.SLIP.FORMAT
applications in T24 constitute the application involved in creating dealslips in T24.
All these applications are interlinked to produce the final deal slip.

9
PRINTER.ID, DE.FORM.TYPE, REPORT.CONTROL and DEAL.SLIP.FORMAT
applications in T24 constitute the application involved in creating dealslips in T24.
All these applications are interlinked to produce the final deal slip.

10
11
The PRINTER.ID application is the one links T24 to the formqueue that is
created at the jBASE level.
Now, what is a formqueue?
I am sure all of you would have used the ‘Add Printer’ icon in Windows to
add a network printer. What happens is, you get a logical printer set up in
your system that takes care of routing the print request received from
applications to the operating system. I am sure you know that no
application or a database prints. They all send the requests to operating
system and it is the operating system that prints.
A formqueue is like a logical printer. It is defined at the jBASE level. It
redirects print requests received from T24 (Application) to the operating
system.
The field ‘Prime Printer Id’ holds the name of the jBASE level formqueue.

Incase you do not want to print but send the output to a repository called
&HOLD&, then, set the value of the field Prime Printer Id to HOLD.

12
&HOLD& : The &HOLD& directory is a directory that gets installed when
T24 is installed. Take a look at the VOC entry displayed above. You will be
able to understand that this directory resides under the bnk.data/eb
directory. This directory, as the name suggests is meant to hold any (Not
only deal slips) spooled output which may not be required to be printed.
The advantage of storing it in this directory is that we can query the
content of this directory and reprint any of the reports whenever we wish
to. Take a look at the output of the ‘LIST &HOLD& command. As you can
see above, all the reports that get spooled into this directory have a
unique ID to identify themselves. I am sure we cant remember these
numbers. Can you? ☺
Take a look at the content of the bnk.data/eb sub directory. Note that the
&HOLD& is a directory or in other words a jBASE non hashed file. This
brings us to the question, will all reports that get spooled to this directory
be stored as flat files. The answer is YES. All reports that get spooled to
this directory will be stored as individual flat files. If they are flat files, how
do we view them? Well, we could do a JED and view them (See output of
JED <Report ID> above).
I am sure you are not happy with JEDing a file (We seem to read your
mind ☺ )
Well, there is no harm in JEDing a report to view, but the issue is, when
we have a 1000 records in this directory and we wish to reprint one of
them, how on earth are we going to locate the report that we wish to
reprint?

13
Keep thinking.

13
Since &HOLD& is a flat file and only stores the reports and does not
enable querying, an application named HOLD.CONTROL is used.
When ever a report is spooled into the &HOLD& directory, details about
the report such as
1. The name of the user who generated the report – Field USER in
HOLD.CONTROL
2. The name of the report (As in REPORT.CONTROL) – Field
REPORT.NAME in HOLD.CONTROL
3. The company for which the report was generated – Field COMPANY.ID
in HOLD.CONTROL
4. The date when the report was generated – Field DATE in
HOLD.CONTROL
5. Time when the report was generated – Field TIME in HOLD.CONTROL
6. Was it generated during COB or online – Field RUN IN BATCH in
HOLD.CONTROL (If set to Y, denotes that it is a COB report)
7. The date and time of COB if it is a COB report that has been generated
– Field BATCH DATE TIME in HOLD.CONTROL
8. The T24 application server date – Field BANK DATE in
HOLD.CONTROL

Are stored in a record in HOLD.CONTROL application. The ID to this

record will be the ID of the report in &HOLD&.
Please note that the HOLD.CONTROL application only holds details of the
report mentioned above along with the actual report ID. It does not
store the actual report. The actual report will only be stored in
&HOLD&.
You may verify the record in HOLD.CONTROL to view the report from
&HOLD&. So, you don’t have to JED the report any more ☺

14
15
Now that we have learnt about setting up the PRINTER.ID in T24 we
move on to another application called DE.FORM.TYPE. This application is
used to design the form on which your deal slip should appear. Will you
not agree with me when I say all the things that need to be printed are
always on a the same type of stationery. There are different forms of
stationery you could think of in a banking transaction. An account
statement is an ideal example of a banking transaction which is printed
and sent to all customers on an A4 paper, whereas a cheque would be on
a form which is rectangular unlike an account statement. Now this is what
we call a form and you can design the same using the application
DE.FORM.TYPE in T24.

There are fields that you can use to alter the layout of the forms you want
to print on. We can change the forms width and depth for instance, also
have some space for top and bottom margin.

The OPTIONS field allows you to define some spooler options

• NOHEAD – Suppress printing of banner page

• NOEJECT – Suppress the page from ejecting at the end of the report
• COPIES n – To print n copies of the report
• DEFER hh:mm – To defer printing until the specified time (24hr time) Eg,
18:00 for 6pm.

Note that the record created in the PRINTER.ID application (with ID

16
HOLD) is specified here.

16
17
REPORT.CONTROL is the application that links the printer related
applications in T24 such as PRINTER.ID and DE.FORM.TYPE to rest of
the applications in T24. All applications in T24 that wish to print will speak
to DE.FORM.TYPE and therefore to PRINTER.ID using this application.
Note that the ID of the DE.FORM.TYPE record that was created earlier
has been specified here in the field ‘Form Name’.

18
19
When ever a new customer walks in to the bank, in T24 we would have to
create a record in the CUSTOMER application to record his details.
Once the details are recorded, the bank wishes to give the customer a
confirmation note like the one shown below

20
The Id of the REPORT.CONTROL application can be any free text which
you think best describes the reason for which you are creating the deal
slip
Report Control Id : Holds the ID of the record in the REPORT.CONTROL
application. This enables us to link to the DE.FORM.TYPE application and
the DE.FORM.TYPE application enables us to link to the PRINTER.ID
application in T24
File : Holds the name of the T24 application form which data needs to be
fetched and displayed here. Similar to the field ‘FILE NAME’ in the
ENQUIRY application. This is a multi value field and hence multiple T24
application names can be specified here. The main application always
should be the specified in the first multi value.
Id : Holds the name of the field that acts as the ID for the application
mentioned in the field ‘File’. Look at the second multi value set
‘File.2:COUNTRY and Id.2:NATIONALITY’. What this denotes is, we are
to pick up data from the application called COUNTRY and the field that
links the COUNTRY application to the CUSTOMER application (The base
application which the deal slip is based on) is the field NATIONALITY.

21
Field : Anything that need to be displayed as it is, should be enclosed within the
quotes. If you want the value from the application record to be displayed, then it
should be a valid field name from the application defined in the field FILE.
Column : Column, Row where the data needs to be displayed

22
Accessing fields from other Applications (not the main file).
COUNTRY.NAME is a field in COUNTRY application
Syntax : Application>FieldName

23
24
Now that we have created the necessary records in various application
like PRINTER.ID , DE.FORM.TYPE , REPORT.CONTROL ,
DEAL.SLIP.FORMAT we need to generate the deal slip from some
application in T24. Deal slips, as you know, can be triggered from any
application in T24 on any function. To achieve this, define a version for the
application and attach the deal slip to it and set a trigger for it to print. Lets
see what are the fields that are available in VERSION application to set up
a deal slip.

25
D.SLIP.FORMAT is where you attach the name of the
DEAL.SLIP.FORMAT record
D.SLIP.FUNCTION is where you specify what is the function in T24 that
should trigger the deal slip ( I , A , R, C, D, H and FINISH)
D.SLIP.TRIGGER can be either OL or RQ. OL is to generate a deal slip
based on the function defined in D.SLIP.FUNCTION and RQ to generate it
using a hot key. We don’t use the hot key functionality any more.

26
27
The printing of deal slip reports is controlled via the following
applications: BROWSER.PREFERENCES.
BROWSER.PREFERENCES
The BROWSER.PREFERENCES application has a record for each of the
users. To access the record, the user needs to select the ‘Amend
preferences’ tool from the Tools menu page.

28
For Automatic, Local printing, the user would change the print location
field in the users BROWSER.PREFERENCES to LOCAL.

29
On committing a deal with the function I, a deal slip will automatically be printed.
This will display the report generated along with the user’s local
print selection screen, which will enable the user to print the report to a local
printer.

30
31
For Automatic, Local printing, the user would change the print location
field in the users BROWSER.PREFERENCES to SERVER.
The three fields in the version are set as follows.

32
On submitting the deal, the deal slip will be printed automatically. The user will
then receive a transaction complete message with the ID of the deal
slip generated on the server.

33
34
For Hot key, local printing, the user would change the print location field
in the users BROWSER.PREFERENCES record to LOCAL.
The 3 critical fields in version are set as follows:
Field Content Required
D.SLIP.FORMAT TELLER.SLIP.INPUT
D.SLIP.FUNCTION I
D.SLIP.TRIGGER RQ

At present, hot key, local printing only works for the function I so set the
field D.SLIP.FUNCTION to I.

35
When the trigger is set to RQ, then the deal slip print icon will be available at all
times within this version record. When the deal slip print icon is
selected, a request will be sent to the server to generate a report. The function
passed down to the server is always I.
The report will then be returned along with a print screen for printing to the local
printer. This will be similar for Hot keys.

36
37
For HOT key, Local printing, the user would change the print location field
in the users BROWSER.PREFERENCES to SERVER.
The three fields in the version are set as follows.

38
At present, hot key, printing at the server only works for the function I – so set
the field D.SLIP.FUNCTION to I.
On clicking the deal slip-printing icon, a request will be sent to the server to
generate a report. A confirmation of the report generation will then be
sent back to the user and displayed in a new window.

39
40
The above deal slip was triggered using the CUSTOMER,CREATE
version but did you notice something here?. Yes, the heading is
colored in red and is of a different font size. Now, how can we
achieve something like that on our deal slip ? We have something
called style sheets which can be used to do all sort of fancy stuff on
the report. Style sheets can be used to create specific templates for
different types of deal slips that are printed.
XSL stands for EXtensible Stylesheet Language.
The World Wide Web Consortium (W3C) started to develop XSL
because there was a need for an XML-based Stylesheet Language.
CSS = HTML Style Sheets
HTML uses predefined tags and the meaning of the tags are well
understood.
The <table> element in HTML defines a table - and a browser
knows how to display it.
Adding styles to HTML elements is simple. Telling a browser to
display an element in a special font or color, is easy with CSS.
XSL = XML Style Sheets
XML does not use predefined tags (we can use any tag-names we
like), and the meaning of these tags are not well understood.
A <table> element could mean an HTML table, a piece of furniture,
or something else - and a browser does not know how to display
it.
XSL describes how the XML document should be displayed!
XSL - More Than a Style Sheet Language
XSL consists of three parts:
XSLT - a language for transforming XML documents
XPath - a language for navigating in XML documents

41
XSL-FO - a language for formatting XML documents
What is XSLT?
XSLT stands for XSL Transformations
XSLT is the most important part of XSL
XSLT transforms an XML document into another XML document
XSLT uses XPath to navigate in XML documents
XSLT is a W3C Recommendation
XSLT = XSL Transformations
XSLT is the most important part of XSL.
XSLT is used to transform an XML document into another XML document,
or another type of document that is recognized by a browser, like HTML
and XHTML. Normally XSLT does this by transforming each XML element
into an (X)HTML element.
With XSLT you can add/remove elements and attributes to or from the
output file. You can also rearrange and sort elements, perform tests and
make decisions about which elements to hide and display, and a lot more.

41
When we commit a transaction using a Version, the deal slip will
automatically be triggered based on the function. Having the
PRINT.LOCATION as SERVER will print the output of the deal slip in the
&HOLD& file but its not displayed. Only the ID of the &HOLD& record is
shown to the end user.
When we set the PRINT.LOCATION to LOCAL, it will display the output of
the deal slip on the browser and also send the output to &HOLD& (We are
experts on &HOLD& ☺ )

42
All style sheets need to be placed under the BrowserWeb.War file in the
path where all the folders related to Webserver is extracted in the location
\BrowserWeb\transforms\custom directory

Instead of creating a style sheet from scratch, lets use an existing one that
is supplied with T24 and modify it to suit our requirements.
clientEnquiry.xsl is a style sheet that is supplied by Temenos. Copy this
with a different name on to the same directory and then change the
content as required.

<h1> to <h6> are HTML tags that define headers. <h1> defines the
largest header. <h6> defines the smallest header
<Font> is a HTML tag which can takes a color option. Hexadecimal Color
codes can be assigned to the text.
Knowledge of HTML or other scripting languages will come in handy when
designing custom deal slips for clients.

43
All style sheets need to be placed under the BrowserWeb.War file in the
path where all the folders related to Webserver is extracted in the location
\BrowserWeb\transforms\custom directory

Instead of creating a style sheet from scratch, lets use an existing one that
is supplied with T24 and modify it to suit our requirements.
clientEnquiry.xsl is a style sheet that is supplied by Temenos. Copy this
with a different name on to the same directory and then change the
content as required.

<h1> to <h6> are HTML tags that define headers. <h1> defines the
largest header. <h6> defines the smallest header
<Font> is a HTML tag which can takes a color option. Hexadecimal Color
codes can be assigned to the text.
Knowledge of HTML or other scripting languages will come in handy when
designing custom deal slips for clients.

44
This function is written to send the output of the enquiry to the
clientdealslip.xsl style sheet. The purpose of this function is to run the
enquiry using the custom style sheet designed specifically for deal slips.

45
The DEAL SLIP that was created earlier have to be linked to the Version
that actually triggers the deal slip. This is achieved using some fields in
the Version application D.SLIP.FORMAT , D.SLIP.FUNCTION and
D.SLIP.TRIGGER.

Until now we just used the above 3 fields now we have another new field
where we can attach a style sheet for the deal slip. This is the
D.SLIP.STYLE.SHEET. This is where a custom style sheet can be
attached to enhance the look and feel of the final output of the deal slip.

46
47
For Automatic, Local printing, the user would change the print location
field in the users BROWSER.PREFERENCES to LOCAL.

48
The Output of the deal slip in Browser is displayed
This deal slip was triggered on COMMITING a CUSTOMER record using
a custom style sheet to enhance the output.

49
When ever a new customer walks in to the bank, in T24 we would have to
create a record in the CUSTOMER application to record his details.
Once the details are recorded, the bank wishes to give the customer a
confirmation note like the one shown below

50
1. Deal slips can triggered from the same version twice one while input
and another while authorizing - True/ False
Answer :True
2. The output of a deal slip can be customized such that the fields of the
application are displayed are shown as Bold characters – True / False
Answer: False
3. The output format of the deal slip can be generated in HTLM, CSV
formats – True / False
Answer: False
4. When a default DE.FORM.TYPE is not defined it takes the ID DEFAULT -
True / False
Answer: True
5. When the output of the deal slip need to be stopped from getting
printed on the Printer it can be sent to a hold file - True / False
Answer: True

51
52
53