Tool Box

Tool Box
Release: R19 AMR

May 2019
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, for any purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.
© 2019 Temenos Headquarters SA - all rights reserved.

Tool Box
Table of Contents
Introduction 4
Purpose of this Guide 4
Intended Audience 4
Overview 5
Tool Box — General 6
Setup 7
Application Features 10
User Options 11
Signing On 14
Connection Profiles 17
User Interface 19
Help System 27
Communications Logger 28
Error Handling 30
Composite Screen Builder 31
Overview 31
Screen Design 32
Data Library 39
Overview 39
Architecture 40
Library Components 41
Data Library — Setup 43
Definition Designer 46
Definition Runner 53
Unit Download 55
Unit Upload 59
Dev Studio 62
Overview 62
Dev Studio — Setup 64
The Code Editor 66
My T24 Projects 82
2
Tool Box
The T24 Visual Debugger 86

Spy Session & Command Session 96
Enquiry Wizard 97
Overview 97
Screen Design 99
Known Issues 105
Help Centre 106
Overview 106
Screen Design 107
Screen Builder 109
Overview 109
Screen Design 110
Branch Administration Console 118
Overview 118
Administration Console 119
Rules Designer 120
Overview 120
Rules Designer — Setup 121
Screen Designer 122
Overview 122
Launching T24 Screen Designer 123
Screen Wizard 126
Design View 130
Screen Settings 134
Saving Screen 146
System Monitor 148
Overview 148
T24 Monitor 150
Monitor Manager 154
System Connectivity 156
3
Tool Box
Introduction
Purpose of this Guide
The Temenos T24 ToolBox is designed to complement the T24 Browser. This doc-
ument details how the T24 ToolBox provides access to specialised components that
interact with the T24 server and implements a uniform interface and access point.
It also details the standard features that all loaded components can exploit, refer
T24 ToolBox Features for more details.
Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.
Introduction 4
Tool Box
Overview
T24 ToolBox is a Windows based application and is installed in a standard manner.
Please refer to the ‘T24 ToolBox Installation’ section.
T24 ToolBox communicates with the T24 web server using the http protocol, send-
ing and receiving XML messages. The T24 web server will use the T24 connector to
rely these messages to the T24 system.
This user guide will describe how to use the T24 ToolBox and highlight all the fea-
tures.
l Toolbox — General
l Toolbox — Composite Screen Builder
l Toolbox — Data Library
l Toolbox — Dev Studio
l Toolbox — Enquiry Wizard
l Toolbox — Help Centre
l Toolbox — Screen Builder
l Branch Administration Console
l Rules Designer
l Screen Designer
l System Monitor
5 Overview
Tool Box
Tool Box — General

l Setup
l Application Features
l User Options
l Signing On
l Connection Profiles
l User Interface
l Help System
l Communications Logger
l Error Handling

Tool Box
Setup
Installation Pre-Requisites
Before the T24 ToolBox can be used, a fully configured web server for the T24
Browser is needed. The T24 ToolBox connects to the same servlet as the T24
Browser. Since installing and configuring T24 Browser has already been doc-
umented please refer the T24 Browser documentation set for details.
The following sections deal with installing the T24 ToolBox on the client machine.
Prerequisites
T24 ToolBox utilises the Microsoft® .NET 3.0 framework. The Microsoft® .NET 3.0
framework is pre-installed on most new PCs however it may be necessary to install
the framework manually. The Microsoft® .NET 3.0 framework can be found on the
Microsoft’s website www.microsoft.com and the installation CD. In addition any ser-
vice packs or updates for the framework will need to be installed.
During the T24 ToolBox setup if you get the following message:
Install of .NET required

This means that the PC does not have the Microsoft® .NET 3.0/.5 framework.
The Microsoft® .NET 3.0 framework can be installed by running the ‘dotnetfx.exe’
file distributed with the T24 Tool Box setup.
Alternatively the Microsoft® .NET 3.0 framework can be obtained from the
Microsoft web site by clicking ‘Yes’ on the above message.
During the .NET framework setup if you get the following message:
The message above indicates that the .NET framework is not compatible with your
operating system. See the chapter below for minimum system requirements.
7 Tool Box — General

Tool Box
System Requirements for Installing .NET Framework 3.0 and T24

ToolBox
Since T24 ToolBox requires the Microsoft® .NET 3.0 framework, the following min-
imum system requirements must be met before .NET 3.0 and ToolBox can be
installed:
Processor Minimum:
l 400 megahertz (MHz) Pentium processor
Recommended:
l 1 gigahertz (GHz) Pentium processor
Operating System .NET Framework 3.0 can be installed on any of the following
systems:
l Microsoft Windows 2003 Server Service Pack 1 (SP1)
l Windows XP SP2
Windows Vista *
* Windows Vista comes with .NET Framework 3.0. There is
no separate installation package required. The standalone
.NET Framework 3.0 packages are not supported on Vista.
RAM Minimum:
l 96 megabytes (MB) *
Recommended:
l 256 MB *
* Or the minimum required to run the Operating System,
which ever is higher
Hard Disk Up to 550 MB of available space may be required.
Of which 50MB is required for ToolBox
CD or DVD Drive Required.
Display Minimum:
l 800 x 600, 256 colours
Recommended:
l 1024 x 768 high colour, 32-bit
Mouse Required

Tool Box
Installation/Un-Installation
The T24 ToolBox application can be installed by running the setup.exe found on the
install CD. The setup will guide you through the install and will allow you to specify
the install location.
To remove T24 ToolBox from your system please use the ‘Add/Remove Programs’
tool provided by the Windows Operating System (normally found under ‘Control
Panel’).
Post Installation
After the T24 ToolBox has successfully installed on to your system. The T24 ToolBox
application can be accessed via:
1. Desktop shortcut – T24 ToolBox
2. Program Files à Temenos T24 à T24 ToolBox

Tool Box
Application Features
Dynamic Plug-In Architecture
The T24 ToolBox provides an interface to components that perform specialised busi-
ness functions. These components can be referred to as ‘Plug-Ins’. Each Plug-In
provides the user with certain ‘Actions’ to carry out the specified function. These
are referred to ‘Plug-In Items’. The T24 ToolBox provides a framework where these
Plug-Ins and Actions are made accessible to the users. During loading the T24
ToolBox framework dynamically loads ‘authorised’ Plug-Ins and hosts them within
the interface. Although the end user does not need to know about this, it is import-
ant to understand that the T24 ToolBox can be easily extended to host a variety of
Plug-Ins and Actions. New Plug-Ins and Actions may become available after an
upgrade. Also system administrators can prevent access to chosen Plug-Ins by not
deploying it to the users machine.
Auto-Launch Items
Users are able to flag any action as a ‘Start-Up Item’. This means that that action
will be automatically launched according to the ‘Start-Up Mode’. Current Start Up
modes are:
1. Launch On Start Up: this will launch the item when the T24 ToolBox applic-
ation is opened.
2. Launch On Sign On: this will launch the item when the user has signed on to
the T24 server.
Using this mechanism, users can flag commonly used actions so reducing the need
to navigate and manually execute each item.
Auto-Launching Items is described further in ‘Plug-In Item Context Menu’ section)
Desktop Management
Screen ‘real estate’ is an important factor in modern computing. T24 ToolBox auto-
matically saves and restores window sizes and positions. Users can arrange the win-
dows on to their screens as desired and the next time they are opened they will be
restored to the previous location and dimensions. This in combination with ‘Auto-
Launch Items’, (described above), can provide users with a fast and efficient screen
‘real estate’ management.

Tool Box
User Options
Before sign-on is possible the address of the T24 web server must be specified. On
the T24 ToolBox menu bar select ‘Tools’ then ‘User Options’. The T24 ToolBox
Options dialog (shown below) will be displayed.
The User Options Dialog

This dialog allows user to enter communications, connection & display settings. Mul-
tiple instances of these settings can be entered by associating them with different
profiles – see ‘Connection Profiles’ section.
Users can select which profile to use from the sign-on screen.
By default a ‘Default’ profile has is created by ToolBox and settings can be entered
under it. The settings that can be entered are:
Communications
CommsLog
This can be set to ‘TRUE’ or ‘FALSE’. If set to ‘TRUE’ ToolBox will start the com-
munications logger application. This application will log all requests & responses
between the active URL, see ‘Communications Logger’ section.
ConnectionType
The following options can be set:
HTTP – Default
HTTPS – Use if the Browser Web application has been secured with HTTPS
TAG – Use if ToolBox is communicating with a TAG node.

Tool Box
Connections
IPAddress
This is the address the web server that the Browser Web Application is hosted on
e.g. localhost
PortNumber
This is the Port Number that the web server has heed set up to use e.g. 8080
Note: this can be left blank if required e.g. when using a proxy server.
URLAddress
The URL of the Browser web application e.g. BrowserWeb/servlet/BrowserServlet
Once all the connection ‘components’ have been entered the full & final address
can be verified by viewing the ‘Current Connection Address’ as this will change as
the address components are supplied.
The User Options Dialog showing connection address components
Display Options
FloatOnTop
This option can be set to ‘TRUE’ or ‘FALSE’. If set to ‘True’ then the T24 ToolBox
application will ‘float’ on the screen when it does not have focus. This can be useful
when the user has many applications open at once and allows for more advanced
screen ‘real-estate’ management, (see screen shot below).
Note: this setting will only become active once ToolBox is restarted.

Tool Box
The T24 ToolBox ‘floating on top’ even though Windows explorer is active, you can
still see a faint image of the T24 ToolBox.
IconSize
The ‘IconSize’ can be set to ‘Large’ or ‘Small’. This will be the default setting for all
item icons displayed in the T24 ToolBox Plug-In screens.
Skin
This changes the ToolBox colour scheme. The options are ‘Default’ or ‘New XP’.

Tool Box
Signing On
Now that a profile has been defined and connection address has been set the T24
username and password can be entered on the T24 ToolBox Sign On screen (shown
below).
Note: If multiple connection profiles have been specified the ‘Profile’

combo box can be used to select the desired profile, (see ‘Connection
Profiles’ section).
The T24 Toolbox Sign-On Screen

Once the correct details have been entered click ‘Sign On’. The T24 ToolBox will
attempt to establish a connection to the Browser Web Server. Once a connection
has been successful the User and Password text boxes will be disabled. If an error
occurs such as ‘Security Violation’ then this will be displayed to the user.

Tool Box
A Security Violation Error Message

If ToolBox detects a connectivity problem during signing on then it will display the
error message and give the user the option to test the connectivity:
If the ‘Test Connectivity…’ hyperlink is clicked then the T24 Connectivity Monitor is
launched and can be used to test the path to the chosen T24 server.
Connection Error Messages

Below are common connection error messages. Your web server may return dif-
ferent errors.
Error Message Cause

Tool Box
Security Violation Incorrect username or password has been sup-

plied.
This could also indicate that the T24 Connector is
not running.
Exception: The underlying con- The full connection address cannot be resolved.
nection was closed: Unable to Ensure you have specified the correct address
connect to remote server. components.
Exception: The Remote Server A connection was made to the remote server but
Returned an Error: (404) Not it could not find the requested page. Review the
Found ‘URLAddress’ part of the connection string.
Exception: Invalid URI: The Check the ‘Current Connection Address’ in the
format of the URI could not be User Options dialog. The format is incorrect.
determined.

Tool Box
Connection Profiles
ToolBox allows multiple connection profiles to be configured. This allows users to
connect to different T24 Browser web instances easily.
Creating & Editing a Connection Profile

From the ‘User Options’ dialog press the ‘Create’ button under the ‘Profiles’ section.
Creating a new connection profile.

Enter a Name and Description for this profile and press ‘OK’
To add settings under this profile simply select it and enter the settings on the right
and press ‘OK’
This entry will now appear in the ‘Profile’ combo box on the ToolBox Sign-on screen
and the user can select this option as desired.

Tool Box
Connection Profile context menu

Profile settings can be edited by pressing the ‘Edit’ button or Deleted by pressing
the ‘Delete’ button or by right-clicking on the profile entry.
Any profile can be set as a default profile by pressing the ‘Set Default’ button. This
will ensure that this profile is always selected each time ToolBox is launched.
Selecting a Connection Profile

On the ToolBox Sign-On screen, the ‘Profile’ combo-box will list all configured con-
nections profiles. To connect to the desired area, simply select the profile from this
list. Ensure a valid T24 user name & password has been provided and click the
‘Sign-On’ button.
Several Connection Profiles available to select. Note that ‘Latest WAR’ has been set
as ‘Default’

