TEMENOS T24 Browser Navigation
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 t he express written permission of TEMENOS Holdings NV.
Browser Navigation
Table of Contents Introduction ................................................................... ............................................................................................................................... ........................................................................... ............... 4 Application Overview ............................................................................ ............................................................................................................................... ................................................... 4 Signing Onto T24 using the T24 Browser............................................................................................ Browser............................................................................................ 5 Connecting to the Server ......................................................................... ................................................................................................................. ........................................ 5 Signing onto T24 ............................................................................ .............................................................................................................................. .................................................. 6 Command line line....................................................................... .................................................................................................................................... ............................................................. 10 Command Line Uses...................................................................................................................... 11 Using the T24 Browser Menus ........................................................................... .......................................................................................................... ............................... 13 Favourites....................................................................................................................................... Favourites............................................................................................................................... ........ 13 Help ........................................................................ ...................................................................................................................................... ........................................................................ .......... 14 My T24 ............................................................................... ........................................................................................................................................... ............................................................ 15 Recent Requests Requests............................................................................ ............................................................................................................................ ................................................ 16 Tools............................................................................................................................................... Tools............................................................................................................................... ................ 17 Contracts............................................................................................................................................ Contracts........................................................................................................................ .................... 18 Contract search .............................................................................. .............................................................................................................................. ................................................ 18 Viewing a contract ........................................................................ .......................................................................................................................... .................................................. 20 Editing a contract......................................................................................... contract............................................................................................................................ ................................... 24 Dropdowns ........................................................................ ..................................................................................................................................... ............................................................. 25 Checkboxes and Radio Buttons..................................................................................................... 26 Frequency Control Control........................................................................ .......................................................................................................................... .................................................. 33 Recurrence Control .............................................................................. ........................................................................................................................ .......................................... 35 Field Expansion.............................................................................................................................. 38 Hot Fields ........................................................................... ....................................................................................................................................... ............................................................ 39 Web Validation .............................................................................. ............................................................................................................................... ................................................. 41 Check File Enrichments. ................................................................................... ................................................................................................................ ............................. 42 Errors.............................................................................................................................................. Errors............................................................................................................................... ............... 44 Overrides ............................................................................ ........................................................................................................................................ ............................................................ 45 Helptext and Online Documentation ............................................................................... .................................................................................................. ................... 46 Displaying T24 reports ............................................................................. ....................................................................................................................... .......................................... 48 Deal Slip Printing .............................................................................. ............................................................................................................................... ................................................. 49 BROWSER.PREFERENCES......................................................................................................... BROWSER.PREFERENCES............................................ ............................................................. 49 VERSION ........................................................................... ....................................................................................................................................... ............................................................ 50 D.SLIP.FORMAT............................................................................................................................ 51 D.SLIP.FUNCTION .............................................................................. ........................................................................................................................ .......................................... 52 D.SLIP.TRIGGER........................................................................................................................... D.SLIP.TRIGGER.......................................................................... ................................................. 53 D.SLIP.STYLE.SHEET................................................................................................................... D.SLIP.STYLE.SHEET........................................... ........................................................................ 54
TEMENOS T24 User Guide
Page 2 of 69
Browser Navigation
DEAL.SLIP.PRINTING examples ............................................................................... .................................................................................................. ................... 54 Custom Printing ................................................................... ............................................................................................................................... .............................................................. .. 62 Custom Style Sheets...................................................................................................................... 62 Enquiries ............................................................................ ........................................................................................................................................ ............................................................ 63 Contracts ............................................................................ ........................................................................................................................................ ............................................................ 65 Image Management .......................................................................... ........................................................................................................................... ................................................. 69
TEMENOS T24 User Guide
Page 3 of 69
Browser Navigation
Introduction Application Overview The purpose of this chapter is to provide an overview of the navigation within the T24 system using the T24 Browser, and to show how to access more detailed information available within the system Help Text. The BROWSER interface is supported in Internet Explorer and Mozilla Firefox 1.5.0.0 and upwards.
The T24 Browser has the following standard Browser features: Buttons, text boxes, menus, drag and drop, etc. There are also many other features…. Auto launch enquiries
Multi/sub value deletion and insertion
Bulk approval/rejection of overrides
Multi Company
Calendar Popup
Multiple Applications
Check Boxes
Multiple Enquiry Drilldown options
Context Sensitive Enquiries
Online HTML Help
Drop down lists
Online user guide
Enquiry Selection
Record locking
Error Handling and reporting as a grid
Skins
Grid & Page Enquiries
Tabbed versions
Internet Integration
Text Boxes
T24 menus
Toggle Buttons
Hot field validation
User configurable Composite Screens
Image Management Interface Customisation Local printing Microsoft Internet Explorer
TEMENOS T24 User Guide
Page 4 of 69
Browser Navigation
Signing Onto T24 using the T24 Browser Connecting to the Server Unlike with Desktop, no proprietary software downloads or installations are required to connect to the T24 Browser. The only prerequisite is that the user has an Internet Browser installed, e.g. IE5.
T24 Browser connects to T24 via a web server. The web server contains the client facing packages and software required to create the user interface.
To connect to the server the user simply types in a designated URL into the Browser window, corresponding to the Web Server’s address.
Figure 1 - Blank Browser Window with a URL
The web server is responsible for taking the HTTP request generated by the client’s browser and parsing it onto the T24 server. T24 will then send back a response to the web server, which will then parse and display the results in the client’s browser window.
TEMENOS T24 User Guide
Page 5 of 69
Browser Navigation
Signing onto T24 Once the T24 Browser has successfully connected to the web server, the T24 Browser Sign In Screen is displayed. Enter your T24 user sign in name and password in the appropriate boxes and click the “Sign in” button or press Enter.
Figure 2 - T24 Browser Sign In Screen
TEMENOS T24 User Guide
Page 6 of 69
Browser Navigation
The Sign In screen also contains a number of links for further information on using the T24 Browser. These include:
LINK
DESCRIPTION
Full Tour
This contains information regarding the functionality contained in the browser, as well as links new functionality, etc.
Quick Guide
Guide showing a brief overview of the user interface of the browser.
FAQ
A list of frequently asked questions and answers for information.
Help
Displays T24 Portal page.
The web server then passes on the information provided to the web server via an HTTP request to the server where T24 resides.
After the username and password have been validated by T24, the user will then be given a token. This token represents a user session. This session will last until the user either logs off from his or her user session, or the session times out. The default timeout for a session is thirty minutes.
T24 will then pass back a response to the web server, which will subsequently be parsed and displayed via a Browser. Any further requests that the user makes during the session will contain the token reference.
TEMENOS T24 User Guide
Page 7 of 69
Browser Navigation
Figure 3 - Screen Display after successful user sign-on
On successful login the user will be presented with a page containing a banner image, a welcome message, a set of useful buttons, a command line (depending on user SMS settings), and a set of menus depending on their USER profile and HELPTEXT.MAINMENU configuration. The buttons in the banner are as follows: -
TEMENOS T24 User Guide
Page 8 of 69
Browser Navigation
Menu sections presented on initial login. BUTTON IMAGE
TEMENOS T24 User Guide
BUTTON TITLE
DESCRIPTION
Favourites
Tailored User Abbreviations
Help
Online help text, user guides, etc.
My T24
Displays the user’s main menu.
Recent requests
Displays a list of the user’s most recent requests.
Tools
Displays a menu allowing the user to define their own settings.
Sign off
Signs the user off.
New main window
Displays a new main window containing the banner and the user’s menu.
Page 9 of 69
Browser Navigation
Command line T24 Browser is similar to T24 Desktop in that it has command line functionality if the USER profile is set-up to contain this functionality.
Figure 4 - Command Line
TEMENOS T24 User Guide
Page 10 of 69
Browser Navigation
Command Line Uses ACTION Launch an Enquiry
DESCRIPTION Enter “ENQ” or “QUERY” followed by the name of the enquiry, e.g.
ENQ ACCOUNT-LIST
Run an Enquiry
To run an enquiry direct from the command line with NO selection criteria enter “QUERY” followed by the name of the enquiry and the word “NONE”, e.g.
QUERY ACCOUNT-LIST NONE
To run an enquiry direct from the command line with selection criteria enter “ENQ” followed by the name of the enquiry and the criteria in the form : field operand value, e.g.
ENQ ACCOUNT-LIST ACCOUNT EQ 100069 or ENQ STMT.ENT.BOOK BOOKING.DATE EQ !TODAY ACCOUNT EQ 100069
To run an enquiry direct from the command line using your last selection criteria enter “ENQ” followed by the name of the enquiry and the word “LAST”, e.g.
ENQ ACCOUNT-LIST LAST
Launch an application
Launch a record with a specific function.
TEMENOS T24 User Guide
Any other input is treated as an attempt to launch an application, in one of the following forms:
1)
CUSTOMER – Initiates the CUSTOMER application; record search screen.
2)
CUSTOMER I – Initiates the CUSTOMER application; record search screen.
3)
CUSTOMER I 123456 – Initiates the CUSTOMER application; invokes the record 123456 for input.
4)
CUSTOMER I F3 – Initiates the CUSTOMER application; invokes the next free record for input.
This is limited in that T24 Browser deals with functions differently to that of T24 Desktop. The only functions that are possible from the command lines are S (See), I (Input) and V (Verify).
Page 11 of 69
Browser Navigation
The execute button to the right of the command line - executes the command currently displayed in the command line, as does hitting the return key when the command line is in focus (i.e. the cursor is in the command line).
In addition, the F3 key may be used as the execution key that automatically adds the F3 to the current command and performs the execution.
A history of previous commands will be displayed on entering the command line text box. A dropdown will appear matching the previous commands against the command typed. Choosing a command from the history list will enter it as the current command, where it may be modified and / or launched as a normal command.
TEMENOS T24 User Guide
Page 12 of 69
Browser Navigation
Using the T24 Browser Menus Favourites The favourites menu is a menu structure set up by the user to contain the applications, versions and enquiries that the user uses on a regular basis. This is done via the file USER.ABBREVIATION .
Figure 5 - Favourites menu
USER.ABBREVIATION A user definable menu is available which is populated for the current user from the USER.ABBREVIATION file when the user signs onto T24 Browser.
The Favourites menu offers the following functionality:
•
Menu listing of user abbreviations
•
Launching of enquiries
•
Launching of applications
•
Direct field input short cuts
•
Launch of third party applications
TEMENOS T24 User Guide
Page 13 of 69
Browser Navigation
Help This menu provides access to the online HelpText and T24 Portal.
Also available are the T24 Browser Quick Guide and build information for the Browser.
TEMENOS T24 User Guide
Page 14 of 69
Browser Navigation
My T24 This displays the user’s defined main menu which can be used to access applications, versions and enquiries.
Figure 6 - My T24 menu
TEMENOS T24 User Guide
Page 15 of 69
Browser Navigation
Recent Requests The Recent Requests menu displays the requests the user recently used.
TEMENOS T24 User Guide
Page 16 of 69
Browser Navigation
Tools The Tools menu allows the user to access some common tools. A selection of the possible tools are highlighted below:
•
Change password
•
Amend preferences
•
Organise favourites
The Tools menu also allows the user to change company if they are in a multi-company environment.
Figure 7 - Tools menu
TEMENOS T24 User Guide
Page 17 of 69
Browser Navigation
Contracts Contract search An application can be invoked either by navigating through the initial T24 menu structures or by entering the correct command via the Command line. E.g. FOREX .
When the application search is invoked the user will be presented with the following Window. Clicking on the More Actions dropdown arrow will produce the drop down list.
Figure 8 - Contract Search Screen
The name of the application – Version will be displayed in the top left hand corner of the screen. The name of the account and the version of T24 will also be displayed.
The Window is spit into two sections. The left hand section consists of related menus; the right hand section consists of a facility to search for a record. The left hand side menu is displayed either by the user expanding it, or depending on the status of the deal being edited/viewed.
The left hand menu can be hidden by pressing the Less button ( displayed by pressing the more button ( ) or caption.
) or caption. The menu can be re-
The user can either enter the record id required into the text box, or do a drop down search for the key. This is accomplished by selecting the down arrow to the right of the text box. A new window will be invoked displaying a list of all the records linked to that application.
TEMENOS T24 User Guide
Page 18 of 69
Browser Navigation
Figure 9 - Pop up window containing valid record IDs to select
Select the value that is required by left clicking on the hyperlink with the mouse. This value will then be automatically placed into the text box, and the pop up window will disappear.
At the top of the screen there are three possible buttons: Edit and View and Action. On selecting the Key that is required, either one of these buttons can be used to invoke the deal. The Edit button opens the deal for editing, whereas the View only opens the deal in See mode. The Action button opens the deal in See mode but takes a lock on the server so delete, Authorise or reversal transactions can be done.
Directly to the right of the down arrow icon there is the new deal icon. When this is pressed, a new deal is invoked.
TEMENOS T24 User Guide
Page 19 of 69
Browser Navigation
Alternatively the dropdown list offers the choice of finding the record by listing or searching the Live, Unauthorised and History Files. Here the Unauth List is selected, and a record is displayed in the enquiry, left clicking on the record ID will select the record and place it in the application ID window, from there further functions may be carried out on it such as View, Authorise etc.
Figure 10 – The Unauth list selection form the drop down menu.
Viewing a contract On selecting the View button, after adding a valid record id to the text box, the user is presented with a deal in read only format.
Figure 11 - A record in read-only mode
The main screen displays the record in View mode, as it is in view mode no functions can be carried out in it so the so the function icons are dimmed.
TEMENOS T24 User Guide
Page 20 of 69
Browser Navigation
A series of buttons will be displayed across the top of the screen. For a break down on the functionality behind each buttons see the table below. Functions displayed for a record Icon
FUNCTION
DESCRIPTION
Commit
Commits the deal to the server
Validate
Sends a record to the server for validation. Returns any errors under the error section in the left hand menu. The deal is not committed on the server.
Hold
Places the deal on hold
Delete
Deletes the deal
Authorise
Authorises the deal
Reverse
Reverses an authorised record
Verify
Verification of input (application specific)
Return to application screen.
Closes down the current record and returns to the main application page.
Help
Will launch help text for the application record and all its fields.
Print
Will print page to predefined print settings.
If the function is not available for that particular record, then it will be greyed out. The name of the application will be displayed just below the function Buttons.
TEMENOS T24 User Guide
Page 21 of 69
Browser Navigation
The dropdown list consists of more actions related menus;
Figure 12 - A record with the dropdown list activated
There are seven sections to the dropdown list. See the tables below for a complete break down on each section of the menu:
The Menu MENU TITLE
DESCRIPTION
More Actions
This is where less-used actions are displayed, as apposed to the common actions displayed as deal buttons. This includes the Copy and Paste deal buttons.
List and Search
Allows listing and searching of the live, unauthorised and history files.
Context Enquiries
Any context enquiries related to the files in the displayed record will be displayed here.
TEMENOS T24 User Guide
Page 22 of 69
Browser Navigation
If a version has a number of associated versions defined then they will appear below the version separated by ‘Tabs’. By clicking on the tabs the other versions will be viewable. If the ‘NO.HEADER.TAB’ attribute is set in the version then it will be shown as a tab instead of on its own.
Figure 13 - Multiple tabbed version with the first version in the header
Each of the fields linked to the record are presented as a series of text boxes. If the field is a no input field then the text box will be replaced by a caption only.
The field values will appear in green, indicating that these fields are editable when in Input mode but not in See mode. Also the function buttons should all be greyed out.
TEMENOS T24 User Guide
Page 23 of 69
Browser Navigation
Editing a contract On selecting the Edit button, after entering a valid record Id, or on selecting a new Deal, the following window appears.
Figure 14 - Contract Input screen
If the record is a new deal then the word “NEW” will be displayed to the left hand side of the header information. If the record is an existing record then the ID will be displayed instead. For a new deal, the deal status will be ‘Capture’.
The fields can either be entered by selecting the text box with the mouse, or by traversing to it using the keyboard tab button.
There are several types of special fields: •
Auto Launch Enquiry
•
Hot Field
•
Hot Validate Field
•
Web Validate Field
These field types are explained in greater detail later in this document.
TEMENOS T24 User Guide
Page 24 of 69
Browser Navigation
Dropdowns Some fields on a contract screen may have a drop down icon to the right of it. A drop down can return a list of IDs relating to the file that the field relates to, or can run an enquiry with optional selection criteria.
If the file has a related file defined in STANDARD.SELECTION , then the drop down will list the IDs and information for that field. If however the field is marked as having an enquiry attached to it as defined in VERSION , then the drop down will contain the results of the enquiry. Clicking on a record in the dropdown list will cause the value to be applied to the contract screen.
An example drop down result related to the CUSTOMER file would be:
Figure 15 Dropdown related to Relation Code field
TEMENOS T24 User Guide
Page 25 of 69
Browser Navigation
Checkboxes and Radio Buttons Fields that have a ‘YES/NO’ option are displayed as a Checkbox by default, when inputting a record. Enrichment is provided next to the checkbox to display the field value based upon whether the checkbox is checked or not. Similarly, fields that have 2 or 3 possible options are displayed as Radio Buttons by default.
The following examples illustrate the above field types: -
Figure 16 Checkbox field display
TEMENOS T24 User Guide
Page 26 of 69
Browser Navigation
Figure 17 Radio Button field display
TEMENOS T24 User Guide
Page 27 of 69
Browser Navigation
There may be circumstances where a ‘Combo-box’ field display type is required instead of the default Checkbox or Radio Buttons illustrated above. This is defined in the related VERSION record by applying the value ‘COMBOBOX’ to the DISPLAY.TYPE , for the related field on the Version. Additionally, Radio Buttons can be displayed vertically by applying the value ‘VERTICAL.OPTIONS’ to the DISPLAY.TYPE , for the related field on the Version. This is illustrated in the following examples: -
Figure 18 VERSION record AM.COMPARE,MODEL – Consolidate field set to COMBOBOX
Figure 19 Consolidate field displayed as a Combo-box
TEMENOS T24 User Guide
Page 28 of 69
Browser Navigation
Figure 20 VERSION record SEC.TRADE,ENTRY – Net field set to VERTICAL.OPTIONS
TEMENOS T24 User Guide
Page 29 of 69
Browser Navigation
Figure 21 Radio Buttons displayed vertically for NET field
TEMENOS T24 User Guide
Page 30 of 69
Browser Navigation
The attribute “NO.SORT.OPTIONS” is set in BROWSER.PARAMETERS to list the Option/Radio values without sorting.
By default the option values always remain sorted. When the attribute “NO.SORT.OPTIONS” is set, the listing remains unsorted.
TEMENOS T24 User Guide
Page 31 of 69
Browser Navigation
Calendar Popup Some fields on a contract screen may have a calendar icon ( ) to the right of it. This icon will display a popup of the current calendar month and is only applicable to date fields. On selecting the date required by left clicking on it with the mouse, the value is then placed in the corresponding field.
If a date including an alternative month or year is required then select the required month and year and press the Go ( ) button. Once the new month is displayed, select the required date as before.
Today’s date is highlighted in red. An example calendar would be:
Figure 22 - Calendar pop-up
Help text is also associated with each of the fields. Refer to the section on “Getting Help”.
TEMENOS T24 User Guide
Page 32 of 69
Browser Navigation
Frequency Control There are certain fields on T24 applications that have a frequency pattern icon at the end of the field (on the right) ( ). This icon when clicked, will display a drop down window where by a Frequency Pattern can be selected as required.
Figure 23 - Frequency Control Pattern -1
The calendar pop-up works exactly the same as a normal Calendar icon within the T24 Application. In Frequency Control, this field is more like a mandatory field. Additionally there are 4 radio buttons defined as “Daily, Weekly, Monthly and Defined”.
Each one of these radio buttons, upon clicking, displays a specific Frequency Pattern. 1.
Daily defines Daily and Business Day Frequencies.
2.
Weekly defines Weekly Frequency between (1-9 weeks)
Figure 24 - Frequency Control Pattern -2
TEMENOS T24 User Guide
Page 33 of 69
Browser Navigation
3.
Monthly Frequency defines frequencies such as “Twice Monthly” and Specific months between (1-12) and on specific days between (1-31) where by we are given an option to select specific months.
Figure 25 - Frequency Control Pattern -1
4.
Finally, the Defined frequency defines all the frequencies defined on EB.FREQUENCY record.
TEMENOS T24 User Guide
Page 34 of 69
Browser Navigation
Recurrence Control There are certain fields on T24 applications that have a Recurrence control pattern icon at the end of the field (on the right) ( ). This icon, when clicked, will display a drop down window where by a Recurrence Pattern can be selected.
Figure 26 - Recurrence Control Pattern -1
We have 6 different options defined in Recurrence Control which are “Daily, Weekly, Monthly, Yearly, Defined and Advanced” Each one of these options, on clicking, displays a specific Recurrence Pattern. 1.
Daily defines Daily and Business Day Recurrence Frequencies.
2.
Weekly defines Weekly Frequency between(1-999 weeks)
Figure 27 - Recurrence Control Pattern -2
TEMENOS T24 User Guide
Page 35 of 69
Browser Navigation
3.
Monthly defines Recurrence Frequencies such as “Every N Months” and a Specific day with the month and day, where by we are given an option to select specific day with in a specific month.
N = 1 – 999 months
Figure 28 - Recurrence Control Pattern -3
4.
Yearly defines Recurrence Frequencies such as “Every N Years” and a Specific day/Monthly with the day specified, where by we are given an option to select a specific day with in a specific month for a specific year.
N = 1- 99 years
Figure 29 - Recurrence Control Pattern -4
TEMENOS T24 User Guide
Page 36 of 69
Browser Navigation
5.
Defined Recurrence defines all the frequencies defined on EB.FREQUENCY Record.
Figure 30 - Recurrence Control Pattern -5
6.
Advanced defines Recurrence Frequencies such as “Every” and “On the” where we can combine years, months, weeks and days for any combination required.
Figure 31 - Recurrence Control Pattern -6
NOTE: All recurrence patterns generated must start with “Every” and not with “On the” pattern
TEMENOS T24 User Guide
Page 37 of 69
Browser Navigation
Field Expansion The T24 Browser allows for the expansion and deletion of multi value fields.
Figure 32 - Multi-value expansion in a tab version.
The contract allows for multi and sub values to be expanded and deleted. A multi value field will have and icons to the left of its text box. The caption to the right of the icons will indicate the actual multi value number of that field. E.g. in the above example, the field paying Acct has two instances. Each of the instances are highlighted like so:
Paying Acct :.1 The number represents the multi value instance.
TEMENOS T24 User Guide
Page 38 of 69
Browser Navigation
A multi value can be added by clicking on the icon with the mouse. Likewise, to delete a multi value, the user can click on the icon. If there is only one multi/sub-value, then the button is not displayed.
In the case of Sub values, the field will have an icon to the right of the minus icon. To add a new sub value, the user simply clicks on this new button. To subtract the sub value, the user clicks on the icon if present. If there only is one sub value, but there is more than one multi value set, then the Browser will delete the multi value set in question.
There only is one
button. T24 Browser uses this button to delete both sub values and multi values.
Each of the sub value instances are highlighted like so:
Bene Address:.1.1
This corresponds to the first multi value instance, and the first sub value instance.
Hot Fields The term ‘hot field’ applies to any field on a record that automatically sends a validation request to the server on change of data. Hot Fields are shown with a next to them.
Figure 33 - Hot fields
TEMENOS T24 User Guide
Page 39 of 69
Browser Navigation
In this case the field CLIENT is a hot field. If the field fails validation, then an error message will be displayed in the menu under Deal Errors. When a Hot Field is validated it will also show any enrichment for that field.
To specify a field as a Hot Field the VERSION to which it belongs must be amended. The field “ATTRIBS“should be set to “HOT.FIELD” to signify that validation should be run when this field is exited:
Figure 34 - Set the ATTRIBS field to HOT.FIELD
If a Hot Field is also a dropdown field (as signified with the dropdown icon), then the validation will only be run if the value in the Hot Field does not contain the wildcard characters “…”. This is to allow a user to obtain a dropdown list without the contract being validated.
TEMENOS T24 User Guide
Page 40 of 69
Browser Navigation
Web Validation Web Validation enables the user to perform validation of a contract on the web server. Web validation fields are indicated by the icon In the past this role has been tailored for by validation routines run in the T24 Application Server. Web Validation classes reside on the Web Server, thus speeding up the validation process. This method involves validation of a contract in the background, thus allowing the user to continue editing the contract while validation takes place at the web server. When the validation has completed the currently displayed contract will be updated with any field data changes, as well as any errors and messages. Web validation makes use of the TSDK – “T24 Software Development Kit“. This product contains Java classes and methods which resemble the core T24 applications (e.g. Customer, Account, etc.). The kit also supports communication to the T24 Application Server to read and write records, etc. In this instance, we use the TSDK to validate T24 contracts.
Note : At present Web Validation only works when the XSL transform is set to the server. This is due to a bug in IE6. This bug, according to Microsoft (Microsoft report number 323069), will be fixed in IE6 service pack 2. For more details please see the following web site: http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D32306 9
The writing of web validation routines assumes that the developer has a sound knowledge of Java. The following outlines the steps involved in setting up Web Validation: •
Create the Web Validation class
•
Package and deploy the class
•
Set up the EB.API record for the new class
•
Set up the Web Validate field in the version
•
Generating tsdk local development classes
For further details and examples please refer to the ‘TSDK Implementation Guide’ under the API Section.
TEMENOS T24 User Guide
Page 41 of 69
Browser Navigation
Check File Enrichments. Check File Enrichments will give the User enrichment text for a field after the focus has been moved away from it, this enhancement will work for all field listed in the STANDARD.SELECTION System fields.
To enable the system to allow Check file enrichments the SYSTEM record in BROWSER.PARAMETERS will need to be edited so that the Attributes field has CHECKFILE.ENRICHMENT flagged up.
Figure 35 - Check File Enrichment
Note: that the TCServer will need to be stopped and restarted after this file has been edited and authorised
This will by default allow all users to use Check File Enrichments functionality, this functionality is automatically applied and will provide enrichments to fields associated with tables and that are listed on the STANADARD.SELECTION record.
TEMENOS T24 User Guide
Page 42 of 69
Browser Navigation
When populating a valid field the enrichment will be displayed when the focus is shifted off that field by either the Tab key or left clicking on another field.
Figure 36 - Enrichment focus
If it is decided to withhold this functionality from a User, that User can be exempted by selecting the NO.CHECKFILE.ENRICHMENT option in the Attributes filed in the BROWSER.PREFERENCES record for that User. Other Users will still be able to utilise this functionality.
Figure 37 - Check File Enrichment
TEMENOS T24 User Guide
Page 43 of 69
Browser Navigation
Errors On either Committing or validating a deal, the contract is sent back to the server. The results of the action are then re-displayed in the same window. In the case of any errors, the contract will highlight any erroneous fields in red and display the reason for each error under Deal Errors. The field names on the Deal Errors menu are hyperlinks that when clicked will place the cursor in the field with that error.
Figure 38 - Contract returned with errors
TEMENOS T24 User Guide
Page 44 of 69
Browser Navigation
Overrides On committing a deal, if the deal has any overrides then the deal will be returned along with a list of all of the overrides. These will be displayed under the heading Deal Overrides. In order to commit the deal successfully all of the overrides must be accepted using the “Accept Overrides” button.
Figure 39 – Overrides
On successfully committing a deal, a transaction complete screen will be displayed, indicating that the new record has been committed. The new key of the committed deal is displayed for reference.
Figure 40 - Successful completion of a deal
TEMENOS T24 User Guide
Page 45 of 69
Browser Navigation
Helptext and Online Documentation The HelpText for T24 is accessed from the Help menu as displayed using the Help icon ( main menu page, and then selecting the “T24 Online Help” option:-
Figure 41 – Help Menu
This displays the Help Text system main page:-
Figure 42 – Help Text System
TEMENOS T24 User Guide
Page 46 of 69
) from the
Browser Navigation
Alternatively, HelpText pages can be accessed through the following methods:1. Clicking on the Help icon (
) on a contract screen:
Figure 43 The Help Icon on a Contract Screen
2.
Clicking on a field name on a contract screen:
Figure 44 Clicking on any on the field names will launch the HelpText
3.
Double-clicking in the input box of a editable field on a contract screen - In screen Versions where the field name or label is not displayed by double-clicking in the input box the HelpText will be launched.
4.
Directly using the following URL: http://localhost:8080/BrowserWeb/portal/portal.htm Where “localhost:8080” should be replaced with the address and port number of your web server.
For full information on how to setup, configure and use the T24 HelpText and Online Documentation System please refer the to the ‘ HelpText and Online Documentation ’ user guide under the System Administration section.
TEMENOS T24 User Guide
Page 47 of 69
Browser Navigation
Displaying T24 reports All T24 reports whether run during the end-of-day or on-line, are available for either printing or display on screen.
To invoke the Report Enquiry, you should run the REPORT.LIST enquiry. From the Command Line run “ENQ REPORT.LIST”. This displays the list of reports as follows:
Figure 45 - Displaying T24 Reports
Use the drill down “View Report” to display the required report.
TEMENOS T24 User Guide
Page 48 of 69
Browser Navigation
Deal Slip Printing The printing of deal slip reports is controlled via the following applications: BROWSER.PREFERENCES and VERSION .
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.
Figure 46 - Selecting the BROWSER.PREFERENCES tool
BROWSER.PREFERENCES allows the user to specify the location of the deal slip printing. This can either be set to the server or to a local printer.
TEMENOS T24 User Guide
Page 49 of 69
Browser Navigation
The ‘printer location’ field has the following possible values:
SERVER LOCAL
Figure 47 - Setting the deal slip printing location
VERSION The actual report printed, and when the report is printed, is controlled via the application VERSION . VERSION has four fields of interest with regard to deal slip printing:
D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER D.SLIP.STYLE.SHEET
TEMENOS T24 User Guide
Page 50 of 69
Browser Navigation
Figure 48 - VERSION report
Figure 49 - Deal Slip Print in VERSION
D.SLIP.FORMAT The value(s) defined here are used to produce Deal Slips according to the function and whether the user wants to have them produced automatically or when a 'hot key' is used. Deal slips can be printed to a connected local printer or directed to a Network device. Refer to the REPORT CONTROL section of the Systems Administration User Guide for details of setting up printers.
Deal slips can be linked to a function such as Input, Reversal or Authorisation and specific Deal Slips can be made to relate to those functions.
Either an ENQUIRY record or a DEAL.SLIP.FORMAT record can be entered. If a valid DEAL.SLIP.FORMAT then the system will provide enrichment from the record so the user will know they have the correct record.
Alternatively, an ENQUIRY record can be used to provide a Deal Slip. In this case the enrichment will inform the user that an ENQUIRY record has been selected.
The user may drilldown to the related table DEAL.SLIP.FORMAT to view or select the record to use.
The combination of the associated fields is used to define when the Deal Slip can be produced.
TEMENOS T24 User Guide
Page 51 of 69
Browser Navigation
To trigger them automatically you need to define:
Field
Content Required
D.SLIP.FORMAT
TELLER.SLIP.INPUT
D.SLIP.FUNCTION I D.SLIP.TRIGGER
OL
This will only print the Deal Slip ' TELLER.SLIP.INPUT ' when the deal is validated at I(nput) time.
To trigger them via a 'hot key' or the Browser Deal Slip icon you need
Field
Content Required
D.SLIP.FORMAT
TELLER.SLIP.INPUT
D.SLIP.FUNCTION I D.SLIP.TRIGGER
RQ
This will only print the Deal Slip ' TELLER.SLIP.INPUT ' at I(nput) time when the 'hot key' is used.
Validation Rules
•
Input to this field must be a valid record in either ENQUIRY or DEAL.SLIP.FORMAT files.
•
Must have values in fields D.SLIP.FUNCTION and D.SLIP.TRIGGER to produce Deal Slips
D.SLIP.FUNCTION The Deal Slips can be produced at various times according to the function (or codeword FINISH) and whether they are produced automatically or in conjunction with a 'hot key'.
This functionality only works when D.SLIP.TRIGGER is set to OL. If it is set to RQ then the ‘hot key’ will always be active on the deal, but will only produce a report when the function is set to I. This differs from Desktop in that Desktop will only print the deal when a certain function is in process – the function as selected below.
TEMENOS T24 User Guide
Page 52 of 69
Browser Navigation
FUNCTIONS Valid functions are:
Data Description I
Input
A
Authorise
C
Copy
R
Reverse
D
Delete
H
History |Restore
FINISH Where FINISH is specified, this processing is dependent on the application and may not be triggered for all applications.
Validation Rules
•
Valid input is I, A, C, R, D, H or FINISH.
•
Must have input in fields D.SLIP.FORMAT and D.SLIP.TRIGGER fields to be effective.
D.SLIP.TRIGGER Specifies whether a Deal Slip is produced using a 'Hot Key' or at specified points in a contracts Life Cycle. Control of how and when the Deal Slip(s) are produced is handled by the combination of the function and the trigger type. The two trigger types are:
Trigger type Action OL
Generate a deal slip automatically at points defined by D.SLIP.FUNCTION
RQ
Generate manually using a HOT.KEY at points defined by D.SLIP.FUNCTION
TEMENOS T24 User Guide
Page 53 of 69
Browser Navigation
Hot Key In Browser the 'hot key' icon can be found on the main toolbar.
Validation Rules
•
Must be either OL or RQ.
•
Must have input in fields D.SLIP.FORMAT and D.SLIP.FUNCTION to be effective.
D.SLIP.STYLE.SHEET Specifies a custom style sheet to use when transforming the deal slip. This field is only used when the user is printing locally (BROWSER.PREFERENCES printer location set to “LOCAL”) and automatically (VERSION deal slip trigger set to “OL”).
Validation Rules
Must be a valid XSL style “/transforms/custom/clientEnquiry.xsl”).
sheet
resident
on
the
DEAL.SLIP.PRINTING examples The following five examples detail how deal slip printing occurs in Browser:
•
Automatic, Local printing
•
Automatic, Local printing, Custom stylesheet
•
Automatic, printing at server
•
Hot key, Local printing
•
Hot key, printing at the server.
TEMENOS T24 User Guide
Page 54 of 69
web
server
(e.g.
Browser Navigation
Automatic, Local printing For Automatic, Local printing, the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL.
The four critical fields in version are set as follows:
Field
Content Required
D.SLIP.FORMAT
TELLER.SLIP.INPUT
D.SLIP.FUNCTION
I
D.SLIP.TRIGGER
OL
D.SLIP.STYLE.SHEET
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.
Figure 50 - Automatic, local printing - transaction complete screen
TEMENOS T24 User Guide
Page 55 of 69
Browser Navigation
Figure 51 - Automatic, local printing - deal slip report
TEMENOS T24 User Guide
Page 56 of 69
Browser Navigation
Figure 52 - Automatic, local printing - local print screen
Automatic, Local printing, Custom Stylesheet For Automatic, Local printing, with a custom stylesheet the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL.
The four critical fields in version are set as follows:
Field
Content Required
D.SLIP.FORMAT
TELLER.SLIP.INPUT
D.SLIP.FUNCTION
I
D.SLIP.TRIGGER
OL
D.SLIP.STYLE.SHEET
/transforms/custom/clientEnquiry.xsl
On committing a deal with the function I, a deal slip will automatically be printed. This will display the report generated as transformed using the custom stylesheet along with the user’s local print selection screen, which will enable the user to print the report to a local printer. TEMENOS T24 User Guide
Page 57 of 69
Browser Navigation
Figure 53 - Automatic, local printing - transaction complete screen
Figure 54 - Automatic, local printing - deal slip report
TEMENOS T24 User Guide
Page 58 of 69
Browser Navigation
Figure 55 - Automatic, local printing - local print screen
Automatic, printing at server For Automatic, printing at server, the user would change the print location field in the users BROWSER.PREFERENCES record to SERVER.
The VERSION record would stay the same.
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.
TEMENOS T24 User Guide
Page 59 of 69
Browser Navigation
Figure 56 - Automatic, printing at server
Hot key, local printing For Hot key, local printing, the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL.
The four 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
D.SLIP.STYLE.SHEET
At present, hot key, local printing only works for the function I so set the field D.SLIP.FUNCTION to I.
TEMENOS T24 User Guide
Page 60 of 69
Browser Navigation
When the user clicks on the print deal slip icon (Hot key), a request is sent to the server. If the trigger is set to OL in the VERSION record, then this icon will be disabled.
Figure 57 - Hot key, local printing
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.
Hot key, printing at server For Hot key, printing at server, the user would change the print location field in the users BROWSER.PREFERENCES record to SERVER.
The VERSION record would stay the same as above.
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.
TEMENOS T24 User Guide
Page 61 of 69
Browser Navigation
Figure 58 - Hot key, printing at server
Custom Printing Custom Printing takes advantage of the custom style sheet and custom java script functionality.
The custom style sheet functionality enables the user to specify the name of a style sheet to use to transform the XML response from the server. The name of the style sheet is set up in the java script document custom.js.
Custom.js enables the user to write their own java script functions. These functions can then be linked to buttons via the application BROWSER.TOOLS , which in turn can be added to a BROWSER.TOOLBAR record.
Custom Style Sheets The client has the ability to design their own custom style sheets. These will be used to transform specific resultant XML documents. Proprietary style sheets should be placed in the following XSL directory on the web server:
•
transforms/custom/test.xsl
The reference to this style sheet would then be set in the java script document, custom.js.
TEMENOS T24 User Guide
Page 62 of 69
Browser Navigation
CUSTOM JAVA SCRIPT – custom.js At present custom.js contains two main functions:
•
RunEnquiryRequest o
•
Used to retrieve enquiry information
runContractRequest o
Used to retrieve contract information
Enquiries runEnquiryRequest enables the user to assign the name of an XSL document to be used to transform the resultant enquiry request.
Figure 59 - The function runEnquiryRequest()
The above function can be implemented through a BROWSER.TOOLS record, which will be added to the existing BROWSER.TOOLBAR for the existing enquiry selection screen. This will be done via the concept of annexed toolbars.
Annexed toolbars are a way of adding tools to an existing core toolbar without actually modifying the core toolbar. For example, the core BROWSER.TOOLBAR record for the enquiry selection screen is called ENQUIRY.SELECTION . In order to add a new tool to this toolbar the user would create a new BROWSER.TOOLBAR record called U.ENQUIRY.SELECTION – the ENQUIRY.SELECTION annex. The Browser Tool will then be added to the annexed toolbar. This will prevent the core record from being overwritten whenever a new release of the ENQUIRY.SELECTION record is made.
TEMENOS T24 User Guide
Page 63 of 69
Browser Navigation
Figure 60 - BROWSER.TOOL for special enquiry printing
The addition of the new button to the annexed toolbar will result in the addition of the new print option to the core toolbar.
Figure 61 - Enquiry Selection Screen with new print button
The function, runEnquiryRequest () has been set up to allow the user to add the name of the proprietary style sheet to use in the transformation of the response. The function then runs a request to retrieve the enquiry data.
TEMENOS T24 User Guide
Page 64 of 69
Browser Navigation
Summary For Enquiries •
BROWSER.TOOLS o
•
•
Create a new record for a button.
BROWSER.TOOLBAR – U.ENQUIRY.SELECTION o
Add the new BROWSER.TOOLS record to the BROWSER.TOOLBAR annex for the core record, ENQUIRY.SELECTION.
o
This will add a new button to the main toolbar.
custom.js o
All the user has to do is change the name of the style sheet parameter in the function runEnquiryRequest():
window.document.appreq.ClientStyleSheet.value="/transforms/custom/custom.xs l";
•
•
If another special print button is required, then a new BROWSER.TOOLS record should be created and added to the U.ENQUIRY.SELECTION record.
A new java script function should then be added to the custom.js document: o
•
This would be a clone of the initial JavaScript function, with two differences:
The function would have a different name.
The style sheet name would be set accordingly.
This new function would then need to be referenced In the new BROWSER.TOOLS record, in place of the function runEnquiryRequest ().
Contracts RunContractRequest enables the user to assign the name of an XSL document to be used to transform the resultant contract information received from the server.
TEMENOS T24 User Guide
Page 65 of 69
Browser Navigation
Figure 62 - runContractRequest
The user enters the name of the style sheet to be used in the transform, via this function. This will result in the contract response being transformed by the XSL document specified.
The user can take advantage of this functionality by generating a new BROWSER.TOOLS button .
TEMENOS T24 User Guide
Page 66 of 69
Browser Navigation
Figure 63 - BROWSER.TOOLS example of special printing button
The button would then be added to the annexed BROWSER.TOOLBAR record for the contract screen.
The annexed toolbars are a way of adding tools to an existing core toolbar without actually modifying the core toolbar. For example, the core BROWSER.TOOLBAR record for deals is called CONTRACT . In order to add a new tool to this toolbar, the user would create a new BROWSER.TOOLBAR record called U.CONTRACT – the CONTRACT annex. This will prevent the record being overwritten whenever a new release of the CONTRACT record is released.
All the user needs to do is change the name of the XSL reference in the function, runContractRequest():
TEMENOS T24 User Guide
Page 67 of 69
Browser Navigation
Summary For Contracts •
BROWSER.TOOLS o
•
•
Create a new record for a button.
BROWSER.TOOLBAR – U.CONTRACT o
Add the new BROWSER.TOOLS record to the BROWSER.TOOLBAR annex for the core record, CONTRACT
o
This will add a new button to the main toolbar.
custom.js o
All the user has to do is change the name of the style sheet parameter in the function runContractRequest():
window.document.appreq.ClientStyleSheet.value="/transforms/custom/custom.xs l";
•
•
If another special print button is required, then a new BROWSER.TOOLS record should be created and added to the U.CONTRACT record.
A new java script function should then be added to the custom.js document: o
•
This would be a clone of the initial JavaScript function, with two differences:
The function would have a different name.
The style sheet name would be set accordingly.
This new function would then need to be referenced In the new BROWSER.TOOLS record, in place of the function runContractRequest().
TEMENOS T24 User Guide
Page 68 of 69
