Browser Screen Versions

TEMENOS T24

Browser Screen Versions

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


Table of Contents

Introduction 3 Application Overview 3 Tabbed Screens 4

Opening a tabbed screen 4 Traversing tabbed screens - Enquiry to Enquiry 7 Traversing tabbed screens - Enquiry to Transaction 9 Traversing tabbed screens ndash Transaction to Transaction 10 Scenario 1 TXN ndash ENQ 11 Tabbed screens ndash Enquiry command line invocation 11 Tabbed Screens - Transaction command line version invocation 13

Composite Screens 15 EBCOMPOSITESCREEN 15

Hyperlinks 19 Custom Field Buttons 20

TEMENOS T24 User Guide Page 2 of 25


Introduction

Application Overview VERSION is a standard T24 application which allows users to create customised screens for input authorisation display etc It may also be used to automate the replacement of data on records

It will be rare for any client to use the standard (main) screen input for all T24 applications In fact T24 comes with many useful VERSION records for the majority of T24 applications You are encouraged to copy these and amend them to suit your requirements Do not amend the originals because changes may be issued in future releases

It is also possible to add local sub-routines which can be used for field input and authorisation validation These small programs will allow even greater customisation of T24 by the user

All T24 trading applications are capable of supporting more than one product eg LDLOANSANDDEPOSITS supports loans deposits commitments etc It also supports a wide variation of options eg discounts maturity liquidation rollovers and schedules to highlight a few In order to support this functionality the main LD contract has two hundred fields Although all the fields are necessary only a few are needed for the input or maintenance of a particular contract type Version allows you to create screens which reflect each contract type presenting only the necessary fields and defaulting data into other fields

Each version you define is referenced by the name of the application and the name of the version separated by a ldquordquo For example an LD version for inputting call deposits could have an id of LDLOANSANDDEPOSITS CALLDEP To lsquorunrsquo the VERSION simply enter the application name with the version reference

SMS control can be defined specifically for the version by entering the name of the version with the comma in USER in the field VERSION Consequently you can restrict access to the contract types as well as the application itself

The creation of VERSION records can be divided into three main categories input of the header or title the fields required for input or display and the defaults to be pre-filled when using that specific VERSION



Tabbed Screens

Opening a tabbed screen A tabbed screen enables the Browser to display a series of Enquiries and Versions together on the same screen

Figure 1 - Tabbed Screen

bull Each of the individual Enquiries and versions are displayed on individual tabs

bull Each tab is completely independent only one tab may be active at any given time

bull Switching to another tab will lose all input to the previous tab

bull Tabbed screens are defined in the table EBTABBEDSCREEN In this example three tabs have been defined an enquiry and two versions

bull Whether the tab is to be an enquiry or a version is determined in the field EBTSCONTENTTYPE

o ENQ ndash Enquiry

o TXN ndash Transaction

bull The name that will appear on the tab is entered in the field EBTSTABTITLE

bull The actual enquiry or version to be run is entered in the field EBTSSOURCE

bull It is possible to link selection criteria such that once the selection criteria has been set subsequent tabs can display the enquiry data without the need for the selection criteria to be entered again If there is no matching selection criteria defined in the EBTABBEDSCREEN then the selection criteria will be displayed



bull The mapping between tabs is made possible via the fields EBTSSELECTFROM and EBTSSELECTTO The field you want to extract the data from goes in the former and the field you want to add the data to goes in the latter

bull The rules on which tabs the actual mapping comes from is determined by the type of tabs involved in the process These rules are covered in the proceeding sections

Figure 2 - EBTABBEDSCREEN record

bull A tabbed screen is invoked from the command line by typing in the command lsquoTABrsquo followed by the key to the EBTABBEDSCREEN



Figure 3 - Calling a tabbed screen from the command line

bull The above command will then display all of the tabs laid out in the EBTABBEDSCREEN record lsquoTEST6rsquo

bull If the first tab on the tabbed screen is an enquiry then it will present the Enquiry Selection screen This will only happen on initial display On subsequent visits to this tab the enquiry selection criteria if there is any will be run

bull If the first tab is a version then it will be run as is



Traversing tabbed screens - Enquiry to Enquiry bull All Enquiry mapping will refer to the first enquiry on the tabbed screen regardless of the

designation of the last tab

bull In Figure 4 if the Enquiry lsquoAccount Balancersquo tab is selected then it will use the fields referred to in the EBTSSELECTFROM field ndash in this case ACCOUNT ndash and attempt to map it to the field in the EBTSSELECTTO field It will use the first enquiry on the tabbed screen to perform the mapping The first enquiry in this case is lsquoStatement Entriesrsquo