Tool Box
User Interface
The T24 Toolbox Interface
Executing an Item
The T24 ToolBox provides an interface to Temenos approved Plug-Ins. The ToolBox
groups each Plug-In under it’s own Tab or Screen. The screen shot above shows that
there several Plug-Ins available. The ‘Designers and Wizards’ plug-in is currently
selected. The ‘Designers and Wizards’ Plug-In contains ‘Items’, the ‘Enquiry Wizard’,
‘Screen Designer’ , ‘Screen Builder’, ‘Composite Screen Builder’ & ‘Rule Designer’.
Each of these items can be executed by double-clicking on them.
ToolTips
Tool tips are provided by the T24 ToolBox on the Plug-In Tab and on the Item icon.
To determine what each Plug-In tab is for simply hover the mouse cursor above the
particular Tab. A tool tip will appear giving a description of the type of action-
s/items associated with it.

Tool Box
Plug-in tool tip

In a similar manner, to determine what each item does, hover the mouse cursor
over the item icon and a tool tip will be displayed giving a description of the selec-
ted item.

Tool Box
Item tool tip
Status Bar
The status bar displays two panels. The first panel displays the connection status
either:
On Line: an active connection has been established.
Off Line: no active connection to the T24 server.
Connecting: this is displayed when the T24 ToolBox is initiating a connection
with the T24 Server.
The status bar panel second displays the T24 user name once a connection has been
established.
Plug-In Item Display

The T24 ToolBox allows the Plug-In items to be displayed in two views. One uses
‘Large’ icons, the other ‘small’ icons. The views can switch from one to the other by
right clicking anywhere on the Plug-In screen and selecting ‘View’.

Tool Box
Switching Plug-In Item views from 'Large' to 'Small' Icons
Note: The default Icon size can be set under the ‘Tools’ à ‘User Options’
dialog. This setting will be applied each time the T24 ToolBox is
launched.
Menu Bar Actions

Tool Box
The Menu Bar
File Menu
l Sign On - Signs On to the T24 Server using the login details supplied on the
‘Sign On’ screen.
l Sign Off - Signs Off the T24 Server, this option is enabled when a connection is
active.
l Exit - Closes the T24 ToolBox.
GoTo Menu
This menu provides direct access to the Plug-In actions and will launch all the Items
found on the Plug-In screens (see figure above).
Tools Menu
l User Preferences menu item will launch the ‘T24 ToolBox Options’ dialog (see
‘ToolBox Options’ section)
Help Menu
l Help – Launches the T24 ToolBox help system. (see ‘ToolBox Help’ section)
l About – Launches the ‘About ToolBox’ dialog.
The ToolBox About dialog.

ToolBox and T24 Server versions are displayed.

Tool Box
A list of all hosted Plug-Ins is given and a hyper-link to the ToolBox build inform-
ation file is provided.
System Tray Actions
The T24 Toolbox System Tray Icon with its context menu
The T24 ToolBox will display a Windows System Tray Icon (as shown above). The
icon displayed reflects the T24 ToolBox connection state; On Line, Off Line or Con-
necting (see Status Bar section).
When right-clicked a context menu is shown (see screen shot above). These actions
perform the following:
l Sign On - Signs On to the T24 Server using the login details supplied on the
‘Sign On’ screen.
l Sign Off - Signs Off the T24 Server, this option is enabled when a connection
is active.
l Open – Brings the T24 ToolBox application to the front of the screen and will
‘restore’ it if it has been ‘minimised’.
l Exit - Closes the T24 ToolBox

Tool Box
Plug-In Item Context Menu
The Item Context Menu

l View – Large or Small Icons (see ‘Plug-In Item View’ section above).
l Auto-Launch - This can be checked and un-checked to set the chosen item as
a Start-Up item according to it’s ‘Start-Up Mode’ defined under ‘Item Prop-
erties’ (see ‘Item Properties’ section).
l Add & Remove Shortcut –This allows a windows shortcut to be added or
removed within this plug-in pane. This can be used to add related documents
or applications. Auto-Launch conditions can also be set on these items.
l Properties – This displays the ‘Item Properties’ dialog (see ‘Item Properties’
section).
l [Plug-in Item] Help - This displays the help file associated with the selected
item.

Tool Box
Item Properties
Item Properties
This dialog displays specific ‘non-modifiable’ properties relating to the currently
selected Plug-In item. This information can help with problem investigation.
Auto-Launch
This can be set to ‘Launch On Start Up’ or ‘Launch On Sign On’. If ‘Launch On Start
Up’ is selected then the item will be automatically launched the next time the T24
ToolBox application is opened/executed. If ‘Launch On Sign On’ is selected then this
item will be automatically launched when a connection has been successfully estab-
lished with the T24 Server.
Note: This setting will only take effect if the ‘Auto-Launch’ menu item is
‘checked’ in the Plug-In Items Context Menu (see ‘Plug-In Item Context
Menu’ above).
Change Icon
The user can change the item icon by navigating to a chosen resource and selecting
it. The ‘Restore Default’ button can be used to restore the original icon.

Tool Box
Help System
ToolBox provides a menu to access it’s own help information. Users can refer to this
help system when required. All ToolBox help files are installed during the install-
ation process.
The ToolBox Help System can be accessed by via the ‘ToolBox Help…’ menu item
under the ‘Help’ Menu on the main menu.
The ToolBox Help dialog can be used to access all help files that relate to the
ToolBox application. A menu is also provided to access the help files for all hosted
plug-ins and their associated actions.
Note: A pdf viewer is required to view some of the help files. A free pdf
viewer can be downloaded from http://www.adobe.com/.
The ToolBox Help dialog

Tool Box
Communications Logger
Under the ‘User Options’ dialog if the ‘CommsLog’ option is set to ‘TRUE’, ToolBox
will start the Communications logger application.
This application will log all requests and responses sent to the T24 Browser web
server.
Accessing the Communication Logger

When the ‘CommsLog’ option is set to ‘TRUE’ and new system tray icon will appear:
The communication logger application system tray icon.

The ‘info bubble’ will disappear after a short time and the communications logger
is now active and will log all communications between ToolBox ad the T24 Browser
web server.
To access the communication logger right-click on the system tray icon to access
it’s menu or simply double-click on it.
Communication Logger’s Menu

Once the Communications Logger application is opened a window will appear that
contains information that may be useful during issue resolution. The contents of this
window can be saved to a file and sent to the Temenos Helpdesk when required.

Tool Box
The communications logger application

Tool Box
Error Handling
The error reporter

If an error occurs during the application lifetime the above dialog box will be
presented to the user. The user may possibly determine the cause of the error click-
ing the ‘Show Details’ button. As well as giving debug information that may help
resolve the problem it will also display the last communications sent and received
with the T24 Server.
The ‘Create Error Report Now’ hyper link can also be used to automatically create a
debug file that can be sent to the Temenos helpdesk for problem investigation. If a
file is created it will be found in the T24 ToolBox installation folder. An example of
the error report is shown below. The newly created error report will be launched
and displayed to the user.
Example Error Report

Tool Box
Composite Screen Builder

Overview
The composite screen builder allows the user to create composite screen for use
with the T24 Browser. Composite split the screen into sections which can have the
content customised e.g. contracts, enquiries etc.
l Screen Design
31 Composite Screen Builder

Tool Box
Screen Design
Navigation buttons are placed at the bottom of the screen. Finish will not be
enabled until an enquiry has successfully been created in T24. The steps required to
complete the creation of an enquiry are listed on the left hand side.
Step 1 – Welcome Screen

Below is a screen shot of the welcome screen, this gives an overview of the func-
tionality and navigation instructions.
Step 2 – Screen Id
The ID must be unique as modifying an existing screen is not supported in addition
there must not be an unauthorised EB.COMPOSITE.SCREEN record with the same
ID.
The ID must adhere to the restrictions on the ID for EB.COMPOSITE.SCREEN.

Tool Box
Step 3 – Description
This step allows the user to provide a user friendly description for the screen. At
least one description must be provided.
Step 4 – Select Layout

Here the user must select a layout from those provided by click the button below
the layout.

Tool Box
Step 5 – Change Size

To sizes can either be in pixels or percentages. To use pixels simply type the num-
ber in the “Other” field. For other percentages simply type the percentage in the
other field and suffix it with “%”.
An understanding of how HTML frames work would be ideal. However, to sum-
marise:
l In a two column/row layout the right frame or bottom frame respectively can
not have a specific size.
l In a tree pane layout the right and bottom most frame can not have a specific
size.

Tool Box
If the version of Browser supports rendering composite screens without frames,

then the ‘Use Frames’ checkbox will be enabled. Turning off this property will
update the ‘NO.FRAMES’ attribute in the composite screen definition. If ‘Use
Frames’ is not set, compatible versions of Browser will render the composite screen
without using frames. For example, this feature should be UNCHECKED for screens
designed for Internet banking applications.
If the Browser version does not support the ‘noframes’ option, then this checkbox
will be disabled.
Step 6 – Pane Properties
This stage allows the user to set the behaviour of the composite screen.
Initial Content
Each pane must have a name and initial content. This is the contents of the pane
when the composite screen is launched. To set this content use the ‘Initial Content’
dialog:

Tool Box
The Initial Content Dialog.

The initial content can be one of the following:
l Banner (The T24 Command Line will be displayed)
l Blank (No Initial content will be set)
l Composite Screen (A valid Composite Screen ID should be specified –
EB.COMPOSITE.SCREEN)
l Enquiry (A valid Enquiry ID should be specified - ENQUIRY)
l Menu (Will display the users T24 Menu)
l Tabbed Screen (A Valid Tabbed Screen ID should be specified –
EB.TABBED.SCREEN)
l Tool Bar (A Valid Tool Bar ID should be specified – BROWSER.TOOLBAR)
l Tool Item (A Valid Tool Item should be specified – BROWSER.TOOLS)
l Transaction (A valid Contract & ID should be specified)
l URL (if not prefixed with http:// the may not behave as intended).
Dynamic Content
Dynamic content is what will appear in the panes when the user starts using the
composite screen e.g. committing transactions, viewing enquiries etc. The
‘Dynamic Content’ dialog should be used to set this.

Tool Box
The Dynamic Content Dialog

Dynamic Content can be set to one of the following:
l All Content, all transaction and enquiry screens will appear in the specified
pane
l All Enquiries, all enquiries will appear in the specified pane
l No Enquiries, all content except for enquiries will appear in the specified
pane
l Specific Enquiry, the pane will only ever contain the specified enquiry
Allow Scrolling
This option can be set to ‘True’ or ‘False’. This allows or prevents a scrollbar appear-
ing on the corresponding pane during use.
Frame Name
This setting must to set to a UNIQUE identifier within the composite screen defin-
ition, i.e. if your composite screen has 3 panes then with ‘FrameName’ must be
unique.
Step 7 – Sending Request Confirmation

Below is the confirmation of a successfully created composite screen. If any errors
occur during the commit process then these will appear in this screen and the user
can click the ‘Previous’ button to correct any errors.
Once the composite screen has been successfully submitted it can be launched in
Browser using the key word ‘COS’ e.g. at the T24 command line enter ‘COS
MY.COMPOSITE.SCREEN.ID’

Tool Box

Tool Box
Data Library
Overview
The T24 ToolBox Data Library can be used as an alternative to the existing
DATA.LIBRARY Application. Although the T24 ToolBox Data Library utilises some of
the existing mechanism and logic there are fundamental differences between the
two applications in terms of functionality and architecture.
The main differences are:
1. Data is stored in an XML format (OFSML) not the propriety DATA.LIBRARY
format.
2. Data is can be downloaded locally on the client.
3. Data is uploaded/imported in to the target T24 environment using an OFS
input channel and not the propriety DATA.LIBRARY restore logic.
4. OFS audit information is applied.
The main common features are:
1. Data Libraries are organised into logical units.
2. Data Library definitions are stored in T24 in DL.DEFINE application.
3. Ability to export/import both data and programs.
l Architecture
l Library Components
l Setup
l Definition Designer
l Definition Runner
l Unit Download
l Unit Upload
39 Data Library
Tool Box
Architecture
The T24 Data Library contains a suite of applications that allows users to upload
and download data records to and from a T24 environment. The data records cre-
ated by the T24 Data Library process are in XML (OFSML) format. The T24 Data
Library process uses the same communication channel as the T24 Browser to read
data records form T24 and will use a specified OFS channel to upload data records
to the system.
The T24 Data Library process overview.
Data Library 40
Tool Box
Library Components
The ToolBox Data Library Components
Definition Designer
This tool allows users to create download units. A Download unit can be composed
of any number T24 Data Records and T24 programs. The Definition Designer
provides a graphical environment that allows easy selection of Data and Program
items. Once a Unit has been defined a user can select to save this definition locally
or to the T24 Server. All Definitions that are saved to the server are stored in the
system table DL.DEFINE.
Run Definitions
Once a Definition has been saved to the server; using the ‘Definition Designer’. The
‘Run Definitions’ tool, can be used to select the required definition and run it. This
actually ‘VERIFIES’ the specified DL.DEFINE record and creates XML files within the
DL.DATA directory on the server.
41 Data Library
Tool Box
Unit Download
The ‘Unit Download’ tool can be used to browse the DL.DATA server directory and
download the units locally to the user’s machine.
Unit Upload
This allows users to browse local units and select them for up-loading to the T24
server. This uses a specified OFS Channel to input/upload the data to the T24 server.
Options
Holds all options and paths required by the T24 Data Library.
Data Library 42
Tool Box
Data Library — Setup

Before using the T24 Data Library applications users must specify required para-
meters. The Options dialog provides a central place were all the options can be spe-
cified.
The T24 Data Library Options

WorkingDirectory: This is the local path where download units will be created.
ServerDirList: A list of server directories that will be displayed in the ‘Add Program’
dialog
CatalogObjectCode: If set to TRUE any Object Code that is uploaded will be auto-
matically catalogued using the jBASE ‘CATALOG’ command.
GTSControl: Controls how GTS and OFS will handle error conditions for activities
using the current version record. The following values are allowed:
[Null] Reject errors / Approve overrides
GTS - Validation errors will result in the record being rejected, the GTS data record
in the output directory will be appended with an error code (90) Overrides will be
accepted by default, the GTS data record in the output directory will be appended
with the acceptance code (00).
OFS - Validation errors will result in the record being rejected, the OFS data record
will be returned with details of the error message. Overrides will be accepted by
default, the overrides will be returned in the populated OFS data record.
[1] Errors on HLD / Approve Overrides
GTS - Validation errors will place the record on hold, the GTS data record in the out-
put directory will be appended with an error code (80). Overrides will be accepted
by default the GTS data record in the output directory will be appended with the
acceptance code (00).
43 Data Library
Tool Box
OFS - Validation errors will place the record on hold, the OFS data record will be
returned with the error messages. Overrides will be accepted by default, the values
approved will be returned in the populated OFS record.
[2] Errors Rejected / Overrides in HLD)
GTS - Validation errors will result in the record being rejected, the GTS data record
in the output directory will be appended with an error code (90). Overrides will res-
ult in the record being placed on hold; the GTS data record in the output directory
will be appended with an error code (81).
OFS - Validation errors will result in the record being rejected, the OFS data record
will be returned with the error messages. Overrides will result in the record being
placed on hold.
[3] Errors in HLD / Overrides HLD
GTS - Validation errors will place the record on hold, the GTS data record in the out-
put directory will be appended with an error code (80). Overrides will result in the
record being placed on hold; the GTS data record in the output directory will be
appended with an error code (81).
OFS - Validation errors will place the record on hold, the OFS data record will be
returned with the error messages. Overrides will result in the record being placed
on hold; the OFS data record returned will store the override message.
[4] Hold Only
GTS - This option is not available using GTS. Messages can be written straight to
HLD using the GTS MODE field in GT.SYSTEM.PARAMETER.
OFS - If field validation (FIELD VAL in OFS.SOURCE) is not set then this setting will
place all records in HLD status immediately, and no further validation or processing
will take place. If field validation is set (FIELDVAL=YES) then any field validation
errors will cause the record to be rejected while all other records will be put into
HLD status.
OFSSourceID: A valid ID held in the OFS.SOURCE table in T24(see example shown
below)
Data Library 44
Tool Box
OFS.SOURCE record
Overwrite: Can be set to True or False. This will instruct the T24 Data Library pro-
cess to overwrite existing Data Records during the ‘Upload’ process.
ServerDirectory: This is the server directory where the program files are located.
This MUST be a pre-existing directory as the T24 Data Library will not create it.
ZeroAuth: If this is set to TRUE then the record will be authorised after input by
OFS.
45 Data Library
Tool Box
Definition Designer
Overview
The Definition Designer can be used to create new or modify existing download
units. The designer allows users to attach data and program records to the down-
load unit.
Users must be signed-on to a T24 environment in the ToolBox application before
designing a download unit.
User Interface
Start Page
The ‘Start Page’ allows users to Open existing or create New server or local defin-
itions. It also lists recently opened local and server definitions. Clicking on these
items will open then in the ‘Designer’ tab.
The ‘Definition Designer’ Start Page
Data Library 46
Tool Box
The Definition Designer
The Definition Designer Application
Running the Definition Designer for the 1st Time:
After signing on to a T24 environment via ToolBox and invoking the ‘Definition
Designer’ a message will appear informing the user that the Application Menu must
be retrieved. This is message is only shown when the ‘Definition Designer’ is run for
the 1st time or the ToolBox is pointed to a different web server. This menu can be
‘refreshed’ at any time by selecting the ‘Refresh Application List’ menu item from
the ‘Edit’ menu.
The File List prompt
Adding and Removing T24 Data Items

Data items can be selected by locating the file in which they are based and check-
ing the checkbox next to it. You can use the Application List to browse for the
required files or by typing the name into the search box. Once the application has
been selected an entry for it will appear in the ‘Definition Explorer’ pane.
47 Data Library
Tool Box
Selecting CUSTOMER from the Application List
Using the Search/Add box to locate T24 Application files beginning with ‘CUS’.
Once the required file has been selected and displayed in the ‘Definition Explorer’
pane a user can add IDs to this file by clicking the ‘Add/Remove ID’ hyper-link dis-
played under it.
The resulting dialog box will list ALL the IDs in that file.
Data Library 48
Tool Box
The ID selection dialog box. Check the required IDs to select them.
Once the required IDs have been selected, click ‘OK’. The selected IDs will now be
shown under the corresponding file.
CUSTOMER file with attached IDs

The file unit can be removed or individual ID’s be removed by right-clicking on the
File Unit. The context menu will give two options:
1. Remove Unit
2. Remove ID
If ‘Remove Unit’ is selected and IDs are attached to that file, a confirmation mes-
sage will appear alerting the user that all ID’s attached to the file will also be
removed.
Using the procedure described above several files units can be defined.
T24 Program Items

Program items can be added to a download definition by selecting the ‘Search/Add’
button on the Search Bar. The ‘Program Code’ item should be selected from the
Combo box (as shown below).
Search/Add bar
49 Data Library
Tool Box
When clicked, this will show a dialog box prompting for the program ID and file.
These can be provided directly and ‘OK’ clicked.
Adding a Program ID
A new entry will appear in the Definition Explorer pane. Alternatively users can
search for a program file by specifying the file/directory and clicking the ‘Find…’
button. The resulting dialog will display a list of ALL the program IDs contained
within that file.
A user can select one or multiple program IDs displayed. When ‘OK’ is clicked the
selected program IDs will be added to the Definition Explorer pane.
Browsing and selecting multiple Program IDs

The ‘Find’ dialog also allows users to search for a program ID using specified cri-
teria. Enter search criteria and click the ‘Search Now’ button.
The program unit can be removed or individual program ID’s be removed by right-
clicking on the Program Unit. The context menu will give two options:
1. Remove Unit
2. Remove ID
Data Library 50
Tool Box
If ‘Remove Unit’ is selected and program IDs are attached to that file, a con-
firmation message will appear alerting the user that all ID’s attached to the file will
also be removed.
Using the procedure described above several program units can be defined.
T24 Object Code Items

Object Code items can be added to a download definition by selecting the
‘Search/Add’ button on the Search Bar. The ‘Object Code’ item should be selected
from the Combo box (as shown below).
Search/Add bar Object Code items

When clicked, this will show a dialog box prompting for the Object Code ID and file.
These can be provided directly and ‘OK’ clicked.
Adding Object Code

A new entry will appear in the Definition Explorer pane. Alternatively users can
search for a program file by specifying the file/directory and clicking the ‘Find…’
button. The resulting dialog will display a list of ALL the Object Code items con-
tained within that file.
A user can select one or multiple items displayed. When ‘OK’ is clicked the selected
items will be added to the Definition Explorer pane.
51 Data Library
Tool Box
Browsing and selecting multiple Items

The ‘Find’ dialog also allows users to search for an item using specified criteria.
Enter search criteria and click the ‘Search Now’ button.
The unit or individual items can be removed by right-clicking on the Unit. The con-
text menu will give two options:
1. Remove Unit
2. Remove ID
If ‘Remove Unit’ is selected and items are attached to that file, a confirmation mes-
sage will appear alerting the user that all ID’s attached to the file will also be
removed.
Using the procedure described above several object code units can be defined.
Data Library 52
Tool Box
Definition Runner
The Definition Runner can be used to ‘execute’ existing download definitions. The
Definition Runner will ‘Verify’ definitions stored on the DL.DEFINE T24 application.
The process will create the XML data units within the specified DL.DATA location.
This procedure can be performed ‘manually’ if required by opening DL.DEFINE,
selecting the required ID and Verifying it in the standard manner.
Since the processing is performed at the server user must be on-line when ‘running’
download definitions.
User Interface
Start Page
The Definition Runner start page.
53 Data Library
Tool Box
The Definition Runner
The Definition Runner Application
Running Download Definitions

From the Definition List select the download definition you wish to run/execute.
Ensure that it’s ID appears in the ‘Selected Definition’ box and either double click
the ID in the Definition List or click the ‘Run’ button.
A message will appear in the Result Output window describing the process action.
Once a definition has been successfully run/executed it is now ready for ‘down-
loading’.
Data Library 54
Tool Box
Unit Download
The Unit Download tool can be used to retrieve existing download units from the
T24 server to your local file system. The Unit Download lists all the available down-
load units held on the T24 system. Once selected; individual units can be down-
loaded locally. The Download utility displays the components held within each unit
and indicates the type of the component.
User Interface
Start Page
The Unit Download Start Page
55 Data Library
Tool Box
Unit Download Application
The Unit Download Application
Downloading Units
To download a unit select the required download ID displayed in the ‘Download
Units’ list. The component list will be refreshed to display the individual components
held within that Download unit.
The individual components can be viewed by double clicking on them. The file
viewer will display the contents of that component.
Data Library 56
Tool Box
The file viewer displaying the contents of a Program Unit

To download the complete download unit, ensure it is selected and click the ‘Down-
load’ button. The ‘Control Panel’ will show the progress and the ‘Summary’ Tab will
display the progress of each component. A report is also generated during the down-
load process and can be viewed and saved via the ‘Report’ tab.
57 Data Library
Tool Box
An example download report

Once downloaded, the components can be viewed either by navigating to the ‘Loca-
tion’ displayed in the summary tab using a File system tool such as Windows
Explorer or by double-clicking on the required component displayed in the ‘Sum-
mary’ tab and the Windows OS will attempt the open the file with the associated
application.
Since all the data items are now in an XML format and stored locally it should be
possible to manipulate this data as required or import them to a 3rd party system.
If these data records are modified they can be re-entered into the T24 system using
the ‘Unit Upload’ tool described next.
Data Library 58
Tool Box
Unit Upload
The Definition Upload can be used to upload downloaded units to a T24 envir-
onment. The Unit Upload will display your local data-library units and will give you
the option to commit/upload them to the current T24 server. It will display a sum-
mary of the progress and create an ‘upload’ report.
The upload process will use the ‘OFSSourceID’ specified in the Options to commit
the XML data record to T24. All data records input to T24 will be un-authorised and
must be authorised accordingly.
Since OFS is used to input data to T24 all new or modified uploaded data will utilise
the standard OFS audit trail. Also if OFS is unable to commit the data record the OFS
error message will be displayed in the upload summary and in the upload report.
Program files/units are created in the ‘ServerDirectory’ specified in the Options. By
setting the ‘Overwrite’ option to ‘True’ or ‘False’ users can instruct the Unit Upload
process what should be done if a program file already exists in that location. i.e. if a
program file exists in the ‘ServerDirectory’ and a program file with the same ID is
being uploaded, if overwrite is set to ‘True’ then it will be overwritten however if
set to ‘False’ it will not. The upload summary and upload reports will reflect all the
files that were or were not overwritten.
User Interface
Start Page
Unit Upload Start Page
59 Data Library
Tool Box
Unit Upload Application
Unit Upload Application
Uploading Units to T24