bull EBTSSELECTFROM and EBTSSELECTTO is multi valued so more than one field can be put forward for mapping

bull If the mapping is successful then it will bring back the results of the enquiry

Figure 4 - Enquiry to Enquiry mapping



Figure 5 - Statement Entries result page

Figure 6 - Account Balance result page based on ACCOUNT mapping from 1st Enquiry



Traversing tabbed screens - Enquiry to Transaction bull When a user traverses from an enquiry to a transaction tab the version will look for the field

specified in its EBTSSELECTFROM field to use as the key to that version

Figure 7 - Enquiry to transaction mapping

bull This field will then be used to interrogate the FENQUIRYSELECT record for the first enquiry on the tabbed screen On finding the field in the FENQUIRYSELECT record it will then use this value as its key

bull In this example the third multi value is a TXN that has specified that it will look for the field CUSTOMER MNEMONIC

bull When the Customer Record tab is clicked the server will attempt to find the field CUSTOMERMNEMONIC from the first enquiry ndash ACCOUNT-LIST It will then attempt to use this as the key to the CUSTOMER record



Figure 8 - Customer record mapped from Enquiry Selection

Traversing tabbed screens ndash Transaction to Transaction bull When a version tab is selected if the previous tab was a version with a valid key then the new

version will attempt to use this key to invoke the new version

bull The second transaction is set up to look for the field CUSTOMERMNEMONIC The following rules apply

o On selecting this tab if the previous tab was a version with a valid key then it will use this as the key to the new version tab

o If a version tab had been navigated to with a valid key then that key will be stored on the client page for future use When selecting the second version if there is a stored key then it will attempt to open up the version with that key

bull This will override the Enquiry to Transaction rule If an enquiry were to be run with a different Customer ID then the stored key on the client would take precedence

TEMENOS T24 User Guide 0 of 25


Figure 9 - Transaction to Transaction mapping

Scenario 1 TXN ndash ENQ bull Enquiry mapping will always refer to the first enquiry

Tabbed screens ndash Enquiry command line invocation bull Running an enquiry with parameters via the command line

o The user can specify the actual tab number of the enquiry to run along with the selection criteria



Figure 10 - Running a tabbed enquiry from the command line with specified selection criteria

bull The above example will open the tabbed screen lsquoTEST2rsquo

bull It will run the enquiry on the first screen with the selection criteria

o CUSTOMERMNEMONIC EQ DBL

bull See below for the resultant enquiry screen



Figure 11 - Command line enquiry result on tabbed screen

Tabbed Screens - Transaction command line version invocation bull The key to a specific tabbed version can be supplied via the command line

Figure 12 - Running a specific tabbed version from the command line with specified key



Figure 13 - Version invoked from command line

bull In the above example the third tab is invoked using the key ldquoDBLrdquo

bull If the version on the tabbed screen already has a key specified in the EBTABBEDSCREEN record then this will take precedence ie the hard coded key will be used instead of DBL

Figure 14 - An example of overriding a command line version key request



In the above example if the second tab is invoked from the command line with the key DBL then the key 100060 will take precedence

Composite Screens A Composite screen is a collection of screens in T24 placed in one browser window but in different frames The individual frames can be set to accept requests for certain enquiries or transactions enabling multiple contract screens and enquiry screens to be utilised without obscuring one another Individual screens within a composite screen can also be set to contain T24 menus Tabbed Screens URLs or other content created through utility routines as well as creating a whole new set of composite screens

Composite screens are defined in the T24 application EBCOMPOSITESCREEN and can be invoked using the command COS ltname of composite screengt which can be run through menus toolbars and on the T24 command line

EBCOMPOSITESCREEN The Composite screen application EBCOMPOSITESCREEN is used to define composite screens This application comprises of a title for the composite screen and a large linked multi value set for defining the contents of each frame and makeup of the frames of the composite screen The multi value is made up of the following fields

bull CONTENTTYPE This field states what the item you are trying to define is it can be one of the following values

o OPENFRAME Create a frame set Tells you are splitting this frame into further frames

o CLOSEFRAME Closes the frameset

o ENQ This item is an Enquiry

o TXN This item is a contract screen

o UTILITY This allows you to call a browser routine Not sure on the entire scope of this

o TAB This item is a tabbed screen

o COS This item is a composite screen