Before units can be uploaded to T24 the following Data Library Options MUST be
specified:
OFSSourceID: A valid ID held in the OFS.SOURCE table in T24. The SOURCE.TYPE for
this record should be set to ‘GLOBUS’
ServerDirectory: This is the server directory where the program files will be
uploaded. This MUST be a pre-existing directory as the T24 Data Library will not cre-
ate it. This will be the Target Directory for ALL program files.
Overwrite: Can be set to True or False. This will instruct the T24 Data Library pro-
cess to overwrite existing Program records found in the ‘ServerDirectory’ location
during the ‘Upload’ process.
CatalogObjectCode: If set to TRUE any Object Code that is uploaded will be auto-
matically catalogued using the jBASE ‘CATALOG’ command.
GTSControl: Controls how GTS and OFS will handle error conditions for activities
using the current version record.
ZeroAuth: If this is set to TRUE then the record will be authorised after input by
OFS.
Once these options have been set sign-on to the target T24 environment in ToolBox
and select the local Data-Library unit you wish to upload. The individual com-
ponents contained within the selected Data-Library unit will be shown in the
Data Library 60
Tool Box
components list. The file type is indicated and its upload order. The up-load priority
of individual components can be set by using the up/down arrows or by right-click-
ing on the component to be moved and selecting the appropriate option on the con-
text menu. In this manner components that have inter-dependencies can be
ordered accordingly and uploaded without OFS rejecting the record. The upload
order will be saved and retained with the upload unit.
Once the components have been ordered as required, the upload process can be
started by clicking the ‘Upload’ button in the control panel.
If a data item has a target of the FILE.CONTROL file then the Data Library upload
process will automatically create the new file in T24.
Upload of Program and Data units.

The upload summary pane will show the progress of the upload and display if it will
was successful or not. A full upload report is complied and can be viewed via the
report tab. It is important to remember that OFS is used when uploaded data library
units. Any unsuccessful uploads will display the rejection message produced by OFS.
Program files and Object Code are not subject to OFS input. These are simply
copied from the local directory and uploaded to the specified ServerDirectory. Pro-
grams are NOT complied after they have been uploaded. The user must compile
these using ToolBox DevStudio or using EB.COMPILE at the jBASE shell.
Object Code can be ‘Cataloged’ by the T24 Data Library by setting the Cata-
logObjectCode option to ‘True’. The jBASE ‘CATALOG’ command will be used to per-
form this.
Note: The Data Library upload process identifies Object Code by the
assuming that its ID will always begin with the '$' character.
61 Data Library
Tool Box
Dev Studio
Overview
The T24 DevStudio contains a set of productivity tools to aid T24 Developers. This
component can be used by both Temenos developers and external clients when writ-
ing T24 core or local developments. Since the T24 DevStudio is provided as a
ToolBox plug-in all pre-requisites for installing and running the ToolBox application
must be met.
The T24 DevStudio plug-in

DevStudio contains 5 main components:
l The Code Editor
l Project Explorer
l Visual Debugger
l Spy Session
l Command Session
Each of these components will be explained in this document.
l Setup
l The Code Editor
Dev Studio 62
Tool Box
l My T24 Projects
l The T24 Visual Debugger
l Spy Session & Command Session
63 Dev Studio
Tool Box
Dev Studio — Setup

The DevStudio Options can be accessed via the Options Icon shown in ToolBox or
via the Code Editor Tools Menu.
The Options Dialog

The Options dialog allows user to specify all required settings needed by DevStudio
alls user preferences such as colours and fonts to be specified.
The Options have been categorised into four sections:
1. Display Settings: to hold fonts & colours etc.
2. Locations: to hold local and server paths
3. Run Time Settings: to hold required settings
4. Your Details: to hold details required for Program locking.
The Options dialog displays a ‘Restore Defaults’ button that can be used to re-set
the options values if required.
Display Settings
Option Name Description
Background The Background Colour of the Code Editor.
CodeFont The Font Used in the Code Editor.
Comment The Colour Applied to Code Comments
CommonVariables The Colour Applied to T24 Common Variables
CurrentLineHighlight The Colour Applied to the Current Line Highlight
DescriptionText The Colour Applied to the Description Text within the
“<desc>…..</desc>’ tags
Foreground The Colour Applied to Normal Text
Dev Studio 64
Tool Box
HighlightCurrentLine If set to True the current line will be Highlighted

IndentationGuides If set to True a faint line will indicate the indentation
level
Keywords The Colour Applied to jBASE Keywords
MarkLineModifications If set to True a line will appear in the margin to indic-
ate a modification has occurred at that line.
Region The Colour applied to the region tags “<region name-
e=…..>…….</region>”
ShowLineNumbers If set to True the line number margin will be dis-
played
StringLiteral The Colour applied to all string literals i.e. text
between “” and ‘’.
Run Time Settings

AutoSaveInterval The Interval of the Auto-Save (In Minutes)
DebugPortNumber The Server Socket that the debug listener runs on
ServerIP The Server to connect to for the Spy and Command Ses-
sions
SpyPortNumber The Server Socket that the spy listener runs on
Your Details
Email User email address
Telephone User telephone number
Username User Name or ID
65 Dev Studio
Tool Box
The Code Editor

The code editor supports all of the features provided by the previous versions. It
provides an IDE (Integrated Development Environment) that performs many func-
tions. At a simple level, the code editor may be used as nothing more than a glor-
ified text editor that allows programs to be downloaded, modified and then saved
to the server and compiled.
User Details
The first time the Code Editor is launched a dialog will appear to prompt for user
details. One person can only edit server program files at any one time. This ensures
that different people do not make conflicting changes. In order to facilitate this a
locking mechanism has been created which registers which user has locked which
file for edit. Therefore, a User Name must be supplied when logging in to the T24
DevStudio. This should be clear enough that the person editing a particular file can
be identified should any problems occur. The Login screen also allows you to add
additional contact information, although this will not be stored in the jBASE data-
base at present.
When the OK button is pressed this information is saved to the T24 DevStudio
Options file. This information can be changed at any time via the Options Icon
found under the T24 DevStudio plug-in.
The user details dialog.
Dev Studio 66
Tool Box
The Development Environment
The Main Code Editor Window

The main screen is split into several areas:
1. The Tool Bar
2. The Main Pane
3. The Navigation Pane (Right hand pane)
4. The Tools Pane (Bottom pane)
The Tool Bar

The toolbar contains the most common buttons for performing editing commands.
Additional functionality is also available by using the right mouse button click while
in the editing area. This displays a list of commonly needed commands.
The toolbar contains the following buttons:
Icon Name Shortcut Description

Create a New Pro- Ctrl+N Creates a new program file on
gram the local PC.
67 Dev Studio
Tool Box
Open a Local Pro- Ctrl+O Opens a program file on the local

gram PC.This may be a new program
currently being developed or a
program previously fetched from
the server. If any files have been
opened or saved in past sessions,
then when the small down arrow
button is pressed a list of up to 5
file names are displayed. Select-
ing one of these files allows quick
access to previously used files.
Open & Lock a pro- Ctrl+Shift+O Launches the Open Server Pro-
gram from the gram dialog that will allow the
Server user to specify the program and
the location of the required pro-
gram for editing. The file is
marked as locked on the server
by an entry in the
EB.DEV.LOCKING application. If
any files have been edited in past
sessions, then the small down
arrow button is pressed a list of
up to 5 file names are displayed.
Selecting one of these files allows
quick access to previously edited
server files
View a Program Ctrl+Shift+V Fetches the specified program
from the server file from the server for viewing.
without Locking it The file downloaded will be read-
only.
Save Locally Ctrl+S Saves a program file on the local
PC. If not already supplied a des-
tination is prompted for. This but-
ton is only available for new
programs or programs that have
been locked on the server and
downloaded.
Save to Server Ctrl+Shift+S Returns the current program file
to the server. The file is saved on
the server.
Dev Studio 68
Tool Box
Compile F5 Saves the file locally before sav-

ing the file on the server ready
for compilation. The output from
the compilation is displayed in the
Output screen and any Tasks that
may result will be shown in the
Tasks Window.
Indent Ctrl+T Indents at the current insertion
point
Outdent Ctrl+Shift+T Outdents at the current insertion
point
Insert a Comment - Inserts a comment line at the cur-
Line rent insertion point.
Comment out the Ctrl+Shift+U Adds a comment directive to the
selected lines currently selected code.
Uncomment the Ctrl+Shift+U Removes any comment directives
selected lines from the currently selected code.
Jump to Line Ctrl+G Jumps to the specified line num-
ber of the program code
Refresh the Code Ctrl+R Refreshes the List pane as well as
Window re-processes the colouring of the
program code
Format the Code Ctrl+Shift+F Formats the program code by
indenting text that is of the same
statement level.
Print Ctrl+P Prints the current code.
Display the current Ctrl+I Displays a dialog showing the cur-

Program’s Locking rent locking information for the
info. currently open program.
Convert F.READ to Ctrl+Shift+C Converts an F.READ Statement
CACHE.READ into a CACHE.READ statement if
detected.
Toggle Bookmark - Adds or removes a bookmark to
the currently open program.
Go to Previous Book- - Jumps to the previous bookmark
mark if any
Go to Next Bookmark - Jumps to the next bookmark if
any.
69 Dev Studio
Tool Box
Clear Bookmark - Clears All defined bookmarks.
Go to Previous Modi- - Jumps to the Previous Modi-

fication fication mark if any.
Go to - Jumps to the Next Modification
Next Modification mark if any.
Clear All Modi- - Clears all Modification mark
fication Marks
The Main Pane

The main pane comprises of four Tabs. Each Tab performs a specific function:
Start Page: This page provides access to recently used Projects, Server & Local
Files. The first time the Code Editor is launched these will be empty, however as it
used any projects or source code opened is listed. To access theses items at any
time users can double-click to launch them.
Code: The ‘Code’ tab is the main editor window. This is where all source code can
be created and modified.
Code Only: The ‘Code Only’ tab will display the source code that is shown in the
‘Code’ tab but without detected comments i.e. all code minus the comments.
Regions: This page will display an expandable list of detected regions within the
code displayed in the ‘Code’ tab.
The Navigation Pane
The Navigation Pane

The Navigation Pane is split into several sections:
Dev Studio 70
Tool Box
Labels: Displays a list of all Label directives in the loaded program. Clicking on
these items will position the cursor at that point.
Inserts: Displays a list of all $INSERT directives in the loaded program. Clicking on
these items will position the cursor at that point.
Calls: Displays a list of a CALL statements in the loaded program. Clicking on these
items will position the cursor at that point. If there are multiple calls to the same
program then each time the item is clicked on the next occurrence is located.
Macros: Displays a list of Standards and User Macros and the Macro Control Panel.
Please see section on Macros in this document for further information.
Map: This is split into two sections ‘Structure’ and ‘Flow’. The ‘Structure’ will
attempt to graphically represent the structure of the loaded program in terms of
labels, gosubs, calls and gotos. The ‘Flow’ will attempt to graphically represent the
logical flow of the program in trems of labels, gosubs, calls and gotos. Clicking on
any of the items will position the cursor at that point.
Online Resources: Contains usefull URLS that a jBASIC developer may find useful.
Regions: Lists detected ‘Regions’ within the loaded program. Clicking on these
items will position the cursor at that point.
The Tools Pane
The Tools Pane

The Tools Pane is split into three sections:
l Task List: This will display any Warning, Error or Information level items after
a program has been compiled. Clicking on each item will position the cursor
at that point.
l Output: This displays all the raw output after a compile action and also
provides information after each action such as a Save or a Load.
l Find & Replace: Provides access to the find & replace control panel and a res-
ults page. Clicking on each item will position the cursor at that point.
Basic Features
Creating a New Program
To create a NEW program, click the ‘Create a New Program’ icon from the Toolbar
or select the ‘New’ menu item from the ‘File’ Menu.
71 Dev Studio
Tool Box
The New Program wizard will started and the user will be prompted to enter the
name for the New program. The wizard will allow the user to select if a template
should be used or a just blank program be created.
The New Program dialog. Once the user has input a name and selected whether a
template should be applied ‘Next’ should be clicked.
If ‘Use Template’ is selected then the user will be prompted with a list of templates
that can be applied.
Template Selection. The required prefix can be entered and DevStudio will apply
the prefix to required points within the template.
‘Finish’ should now be clicked and the program will be generated. The user is now
able to edit the program as required.
Opening a Program
The user is able to open both ‘local’ and ‘server’ programs. Local programs are
defined as all programs saved on the local machine and Server programs are
defined as all programs saved on the T24 server. To open local programs use the
‘Open Local File’ option and DevStudio will display a standard browse and select dia-
log so that the required file be specified.
To open a Server sided program use the ‘Open Server File’ option and DevStudio
will display the ‘Open Server File’ dialog
Dev Studio 72
Tool Box
The Open Server File dialog

The option is given to ‘Browse’ the directory specified. If this is clicked then DevStu-
dio will display a list of all programs found under that location.
The Browse Server dialog

The Browse Server dialog displayed the contents of the specified directory. The user
is able to search for specific files by using the ‘Search Now’ button. The required
operand can be specified and a value to search for.
Once selected the required program can be opened by clicking ‘OK’.
Editing the Code

Once the server of local program has been opened, the user may edit the program
as required. To further facilitate the user a context menu is provided on the main
editor screen that can be accessed by right-clicking within the editor area.
73 Dev Studio
Tool Box
The right-click context menu

The context menu provides standard editing options, cut, copy & paste. It also gives
the options to Open the selected text in the current session of a new session. Selec-
tion New session will open a new DevStudio code editor. A lock will be applied to
the program when it is opened. If the selected text does not match an existing pro-
gram DevStudio will be unable to resolve it and it will not be opened. If ‘View’ is
selected then the program will be opened in ‘Read-Only’ mode and a lock will not
be applied to that program.
The ‘Last Position’ option can be used to jump to the previous cursor (usually the
position of the cursur before an item was selected from the navigation tools.
Viewing Code on the Server

DevStudio allows programs to be opened in a ‘Read-Only’ mode. This means that
programs can be viewed but not modified. In this case a lock will not be applied to
the program and the user will be unable to modify the program displayed. This is
only applied to ‘Server’ programs.
Open and View Options provided by the ‘File’ menu
Saving Code
Once a program has been modified the user is able to save the program either to
the server or locally. The following options from the ‘File’ menu item can be used
to save a program to the server or locally:
Dev Studio 74
Tool Box
Save Options provided by the ‘File’ menu
Compiling Code
Only server programs can be compiled. The option to compile will be disabled for
local programs.
To compile a program select the ‘Compile’ toolbar item or select the ‘Compile’
menu item from the ‘Build’ menu. Once requested DevStudio will send a request to
the server to compile the program. Compilation output will be displayed in the ‘Out-
put’ tab of the Tools pane. Any warnings, errors or information messages will be dis-
played in the ‘Task List’ pane.
Compile Output
Compile Task List
Find & Replace
The Find & Replace console
75 Dev Studio
Tool Box
The Find & Replace facility in DevStudio allows users to specify values to find and
replace. The results are displayed and items can be clicked on to move the cursor to
that item.
Autosave
DevStudio has a built in Autosave mechanism. All auto-saved items will be saved in
the following location:
[LocalWorkPath]\Autosave\
The LocalWorkPath is specified in the DevStudio Options. A sub-directory will be
created called ‘Autosave’ and all programs will be saved to that location using the
specified AutoSaveInterval. All auto-saved programs will have a ‘.sav’ extension.
The DevStudio status bar will indicate if the auto-save has been successful or not.
The Auto-save complete message on the DevStudio status bar
Advanced Features
System & User Defined Macros
DevStudio is deployed with a set of Standard Macros. These Macros or code snip-
pets allow the user to rapidly insert commonly used code snippets. The standard set
of macros can be seen via the ‘Macro’ tab on the navigation pane.
To run a Macro the user can simply position the cursor at the required section in
the program. Select the Marco and either double-click on it or click the ‘Run’ but-
ton.
The ‘Macro’ Pane
Dev Studio 76
Tool Box
After the Marco has been run, any user prompts will be displayed and then the
code snippet inserted.
Users have been given the ability to create their own Macros. To create a Macro
click the ‘Create’ button and a dialog will be displayed that will allow the user to
design the required Macro.
The Macro Editor

The Prompts field holds the sets of questions that the user will be asked when using
this command. This is used to supply command data that will vary each time this
command is run.
In the case of the example above, a conditional debug command will be inserted
and the user must supply the operator. When more that one prompt is required,
each instance of the prompt should be placed on a new line. The prompts field is
optional. In this case just the text in the Text field is inserted directly in to the pro-
gram code pane. This facility is useful when common code is required to be inser-
ted but no differentiation is required in the text inserted.
The Text field holds the text to be inserted in to the program code when the ‘Run’
button is pressed from the Macro pane. This text should be inserted including any
new line characters that are required. The answers to the prompts are placed in the
‘<>’ placeholders, where ‘x’ is a number corresponding to the prompt number. The
prompt numbers start at 1, this matches with the answer to the first prompt line.
Creating GOSUBs
When writing a large and complicated program, a user may wish to move some
code in to a separate GOSUB within the same file. To do this the ‘Create Gosub’
item should be selected from the ‘Tools’ menu. The user may pre-select the code to
be moved into the Gosub before the ‘Create Gosub’ item is selected. If no text has
been selected then a new ‘empty’ Gosub will be created. On selecting this item the
following dialog is displayed:
77 Dev Studio
Tool Box
The Create Gosub dialog.

The name of the new GOSUB should be entered and an optional description. When
OK is pressed the selected code is moved to the end of the program code (or where
the previously ‘* ’ label has been inserted) and the selected code replaced with a
call to the new GOSUB.
Creating Regions
Regions are expandable and collapsible user defined areas. Regions help to organ-
ise programs logically and help with maintenance. It allows logical grouping of pro-
gram subroutines. Creating regions is done in a very similar manner as when
creating GOSUBs.
The Create Region dialog

A name and optional description should be supplied when creating the region. As
with GOSUBs if the user has pre-selected text then the new region will encapsulate
it. If the user has not then an empty region will be created.
The region code encapsulating some text. The region is shown expanded.
The same region but shown collapsed.
Dev Studio 78
Tool Box
The region as detected by the ‘Regions’ pane. Refresh should be clicked to re-fresh
this list.
Bookmarks & Modification Marks
Bookmark and Modification Mark navigation panel.

Users and declare Bookmarks within the open program by simply placing the cursor
at the required line and clicking the ‘Toggle Bookmark’ icon on the toolbar. A blue
bookmark icon will appear on the left hand margin.
A user defined bookmark.

The user can specify multiple bookmarks within the same program and use the Pre-
vious and Next bookmark icons to quickly navigate between them. All bookmarks
can be cleared by clicking the ‘Clear bookmarks’ icon.
Bookmark information will NOT be saved with the program. When you closed your
program user bookmarks are not maintained.
Modification marks appear as a highlight line next to every line that has been mod-
ified by the user since the program was opened. Rapid navigation between them is
provided and the user can reset these at any time by using the ‘Clear Modification
Marks’ icon. Again these marks are not saved when the program is closed.
Program Locking
As previously mentioned, in order that only one person edits server code at any one
time, a locking mechanism is used. This involves adding an entry to the jBASE applic-
ation EB.DEV.LOCKING. The key to this application is the program file name.
The underlying jBASE file used by the EB.DEV.LOCKING application is
F.EB.DEV.LOCKING.
The EB.DEV.LOCKING application has the following fields :-
Field Description Status

User Name The name of the user who locked the pro- Mandatory
gram file. Taken from the Login screen.
79 Dev Studio
Tool Box
Email Address The email address of the user who locked Optional
the program file. Taken from the Login
screen.
Contact Number The contact number of the user who locked Optional
the program file. Taken from the Login
screen.
Lock Date The date that the program file was locked. Mandatory
The fetching and returning of program code automatically locks and unlocks files.
However, the jBASE EB.DEV.LOCKING program can be used to view current pro-
gram locks, as well as unlock files that were locked by mistake or no longer need to
be locked.
The use of the Verify function on a EB.DEV.LOCKING record will remove the lock for
the specified program file. Please note that this should only be performed in emer-
gencies and only by a senior developer.
DevStudio provides a facility to Manage your individual locks and for you to view
the program lock information for the currently open program.
Lock management on the ‘View’ Menu item.

To display all Program locks maintained by the current user the ‘Program Locks…’
item should be selected. The following dialog will be displayed.
The Program Locks dialog.

This dialog gives user the facility to un-lock all or individual items. This dialog will
be automatically displayed to the user when all DevStudio code sessions are closed.
All locks are held on the T24 server so DevStudio will only attempt to retrieve them
if your ToolBox is signed-on.
To display the locking information for the currently open file then select the ‘Pro-
gram Lock Information’. A dialog will display the lock information for that program.
Dev Studio 80
Tool Box
The Program Lock Information dialog.

If a user attempts to open a locked program (that does not belog to them) then
DevStudio will display the Program Lock Information dialog but give the user the
option to open the program in a ‘Read-Only’ mode.
The user can click on the ‘Open as Read Only’ button.
81 Dev Studio
Tool Box
My T24 Projects
This component allows developers to group Server and Local program files into pro-
jects. It provides a useful interface to access these items and allows you to include
other project resource files such as Functional and Technical Specifications.
The Project Console
The T24 Project console

When ‘My T24 Projects’ is launched from ToolBox the T24 Project Console is dis-
played. This allows users the Open existing projects, Remove existing projects or
Create a New Project.
The project console displays the Name & Description of the selected project and
lists all files included within that project.
Creating a New Project

Once ‘New Project’ is clicked the New Project dialog is displayed:
The New Project dialog.
Dev Studio 82
Tool Box
The user can specify the name of the project, a description and a location. By
default the location will created from the LocalWorkPath option and the Project
Name.
Once ‘OK’ is clicked the Project explorer will be displayed:
The Project Explorer

The project explorer is empty so the user must add files to it.
Adding Files to your Project

To add server, local or any other file to your project select the ‘Project’ menu and
click on the ‘Add Project Item…’ menu item.
The ‘Project’ Menu

The following dialog will appear:
83 Dev Studio
Tool Box
Add Project Item dialog

If you wish to add a server file’ then select the ‘Server File’ Icon and click ‘Add’. If
you wish to add a local file then select the ‘Local File’ icon. If you wish to add any
other file such as a document, viso diagram, spreadsheet, project plan etc.. then
select the ‘Other File’ icon and click ‘Add’.
The Project Explorer will display the appropriate dialog to add the particular item.
Once items have been selected the Project Explorer will display the items within a
tree.
The Project Explorer showing different project items.

Each project item can be launch by double-clicking on it. All Server and Local Files
will be open by the DevStudio Code editor. All Other Files will be launched using the
associated application e.g. MS Word, MS Project etc.
Once all items have been added to the Project then it must be saved using the save
icon on the toolbar or the ‘Save Local’ option from the File Menu.
To remove an item from the project simply select it within the Project Explorer
right-click can select ‘Remove Item’ from the context menu. The item will be
removed.
The Project Explorer can be docked to the Left or Right of the Windows Desktop.
This allows the Project Explorer to be always visible and manage your DevStudio
and other application sessions.
To Dock the Project Explorer select the ‘Docking’ menu item and check the required
docking position from the menu.
Dev Studio 84
Tool Box
Project Properties
The Project Properties tab

Each project has the following properties:
Property Name Description

Description Short description of the current project
Project File This is the main file that hold ALL project information. This
is the file to open when you wish to open this project.
Project Folder The projects ‘working’ directory.
Project Name The name of the current project.
85 Dev Studio
Tool Box
The T24 Visual Debugger

The T24 Visual Debugger is a tool that allows users to interactively debug T24
routines within the stateless architecture.
It uses the jBASE Debugger engine and it supports ‘Most’ of its commands. The T24
Visual Debugger relies on the Temenos Connector Server (TCS) to redirect debug
output to a specified port.
The debugger eliminates the need for Classic sessions and provides ‘true’ debug-
ging for T24 Browser. Debugging via classic may not always produce the same res-
ults that you would get in Browser.
The T24 Visual Debugger allows users to step in & over code, set break points
including conditional breaks, watch variables etc.,
Pre-requisite Set-up
Before the T24 Visual Debugger can be used the T24 Browser, TCServer T24
account must be configured accordingly:
NOTE: The setup indicated in this document should be used as guide lines only.
Please refer to the documentation of each component for further information.
T24 Account:
Ensure that the environment variable is set in the T24 account that you wish to
debug:
JBASE_DEBUG_PIPE=1
This can be set in the .profile, environment.vars or remote.cmd
TC Server:
In the file ‘tcserver.xml’ found under the ‘conf’ directory ensure that the ADAPTER
that the T24 Browser channels are using has a <MAX_SESSION> value of at least 2.
An example would be:
<ADAPTER id="T24">
<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 1 </MIN_SESSION>
<TIMEOUT>3000</TIMEOUT>
<STARTIN>/stor-
age1/globus.accounts/globus.acc.2/srdevc.run</STARTIN>
<JBASEPATH>/usr/jbc</JBASEPATH>
<PROGRAM>tSS</PROGRAM>
<PARAMETER>WZ</PARAMETER>
Dev Studio 86
Tool Box
</ADAPTER>
T24 Browser:
In the file ‘BrowserParameters.xml’ found in the root of the Browser Application
the following values must be set:
<?xml version="1.0"?>
<browserParameters xmlns:xsi="http://www.w3.or-
g/2001/XMLSchema-instance">
<messageData>
<parameter>
<parameterName>Server Connection
Method</parameterName>
<parameterValue>INSTANCE</para-
meterValue>

</parameter>
<parameter>
<parameterName>Instance</para-
meterName>
<parameterValue>production</para-
meterValue>
</parameter>
.
.
Under the \WEB-INF\conf directory locate the file ‘BrowserConnection.xml’ and

ensure it contains an Instance name as defined above ‘production’ in this case.
Ensure that this instance defines the required channels as defined in ‘channels.xml’.
<instances>
<instance name="production">
<encrypt>false</encrypt>
<compress>false</compress>
<retryperchannel>2</retryperchannel>
<encoding></encoding>
87 Dev Studio
Tool Box
<verbose>false</verbose>
<channels>
<channel>browser.1</channel>
<channel>browser.2</channel>
</channels>
</instance>
</instances>
Starting the T24 Visual Debugger

Before the T24 Visual Debugger can be started the ‘Run Time’ options within the
DevStudio Options dialog must be provided:
DebugPortNumber:
This should be the same port number that the TC Server will redirect the Debugger
output to. This value is held in the ‘tcserver.xml’ file under the <DEBUGGER_PORT>
attribute.
ServerIP:
This should be the IP address of your host server.
Once these parameters have been supplied you should be able to start the T24
Visual Debugger. To do this, execute the ‘Visual Debugger’ icon shown in the DevStu-
dio tools suite.
The T24 Visual Debugger will attempt to connect to the IP address and port spe-
cified. Once completed a tray icon is created and an information balloon displays
the connection details. The main T24 Visual Debugger window also displays the con-
nection information and informs the user that it is awaiting a Debug statement:
The Debugger Listener Tray Icon & Information Balloon
Dev Studio 88
Tool Box
The Visual Debugger Main Window awaiting a Debug statement.
Debugging Your Programs

When using Browser to run T24 programs if a DEBUG statement is encountered nor-
mally your program will appear to hang and the an invalid response will be
received.
If however the T24 Visual Debugger is active a screen prompt and information bal-
loon will appear informing you that a DEBUG statement has been detected and will
ask you if you wish to launch the T24 Visual Debugger.
The Debugger prompt
The Debugger Listener has detected a DEBUG statement

If you click ‘Debug’ then the T24 Visual Debugger is launched. If ‘Continue’ is
pressed then the program will continue until a further DEBUG statement is detected
or until execution is complete.
89 Dev Studio
Tool Box
When ‘Debug’ is pressed the T24 Visual Debugger is launched and the source code
of your program is retrieved. (Ensure that you have signed on in ToolBox). The T24
Visual Debugger will display a dialog that will allow the user to specify the source
program to open. The T24 Visual Debugger will attempt to pre-fill the program
name and it directory if it is contained within the Debugger output.
Open Source dialog

Once the program has been opened the current line is highlighted and the user will
be able to use the debugger commands to step-over, step-in, set break points, con-
tinue etc as required. The ‘Debug’ menu item shows the commands that can be
executed.
Debugger Commands Menu
Dev Studio 90
Tool Box
The T24 Visual Debugger with source code loaded.

Once debugging is complete the T24 Visual Debugger will close and your program
should now be active.
Note: If you have taken a long time to debug your program you may
receive the following error message in T24 Browser:
T24 Browser response after a Time out has been reached.

This indicates that you have exceeded the time-out settings for the response. To
over come this problem set the time out values in Browser and in the TCServer to
higher values. Alternatively debug in an efficient manner so that you do not exceed
the time out threshold values.
Adding Watches
The T24 Visual Debugger allows user to evaluate variables by setting watches. The
lower pane of the main debugger window contains a ‘Watches’ section.
91 Dev Studio
Tool Box
The ‘Watches’ pane displaying some variables and their values.

Watches can be added to the list by clicking the ‘Click to Add..’ item. A dialog will
appear and will allow the user to enter the required variable name.
The ‘Add Watch’ dialog

Once ‘OK’ is clicked the variable will appear on the list. To evaluate that variable
simply select that item and click the ‘Refresh’ icon above it. The variable will be
evaluated.
If there are multiple variables in the list each must be ‘refreshed’ by the user indi-
vidually and each should be ‘refreshed’ manually during debugging.
Context Menu
The T24 Visual Debugger window provides a context menu to give access to com-
monly used commands. To access this menu right-click on the source code window.
T24 Visual Debugger Context Menu
Setting a New Breakpoint

The context menu can be used to set a breakpoint at a given line or a double-click
action can be used. For conditional breakpoints, use the ‘New Breakpoint’ item
under the Debug menu to display the following dialog.
Dev Studio 92
Tool Box
New Breakpoint dialog

Insert values as required and a conditional break point will be set at the specified
location.
Call Stack and Memory Allocation

The T24 Visual Debugger provides a Call Stack and Memory Allocation facility. Do
view these select the required option from the ‘Debug’ menu and each will be dis-
played in the relevant window. These can be refreshed at any time during the
debugger session.
The Call Stack
Memory Allocation
The Debugger Console

The T24 Visual Debugger provides a console (or a command line) where debugger
commands can be executed. To execute a command enter the command at the
command line and click the ‘Go’ button.
93 Dev Studio
Tool Box
The Debugger Console

The jBASE debugger can accept the following commands:
Command Syntax Description

< filename execute lines in filename as debugger commands
> filename write debugger status as debugger commands to file-
name
! Command execute Unix Command (!! to execute previous Com-
mand)
? help screen
nnn display line nnn of current source
a{bort} Executes an ABORT statement
b display Breakpoints
b nnn set Breakpoint at line nnn in current source
b nnn,filename set Breakpoint at line nnn in source filename
b {-gt} Variable set Breakpoint when contents of Variable changes
b {-gt} expr op expr set Breakpoint based on evaluation of expressions
c Continue program
d {-bdet} {nn|*} Delete {Enable/Disable} Trace/Break points
e filename Edit file filename and make it current source
end End program and return to shell
f {on|off} File name change status trace on/off
g Go - continue program
h {-rs{n}} {nn|on|off} History display and status
i {-v} Information in general
j {-g} Jump GOSUB stack display
l {-acf{nn}} {text} Locate text in current source
m {-v} Memory utilisation
Dev Studio 94
Tool Box
n {nn} display Next nn lines of current source

o log OFF this user
p display Path for current sources
p pathlist set Path for current sources (delimited by ':')
q{uit} Quit program, issue a STOP statement
r devicename Redirect debugger to devicename
s {-dtcg} {nn} Single step for nn lines
S {-dt} {nn} Single step for nn lines, same GOSUB and CALL level
stop Executes a STOP statement
t display Trace expressions
t {-gmrsv} expr set Trace expression
v {-gmrsv} {expr} display expression
w {nn} display Window of nn lines of current source
95 Dev Studio
Tool Box
Spy Session & Command Session

Due T24’s stateless architecture it has become increasingly difficult to determine
the status of each message going back and forth. There are many layers and com-
ponents involved and from a developers point of view it can be very time con-
suming to determine what has gone wrong.
The Spy Session allows developers to see all response messages sent from the T24
server.
The Command session allows developers to execute jBASE and shell commands
without the need for 3rd party terminal emulator software.
Dev Studio 96
Tool Box
Enquiry Wizard
Overview
The Enquiry Wizard allows you create enquiries in T24 through a simple guided
user interface. Customisation is minimal as to make the process quick and easy. The
Enquiry Wizard allows users to create customised enquires based on existing T24
applications. The Enquiry Wizard also allows users to delete existing enquires.
To be able to create new enquires you must be signed on in ToolBox.
The Enquiry Wizard can be launched from the Tool Box main screen, by going to
‘Designers and Wizards’ and double-clicking on the Enquiry Wizard icon.
The Enquiry Wizard can also be launched via the Tool Box tool bar, under Go
To>Designers and Wizards>Enquiry Wizard.
97 Enquiry Wizard
Tool Box
l Screen Design
l Known Issues
Enquiry Wizard 98
Tool Box
Screen Design
The wizard navigation buttons are placed at the top of the screen (similar to a web-
browser) and the wizard stages are shown below them. Each stage will be high-
lighted as the user progresses through the wizard.
Stage 1 – Enter Enquiry ID and Delete Enquiry

This stage allows users to specify the new enquiry ID to be created. The ID must be
unique as modifying an enquiry is not currently supported by this wizard.
Enter the ID you wish to create for you new enquiry in the field shown and click
‘Next’ (right arrow icon) to proceed to the next stage. The ID will be validated and
the next stage shown. If the ID specified already exists on the ENQUIRY application
in T24 then the user will be prompted to specify an alternative.
99 Enquiry Wizard
Tool Box
This stage also allows the user to delete an existing Enquiry. Click to the ‘Delete
Existing Enquiry’ button to display the ‘Delete Existing Enquiry’ dialog.
The ID of an existing ENQUIRY record can be given and click the ‘Delete Enquiry’
button to delete it.
Stage 2 – Enter Enquiry Details

Enter the T24 application you want to query. This can be any valid T24 Application.
Here you can also enter the Screen Title for the new enquiry in the second text
field.
Again if any of the data input by the user is not correct then the user will be promp-
ted to modify it before the next stage is displayed.
Note the ‘Previous’ button is now highlighted allowing the User to return to step
back and change the Enquiry ID in the previous stage.
Enquiry Wizard 100

Tool Box
Stage 3 – Select & Order Fields

On the left is a list of available fields, on the right is the list of fields that will
appear in the new enquiry. To add fields click the “Add Field” or “Add All” button,
and to remove field click “Remove Field” or “Remove All” button. The order in
which the fields appear in the enquiry can be changed by selecting the required
fields and clicking the up or down arrow buttons to modify it’s position in the list.
101 Enquiry Wizard

Tool Box
Stage 4 – Column Properties

The columns selected in the previous stage are displayed horizontally as they would
be on the submitted enquiry. Here the user can modify the header text i.e. the
column header by clicking on the text. An input box will be displayed and new text
can be entered.
This stage also allows the columns to be re-ordered. The column header can be
selected by holding the left-mouse button down and dragged to a new position.
Enquiry Wizard 102

Tool Box
Stage 5 – Summary
This stage displays a preview of how the enquiry will be displayed by T24 Browser.
The Enquiry ID is displayed and the file that it is based on.
If the preview is correct and displays all the required information in the correct
format then this enquiry can be created by clicking on the ‘Create Enquiry’ button.
If any corrections need to be applied then the ‘previous’ button (left arrow icon) can
be used to return to the previous stages to make necessary adjustments.
Stage 6 – Confirmation
If the enquiry definition has been accepted by T24 then this stage will provide con-
firmation. If any errors where encountered then they will be shown.
103 Enquiry Wizard

Tool Box
The user can create another enquiry by clicking ‘Next’ which will take the user back
to the beginning stage.
Enquiry Wizard 104

Tool Box
Known Issues
Description Solution
When creating an Enquiry Due to the workload the server processing time may
based on an Application exceed the time out threshold on the TC Server. In
that has a high number of this case it may become necessary to increase the
fields the column list is timeout threshold so that the response be sent to the
never returned. Enquiry Wizard.
105 Enquiry Wizard

Tool Box
Help Centre
Overview
The Help Centre provides convenient access to the help resources.
The Help Centre Plug-In

l Screen Design
Help Centre 106

Tool Box
Screen Design
T24 User Guides
Once this icon is executed the active connection profile will be used to locate the
T24 Portal. A web browser will be opened and directed to the T24 Portal as shown
below:
The T24 Portal Page

Please note that the T24 User Guides & Help Index must be installed on the T24
Browser application server. For information on how this can be done please refer to
the Browser Installation guide.
ToolBox User Guide

This will launch the ToolBox user guide. This document is in PDF format so to view it
Adobe acrobat reader must be installed. A PDF viewer can be downloaded and
installed from www.adobe.com.
Plug-In User Guides

This will launch the ToolBox help dialog where all user guides for ToolBox and
installed Plug-ins can be launched. Once again all documents are in PDF format so
a PDF viewer will be required.
107 Help Centre

Tool Box
The ToolBox help dialog

To launch the help file for the required plug-in the user can click on the hyper-links.
The PDF help document will be launched.
It should be noted that the ToolBox build information can also be accessed via this
dialog.
Temenos Online
This will open www.temenos.com in your web browser.
Help Centre 108

Tool Box
Screen Builder
Overview
The T24 Screen Builder allows rapid creation of T24 screens (VERSIONS) via a
simple wizard interface. The Screen Builder allows fields to be selected and ordered
as desired. Screen layout is controlled by pre-defined templates that can be selec-
ted.
NOTE: The Screen Builder can be used to edit existing screens. The ‘Screen
Designer’ application should be used if advanced screen layouts are required. The
‘Screen Designer’ can be used to create and edit T24 screens. See the Screen
Designer User Guide for further information.
l Screen Design
109 Screen Builder

Tool Box
Screen Design
Navigation buttons are placed at the bottom of the screen. Finish will not be
enabled until a screen has been defined in the Screen Builder. The steps required to
complete the creation of a T24 Screen are listed on the left hand side.
Step 1 – Welcome Screen

Below is a screen shot of the welcome screen, this gives an overview of the func-
tionality and navigation instructions.
Step 2 – Screen ID
The ID must be unique as modifying an existing screen is not supported.
The id must be in the format “<T24 application name>,<version name>” note the
comma between the application name and version name.
The Hide Settings option offers OFS.SOURCE and INPUT VERSION options.
Screen Builder 110

Tool Box
Step 2 – Select Languages

Languages and be selected tick ticking the box on the left. At least one language
must be selected.
111 Screen Builder

Tool Box
Step 3 – Screen Settings

This is where the screen can be given a title and the number of authorisers is spe-
cified. A title is not required. The number of authorisers is the number of times a
record created using the screen will have to be authorised.
Screen Builder 112

Tool Box
Step 4 – Field Selection

appear in the new screen. To add fields click the “Add Field” or “Add All” button,
and to remove field click “Remove Field” or “Remove All” button. The order in
which the fields appear on the screen can be changed by clicking (to move
field up) or to move the field down.
The order in which the field list is displayed can be sorted by Field Number or field
name.
Step 5 – Field Properties

The list of chosen appear on the left, on the right is the property editor, where the
settings for each field can be changed.
Prompt Text
This is the name that will appear to the left of the field input area.
Tool Tip
When the user moves the mouse over the field this text will appear in a tool tip.
Enquiry Selection
Place any filter you may want to apply to the “Drop Down List”.
113 Screen Builder

Tool Box
Drop Down List

This should be an enquiry, this provides the user with a selection instead of having
to remember and type in the id of the relating file.
Enrichment
Settings this to false will cause any description next to the field not to appear.
Hyperlink
Setting this will make the field label a hyperlink, setting this to the name of an
application will launch an application as with an enquiry.
Mandatory
Specifies weather the user can commit the contract is the field is left empty.
No Change
If set to true the user will not be able change the contents of the field.
No Input
If set the user will not be able to input data into the field, instead just display the
data.
Re Key
If set the user has to re input the field value before committing the contract.
Display Type
Settings this will cause the field to display as a check box or toggle button, this
should only ever be set when the field has only 2 possible values.
Hot Field
If set in browser the field is validated after the user moves to the next field.
Screen Builder 114

Tool Box
Step 6 – Template
One column – Descending Field Order
This will sort the selected fields in one column in the order in which they appear in
the ‘Screen Fields’ list.
Two Columns – Descending Field Order

This will sort the selected fields in two columns using a descending pattern in the
order in which they appear in the ‘Screen Fields’ list. The Screen Builder will
attempt to make both columns equal in depth.
Two Columns – Pan-Descending Field Order

This will sort the selected fields in two columns using a pan-descending pattern (i.e.
left to right) in the order in which they appear in the ‘Screen Fields’ list. The Screen
Builder will attempt to make both columns equal in depth.
115 Screen Builder

Tool Box
Step 7 – Summary
A summary of the information gathered is display at this stage. When click “Next”
the information is submitted to T24.
Screen Builder 116

Tool Box
Step 8 – Confirmation
This step will display “Txn Complete:” if the screen has been created as per below.
If however it fails validation any errors will be displayed in this screen and the user
can click the ‘Previous’ button to correct any errors.
Clicking finish will exit the Screen Builder.
117 Screen Builder

Tool Box
Branch Administration Console

Overview
Branch Resilience (BR) is a backup system for branches to be used when com-
munications (comms) to the head office system are interrupted due to unforeseen
events such as adverse weather conditions (hurricanes, tornados or flooding) or
other disaster scenarios.
It should be noted that without permanent communication links it is not possible to
run a full branch service (as if the link between the branch & head office was in
place). The BR module will be used by the branch to provide the best service to its
clients that is possible whilst communications are broken and to assist in re-estab-
lishing the data at the head office that is needed for branch operations to continue.
The Branch Administration Console is a key component in the Branch Resilience
mechanism.
The ‘Branch Administration Console’ Plug-In

l Administration Console
Branch Administration Console 118

Tool Box
Administration Console
The Branch Administration Console should be used by Branch Managers to perform
the following tasks:
l Monitor Branch Connectivity (comms)
l On-line/Off-line switching
l Branch Administration (online & offline) e.g. Data Upload, Date Rollover etc.
l SFQ Posting
For detailed information on Branch Resilience & the Branch Administration Con-
sole, refer to the following user guide:
[Functional\Core] Branch Resilience
The Branch Administration Console Connectivity Monitor.
119 Branch Administration Console

Tool Box
Rules Designer
Overview
The Rule Designer allows users to construct simple rules through an intuitive graph-
ical interface.
The ‘Rule Designer’ Plug-In

l Setup
Rules Designer 120

Tool Box
Rules Designer — Setup

Before the Rule Designer can be used, the T24 Rules Engine must be set-up and con-
figured within the T24 environment.
For information on how this can be done, refer to the following user guides:
[Sys Admin] T24 Rules Engine Installation Guide
[Sys Admin] T24 Rules Engine Configuration Guide
For a detailed guide on how to use the T24 Rules Engine and Rule Designer Plug-In
refer to the main user guide:
[Functional\Core] Rules Engine
The ‘Rule Designer’ Start Page.
121 Rules Designer

Tool Box
Screen Designer
Overview
The T24 Screen Designer application enables VERSIONs to be created in T24
through a simple user interface. The Screen Designer provides a ‘design surface’
upon which the required fields can be positioned, and provides a series of tabbed
screens for field and screen settings to be applied.
T24 Screen Designer

l Launching T24 Screen Designer
l Screen Wizard
l Design View
l Screen Settings
l Saving Screen
Screen Designer 122

Tool Box
Launching T24 Screen Designer

Screen Designer is accessed via the T24 Toolbox Designers and Wizards plug-in:
T24 Toolbox
Ensure you have signed on to a T24 environment and execute the ‘Screen Designer’
by double-clicking on the ‘Screen Designer’ Icon. The Screen Designer will load and
request information from T24. A splash screen will appear as follows:
123 Screen Designer

Tool Box
Screen Designer Splash screen

If this splash screen does not appear and the following message is displayed on the
Screen Designer start page then is indicates that the server you are connecting does
not have the correct functionality installed.
Screen Designer Start Page
Start Page
The Start Page tab provides the facility to create or edit a screen design. A new
screen design is created by entering a Screen Id and clicking the ‘Open Screen’ but-
ton.
Selecting an existing screen design can be performed in the same way or altern-
atively, from the list of ‘Recent Screens’ or by clicking on the ‘Find a Screen…’ link.
The Screen Id is the same format as the Id of VERSION records. (E.g.
CUSTOMER,CLIENT)
The Start Page also provides a link to the ‘Screen Wizard’. See the ‘Screen Wizard’
section in this document for further information.
Screen Designer 124

Tool Box
T24 Screen Designer Start Page
125 Screen Designer

Tool Box
Screen Wizard
The Screen Wizard is an application that allows screens to be created using pre-
defined layout templates. The wizard can be used to select and order the fields on
the screen and apply them in a consistent manner. The Screen Wizard can be
launched via the ‘Start Page’ or from the ‘Tools’ menu bar item. The Screen Wizard
allows rapid creation of standard screens.
Stage 1: Select a Screen ID
Selecting a Screen ID
This stage provides the options to create a New Screen ID or select an Existing
Screen ID. If the ID is already known then it can by typed directly into the Screen Id
field.
New ID & Find Existing dialogs

Once an ID has been specified the ‘Forward’ button should be clicked to show the
next stage. A request to the T24 server will be made to retrieve the Base fields for
the application specified, (CUSTOMER in the example above). The Base fields will
be loaded into the ‘Available Fields’ list in the next stage.
Screen Designer 126

Tool Box
Stage 2: Choose & Order Screen Fields

appear in the screen. To add fields click the “Add Field” or “Add All” button, and to
remove field click “Remove Field” or “Remove All” button. The order in which the
fields appear on the screen can be changed by clicking (to move field up) or
to move the field down.
Select and Order the Screen Fields

The order in which the field list is displayed can be sorted by Field Number or Field
Name.
Once the required fields have been selected click the ‘Forward’ button to move to
the next stage
Stage 3: Select a Template

Currently the Screen Wizard supports 3 common templates. The templates define
how the screen fields will be positioned.
127 Screen Designer

Tool Box
3 common templates for the screen fields layout

One column – Descending Field Order
This will sort the selected fields in one column in the order in which they appear in
the ‘Screen Fields’ list.
Two Columns – Descending Field Order
This will sort the selected fields in two columns using a descending pattern in the
order in which they appear in the ‘Screen Fields’ list. The Screen Wizard will
attempt to make both columns equal in depth.
Two Columns – Pan-Descending Field Order
This will sort the selected fields in two columns using a pan-descending pattern (i.e.
left to right) in the order in which they appear in the ‘Screen Fields’ list. The Screen
Wizard will attempt to make both columns equal in depth.
Once a template has been selected the ‘Forward’ button should be clicked to go to
the next stage.
Screen Designer 128

Tool Box
Stage 4: Submit
Confirmation Screen
To submit this definition to the Screen Designer the ‘Create Screen & Exit Wizard’
button should be clicked.
Once this has been clicked the Screen Designer will build the screen fields accord-
ing to the template selected.
The Screen Designer displaying the Screen as specified in the Screen Wizard
Further modifications to this screen can be made as desired using the Screen
Designer. Once complete it should be saved to T24 by using the Save function.
129 Screen Designer

Tool Box
Design View
When a new screen is created, the Designer tab is presented with a blank design
surface. In the event of an existing screen being opened, the fields defined on the
version record are placed on the design surface.
Designer Tab
The Designer tab provides a design surface onto which the required fields, com-
ments or lines can be placed. This can be carried out in one of three ways: -
l Drag and drop a Base Field on to the design surface
l Single click on a Base Field. Place the cross hair at the required position on
the design surface and single click
l Double click on the Base Field. (Field is placed in the top left corner of the
design surface)
Once the fields have been placed on the design surface they can be repositioned
using ‘drag and drop’ facility.
The column position of each ‘Input Box’ can be adjusted independently by selecting
the ‘Input Box’ and using ‘drag and drop’. Resizing of the ‘Input Box’ is achieved by
selecting the ‘Input Box’ and adjusting the length using the side squares.
It is also possible to move multiple fields simultaneously. To do this, select multiple
fields by: -
l Pressing the <CTRL> key and clicking on each field. Or
Screen Designer 130

Tool Box
l Draw a box around the required fields by keeping the left mouse button
depressed whilst moving the mouse.
The selected fields can then be moved to the required position
Fields can be removed from the design surface by selecting them and pressing the
delete button.
Reposition/Resize Input Box
Base Fields
When a screen is opened, the ‘Base Fields’ pane is populated with the available
fields for the T24 application that the screen is based upon. The Base Field Prop-
erties pane displays the properties of the selected field in the Base Fields pane.
131 Screen Designer

Tool Box
Base Fields
The Base Fields pane visually displays information about each field so that a
designer can determine how the application is constructed and design the screen in
an appropriate manner. An icon is placed before the field name to indicate the fol-
lowing:
Icon Description
Indicates a mandatory field, the field name will also be in displayed
in red.
Indicates an inputtable field.
Indicates a non-inputtable field, the field name will be displayed in

dark grey.
Indicates an inputtable Language field
Indicates that this field is a dropdown
Screen Designer 132

Tool Box
Indicates a local reference field
Indicates this field is a multi-valued field

Indicates the multi-value group. The group indicator will span two or
more fields.
133 Screen Designer

Tool Box
Screen Settings
Screen Fields
The Screen Fields tab is used to apply the settings for individual fields. Selecting a
field on the design surface displays the related field settings in the Screen Fields
tab. These settings can be amended and fall into the following categories and cor-
respond to related field in the VERSION application: -
l General Field Settings
l Field Dropdown List
l Automatic Defaulting
l Field Validation
l Other Attributes
General Field Settings
Screen Designer 134

Tool Box
Field Dropdown List

Clicking on the ‘Set Field Defaults…’ link presents the Field Defaulting window. This
allows Auto Old Content and Auto New Content to be defined for the selected field.
This feature also caters for Multi value and Sub value fields. The ‘Save’ button
should be clicked to save the Field Defaulting settings for each field
135 Screen Designer

Tool Box
Automatic Defaulting
Field Validation
Screen Designer 136

Tool Box
Other Attributes
Non Screen Fields

The ‘Non Screen Fields’ pane allows customisation of field settings that have not
been added to the design surface. A typical example of this scenario is that some
field values may be automatically defaulted by your screen and the user does not
need to see them or in fact even be aware of them. These fields will not be visible
on the screen so the designer provides this pane so that this type of scenario can be
defined.
137 Screen Designer

Tool Box
Non-Screen Fields
Available Base fields can be ‘dragged and dropped’ from the field list into the Non-
Screen fields pane and by double-clicking on entry the following dialog will be
presented:
Non-Screen Field settings

Using this dialog various properties can be set.
Question:
How can a Non-Screen Field be set to Non Inputtable, Re-Key or No Change if the
field object is not available on the screen to the user?
Screen Designer 138

Tool Box
Answer:
These can be defined to allow inheritance of field settings. For example, if this field
appears on any of the sub-tabs (associated versions) then these settings will be
applied to that field. This technique allows generic screens to be defined and the
appropriate field settings are applied in the context of the main screen.
TIP: If a field has been defined on the main screen and also on the any of the sub
tabs (associated versions) then all settings that have been defined on the main
screen will be applied to that field wherever it appears.
The dialog shown in figure 7.1 also provides a link to set the field defaults. By click-
ing on the hyper-link the following dialog is displayed:
Field Defaulting
The Field Defaulting dialog allows Auto Old Content and Auto New Content to be
defined for the selected field. This feature also caters for Multi value and Sub value
fields. The ‘Save’ button should be clicked to save the Field Defaulting settings for
each field
Screen Details
The Screen Details tab defines the overall settings for the VERSION. These settings
fall into the following categories: -
l Screen Languages
l Headers & Titles
l Screen Validation
l Printing Settings
l Behaviour & Layout
Selecting the ‘Define Screen Languages’ link displays the following window where
language settings are defined: -
139 Screen Designer

Tool Box
Screen Languages
Selecting the ‘Define Screen Validation Routines’ link displays the Screen Validation
tab where validation routines are applied to the VERSION: -
Screen Designer 140

Tool Box
Validation Routines
Selecting the ‘Set Screen Print Settings’ link displays the following window where
Deal Slip Printing settings are defined: -
Deal Slip Printing

The ‘Behaviour & Layout’ Menu defines the number of authorisers for the version,
and the next version to be launched if required (e.g. when designing a CUSTOMER
version, an ACCOUNT version could be applied to the ‘Next Version’ which will be
launched after Customer data has been entered)
141 Screen Designer

Tool Box
Behaviour & Layout

Selecting the ‘Set Associated Versions’ link displays the following window where
associated versions can be added to the VERSION. These are displayed in tabbed
format: -
Associated Versions
In the above example the associated Versions are then displayed when utilising
CUSTOMER,DISPLAY: -
Screen Designer 142

Tool Box
CUSTOMER,DISPLAY displaying Associated Versions
Screen Validation
Validation routines for the VERSION are defined under the Screen Validation tab.
This tab can also be accessed from the ‘Define Screen Validation Routines’ link
under the Screen Details tab. These routines are executed at different stages. E.g.: -
l Input.Routine – Executed at the commit stage of a transaction processing
using I, C, V, R or H functions as the final stage before updating the unau-
thorised file.
l Auth.Routine – Executed at the authorised stage of transaction processing, as
the final stage before updating authorised files.
The following example illustrates the addition of validation routines: -
143 Screen Designer

Tool Box
Validation Routines
Advanced Settings
The Advanced Settings tab defines additional Screen settings as illustrated in the fol-
lowing example. These correspond to the related fields in VERSION: -
Screen Designer 144

Tool Box
Advanced Settings
145 Screen Designer

Tool Box
Saving Screen
Screen Designs are submitted by clicking the ‘Save’ button. If the definition is valid
a ‘Save Response’ dialog will be displayed as follows:
Successful Save
If for any reason the definition is correct and can not be saved then any errors will
be displayed in the ‘Tasks’ panel.
Definition problems to correct

A ‘Save As’ option also exists in the File menu to change the Id of the screen. The
base application part of the Id cannot be changed.
Screen Designer 146

Tool Box
Save Screen As
147 Screen Designer

Tool Box
System Monitor
T24 Enterprise console is deprecated since R09 GA. please refer T24 Monitor for the
new Monitoring solution of R09
Overview
The System Monitor ToolBox plug-in provides a facility to monitor the TC Server
activity and also view the connectivity status of the key T24 system components.
The existing java TC Monitor functionality that is provided with the TC Client &
Server package will be replicated in the T24 Monitor plug-in.
The System Monitor plug-in provides access to the following components:
T24 Monitor Manager: An application to define and mange multiple T24 Monitor
configurations
T24 Monitor: The graphical monitor of TC Server activity
T24 Connectivity: An application to display the connectivity status of the T24
Browser web server, TC Server and T24 system.
System Monitor 148

Tool Box
l T24 Monitor
l Monitor Manager
l System Connectivity
149 System Monitor

Tool Box
T24 Monitor
The T24 Monitor can be launched by clicking on the ‘T24 Monitor’ icon of via the
‘T24 Monitor Manger’. When the T24 Monitor is launched directly via the icon a dia-
log will by shown requesting the required configuration.
The host is the IP Address of the TC Server and the Port is the Monitor Port that is
defined in ‘tcserver.xml’. The description can be used to identify this TC Server.
Once the details have been supplied the click ‘OK’ and the T24 Monitor application
will be launched.
The T24 Monitor application
System Monitor 150

Tool Box
Monitor Legend
Along the X axis the value is set as time in seconds , the Y axis has no labelled
description but inherits the label from the legend, both X and Y axis are self scaling.
Below is the Legend attached to each path is a different value, T24’s value is in mil-
liseconds, Total Transactions is in single units. The symbols used in the ledged can
be changed by selecting the option Reload Config found under the toolbar directory
File.
Monitor Statistics
Under the graphic consol is the numeric interpretation of the graph above.
Here the active listener is T24, the columns are re-sizable and the graphic paths
related to the listener can be hidden or displayed with by clicking the tick box on
the left.
TC Server Control
From the T24 Monitor the TC Server can be restarted and stopped.
NOTE: Once the TC Server is stopped it can not be restarted from the T24 Monitor.
A system administrator must re-start it via the TC Server shell or batch file.
These options are available from the toolbar directory Server and the Monitor tab.
151 System Monitor

Tool Box
Monitor Configuration
The T24 Monitor displays the listeners and adaptors that have been defined in the
TC Server set up
By left clicking on any of the adaptors or listeners in the Configuration tab the main
screen will list the associated adaptor group with the listeners present.
Here the Listeners can be enabled or disabled.
System Monitor 152

Tool Box
153 System Monitor

Tool Box
Monitor Manager
The T24 Monitor Manager can define multiple configurations that the T24 Monitor
application can use. The T24 Monitor Manger can be used to define multiple con-
figurations and be used to launch them.
Creating a Configuration
To create the T24 Monitor configuration, launch the T24 Monitor Manager and
click the ‘Create’ link at the bottom left hand corner of the screen.
A dialog box requesting the TC Monitor settings will be shown and must be com-
pleted before the configuration is saved.
The Name and Description fields can be populated with anything the user requires,
the host details in this case are the Host or Service name that is to be monitored (IP
System Monitor 154

Tool Box
address), and the Port Number must be the Monitor Port number found in the
‘tcserver.xml’ file in the tcserver install directory under the ‘conf’ directory.
Once the details of the new profile have been approved the profile appears along
side others in the profile and can be launched by focusing the cursor on the
required profile and clicking on Start in the top left hand corner. This will launch the
T24 Monitor application for that configuration.
155 System Monitor

Tool Box
System Connectivity
The ‘T24 Connectivity’ application can be used to graphically display the con-
nectivity status of the key T24 system components.
The T24 Connectivity application tests the status of the following components:
l T24 Browser web container - This is the path to the URL as defined in the
selected ToolBox connection profile.
l TC Server - This is the TC Server as defined by the configuration given, the IP
address (or host name) and the TC Server monitor port number
Note: The TC Server feature is used by pre-R09 users and the

latest users may ignore this feature.
l T24 System - The T24 environment as defined in the TC Server configuration.

The T24 Connectivity application can be used to test if all the above components
are available i.e. reachable from the current ToolBox location.
Launching the Application

Double click on the T24 Connectivity icon and a dialog will appear requesting the
connection profile to use. The IP address (or host name) that the TC Server is
deployed on and the TC Server Monitor port as defined in the TC Server con-
figuration.
Once these details have been supplied click the ‘Test >>’ button to launch the T24
Connectivity application.
System Monitor 156

Tool Box
Monitoring Connectivity
The T24 Connectivity Monitor displays an animated diagram of, ToolBox, Web
Server, TC Server and T24 Server components. It also displays Adapter information
received from the TC Server configuration and T24 System Information received
from the T24 environment.
If all information is displayed and the diagram is fully animated then the currently
selected connection profile (URL) is valid and ToolBox is able to fully communicate
with The T24 environment.
The T24 Connectivity Monitor functions by sending requests to each component and
analysing the response. The requests are sent at a user defined poll interval.
The Web Server is polled, the TC Server is polled and if both are successful then the
T24 Server is polled. If all poll results are successful then full connectivity is con-
firmed.
Connectivity Scenarios
Unable to resolve the Web Server (URL)
This situation may occur if an invalid URL has been defined in the selected con-
nection profile or the web server is down. The T24 Connectivity Monitor will display
the following:
157 System Monitor

Tool Box
The link to the web server is broken and the link between the TC Server and T24 is
broken, however the link between the web server and TC Server is active.
This reflects the scenario where the TC Server is reachable and as observed the list
of adapters has been returned for the defined TC Server.
Since the T24 Connectivity Monitor is unable to retrieve data from the T24 envir-
onment, note that the T24 System Information displays ‘Unreachable’ the link
between TC Server and the T24 Server is broken.
Unable to resolve TC Server

This situation may occur if the configuration provided for the TC Server is in valid or
the TC Server service is not running / available.
The link to the web server is active indicating that the URL is valid and the T24
Browser web application is available. The link between the Web Server and the TC
Server is broken as the TC Server is unreachable. Notice that no adapter
System Monitor 158

Tool Box
information has been retrieved and all T24 System Information is unreachable. The
link between TC Server and the T24 Server is broken as the TC Server is unreach-
able.
Unable to resolve the Web Server & TC Server

In this scenario ToolBox is unable to resolve paths to both the Web Server and the
TC Server.
All links are broken.
Configuration should be checked and the availability of services should be con-

firmed.
Monitor Interval
Under the ‘Tools’ menu item the ‘Poll Interval’ can be set. A dialog is shown where
the user can set a poll interval. This will control how often the T24 Connectivity
Monitor will check for service availability.
159 System Monitor

Tool Box

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tool Box

Uploaded by

Copyright:

Available Formats

Tool Box

Release: R19 AMR

Information in this document is subject to change without notice.

© 2019 Temenos Headquarters SA - all rights reserved.

The T24 Visual Debugger 86

Tool Box — General

Tool Box — General 6

Install of .NET required

7 Tool Box — General

System Requirements for Installing .NET Framework 3.0 and T24

Tool Box — General 8

9 Tool Box — General

Tool Box — General 10

The User Options Dialog

11 Tool Box — General

The User Options Dialog showing connection address components

Tool Box — General 12

13 Tool Box — General

Note: If multiple connection profiles have been specified the ‘Profile’

The T24 Toolbox Sign-On Screen

Tool Box — General 14

A Security Violation Error Message

Connection Error Messages

Error Message Cause

15 Tool Box — General

Security Violation Incorrect username or password has been sup-

Tool Box — General 16

Creating & Editing a Connection Profile

Creating a new connection profile.

17 Tool Box — General

Connection Profile context menu

Selecting a Connection Profile

Tool Box — General 18

The T24 Toolbox Interface

19 Tool Box — General

Plug-in tool tip

Tool Box — General 20

Item tool tip

Plug-In Item Display

21 Tool Box — General

Switching Plug-In Item views from 'Large' to 'Small' Icons

Menu Bar Actions

Tool Box — General 22

The Menu Bar

The ToolBox About dialog.

23 Tool Box — General

System Tray Actions

Tool Box — General 24

Plug-In Item Context Menu

The Item Context Menu

25 Tool Box — General

Tool Box — General 26

The ToolBox Help dialog

27 Tool Box — General

Accessing the Communication Logger

The communication logger application system tray icon.

Communication Logger’s Menu

Tool Box — General 28

The communications logger application

29 Tool Box — General

The error reporter

Example Error Report

Tool Box — General 30

Composite Screen Builder