o MENU This item is a menu

o URL This item is a URL

o BLANK This item starts blank

The value of this field then defines what the rest of the item will require

bull BORDERSIZE This field defines what the border of the frame set will be Only used for Open Frame

bull COLS This defines the number and width of the columns It is done in the same format as the frameset tag in html For reference and instructions on this see httpwwww3schoolscomhtmlhtml_framesasp For a given OPENFRAME item you must have either the ROWS or the COLS field set You cannot however have both

bull ROWS As Cols but used to specify rows



bull NAME Gives a name for the Frame All content defining items (ie telling you what is in a frame) must have a name

bull SCROLLING This defines whether the frame is going to allow scrolling Can only be entered with content defining items

bull CONTENT This is a multi purpose field that defines the content of the frame Either a URL the name of an Application and version an enquiry etc Also used to define the name of the utility to be called

bull CONTENTARGS If a UTILITY type is set then this will define the args for the called utility will be defined here

bull ITEMS This sub-valued field is used to define what requests should be sent to this frame It can be specific requests of application and version or enquiry or it can be set to take all unassigned enquiries by setting it to ENQ or all unassigned requests by setting it as ALL Furthermore it can be set to take everything except enquiries by setting it to NOENQ The request is assigned to a window by running through each item until a valid match is found for the request If none are found a new window is launched

NOTE By default when using Composite Screens enquiry drilldowns will be opened in a new window To send an enquiry drilldown to a specific Composite Screen frame set the ITEMS field to be the drilldown option number (eg ldquo1rdquo for the first drilldown ldquo2rdquo for the second drilldown etc)



The structure of a composite screen would be to create a frame set using the OPENFRAME type Then the next items would be the frame contents from left to right or top to bottom The contents of a frame can be another OPENFRAME item which will create a new frameset within that frame The next items would then relate to the frames in that frame set Once all the items in that frame have been defined then the CLOSEFRAME item is added This will cause the current frameset to close If the current frameset was embedded within a frame then the next item definition will return to the previous frameset unless it is at the top level at which point the composite screen definition is closed

The content type and defined content of a content item is only defines the starting content of the item If the frame has any values defined in its ITEMS field then the content will be overwritten by any requests that match those items

Figure 15 - Composite Screen



Figure 16 - Customer Summary



Hyperlinks Hyperlinks are added to a screen version by defining the path of the document or file in the HYPERLINK field on VERSION All information regarding hyperlinks must be input into the hyperlink field with forward slashes ldquordquo as below -

- Internet files must be input as http or https or www followed by the address

- Files must be input as file followed by the path

Figure 17 VERSION record CUSTOMERCLIENT

Highlighted field shows hyperlink in field 10(Account Officer)

In the above example clicking on the fieldname ACCOUNTOFFICER in CUSTOMERCLIENT displays the document defined in the hyperlink in a separate window



Custom Field Buttons T24 Browser provides the facility to attach custom buttons to fields on a Version Custom Buttons perform the related custom javascript function applied to the customjs file (under the scripts directory)

T24 Browser will provide the fieldname and the field value as two parameters and call the function as defined in customjs

For example if ldquoopenOutlookrdquo is placed into the ITEM field on BROWSERTOOLS the system looks for the function ldquoopenOutlookrdquo in customjs and passes in the field name as the first parameter and the field value as the second (where the button has been defined in a VERSION) Since the parameters are pre-defined brackets must not be used in the ITEM field

It is therefore possible to pass in an email address under the field value and open up an email application such as Outlook

The following screenshots illustrate an example setup of a custom button -

Figure 18 Showing new BROWSERTOOLS creation with ldquoFIELDBUTTONrdquo type



For the created browser tool to function some java script code must be added to the customjs script file -

Figure 19 Example display of customjs path



The highlighted text in the following example illustrates some JAVASCRIPT which can be changed to dictate to the system what action to take for the custom button Note that the function name lsquochequeIssuersquo needs to match the value in the ITEM field on the BROWSERTOOLS record -

Figure 20 customjs

The custom button is added to a version by applying the BROWSERTOOLS record id to the required HYPERLINK field on the VERSION record



CURRENTXXXX

CURRENTXXXX variables In addition to the system common variables that can be used in ENQUIRY and VERSION there is a feature where users can populate a variable of their own and use it later There are also a series of new system variables and a much wider option for users to create and use their own User set variables CURRENTXXXX where XXXX can be any value that you feel is applicable the important part for the system to recognise them is the CURRENT prefix The same use is made of these in ENQUIRY amp VERSION Setting them is done by using them without the prefix and reading the content by using the prefix The variables can be set with values from an existing Enquiry field or with a literal value Example CURRENTNAMEgtSHORTNAME populates the variable with the content of SHORTNAME

field from the Enquiry CURRENTTEXTgtHello Everyone populates the variable with the simple text Hello Everyone CURRENTCCYSgt[USD][GBP][JPY] populates the variable with a list of values Then use them in ENQUIRY in the selection field or predefined selection TESTDATE EQ TODAY TESTNAME EQ CURRENTNAME TESTTEXT EQ CURRENTTEXT TESTCCYS EQ CURRENTCCYS

Creation of a CURRENTTEST1

Figure 21 Creation of Enquiry called CURRENTTEST1



Linking this enquiry to previous enquiry

Figure 22 Creating a second enquiry When this enquiry is run the system will search for CURRENTTEST1 variable (highlighted) set by the running of the first enquiry and display the results

These can be set to VERSION too AUTOMFIELDNO = DEBITTHEIRREF AUTNEWCONTENT = CURRENTTEXT

This field should be populated with your CURRENT enquiry

Figure 23 Above shows how the VERSION record fields should be populated using the new variable data

Note You can set the Enquiry to drill down to both another Enquiry and a Version on the one screen




To view the content of any CURRENTxxxx variables there is an ENQUIRY called USERVARIABLES which displays the current content

Note The values of user set variables are empty at initial login and cleared on exit so this Enquiry will only display values set during the current login session

Figure 24 Showing variables set after running variety of enquiries

EBExternalUser These are set on login by an external user and cleared when they logout This means that ENQUIRY amp VERSION can be tailored to accept the content of the variable instead of forcing a user to enter their own customer number or arrangement etc For example instead of having a selection criteria for an Enquiry like CUSTOMERNO EQ 123456 the same Enquiry can use a pre-selection of CUSTOMERNO EQ CURRENTCUSTOMER The standard convention of using the variable is to prefix it with an exclamation mark ie CURRENTCUSTOMER Similarly in VERSION you can now default a field content by using the CURRENTCUSTOMER to populate a customer field with the current content of the variable So the variable could be set in one Enquiry and used in either another Enquiry linked to it or via VERSION to populate fields in an application triggered from the Enquiry

CURRENTCUSTOMER (Customer number)

CURRENTEXTERNALUSER (Mnemonic)

CURRENTARRANGEMENT (Arrangement number)

Introduction

Application Overview

Tabbed Screens

Opening a tabbed screen

Traversing tabbed screens - Enquiry to Enquiry

Traversing tabbed screens - Enquiry to Transaction

Traversing tabbed screens ndash Transaction to Transaction

Scenario 1 TXN ndash ENQ

Tabbed screens ndash Enquiry command line invocation

Tabbed Screens - Transaction command line version invocation

Composite Screens

EBCOMPOSITESCREEN

Hyperlinks

Custom Field Buttons

CURRENTXXXX

CURRENTXXXX variables

EBExternalUser


Table of Contents

Introduction 3 Application Overview 3 Tabbed Screens 4

Opening a tabbed screen 4 Traversing tabbed screens - Enquiry to Enquiry 7 Traversing tabbed screens - Enquiry to Transaction 9 Traversing tabbed screens ndash Transaction to Transaction 10 Scenario 1 TXN ndash ENQ 11 Tabbed screens ndash Enquiry command line invocation 11 Tabbed Screens - Transaction command line version invocation 13

Composite Screens 15 EBCOMPOSITESCREEN 15

Hyperlinks 19 Custom Field Buttons 20

TEMENOS T24 User Guide of 25


Introduction










Tabbed Screens








o ENQ ndash Enquiry


































































































































Figure 20 customjs




CURRENTXXXX























Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser


Introduction










Tabbed Screens








o ENQ ndash Enquiry


































































































































Figure 20 customjs




CURRENTXXXX























Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser


Tabbed Screens








o ENQ ndash Enquiry


































































































































Figure 20 customjs




CURRENTXXXX























Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser





























































































































Figure 20 customjs




CURRENTXXXX























Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser


CURRENTXXXX























Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser


















Introduction


Tabbed Screens








Composite Screens

EBCOMPOSITESCREEN

Hyperlinks


CURRENTXXXX


EBExternalUser

Browser Screen Versions

Documents

Transcript of Browser Screen Versions