TBOX1 T24 ToolBox Customisation Components R10.01
TBOX1 T24 ToolBox Customisation Components R10.01
01
Trainee notes
What is it:
ToolBox can be viewed as a container/placeholder for specialised T24 Tools & Utilities.
It provides the user with a rich user interface (UI) that allows them to interact with T24 to access certain
functionality.
It is designed to be expandable and employs the concept of Plug-Ins. The ToolBox framework will allow
3rd parties to write their own Plug-Ins.This will be possible as and when the strategic decision is made
by Temenos.
What does it do:
Currently ToolBox encompasses a few of the well known Desktop designers such as the Enquiry Wizard.
DevStudio contains a set of productivity tools including new Development Environment, a Visual Debugger,
Spy and Command Session all aimed at helping T24 Developers code, debug and maintain T24 port.
The T24 Monitor contains tools to monitor TCS and test the connectivity path to T24 through TCS.
Port numbers for debugger, Spy and Monitor port can be found in tcserver.xml file under conf dir.
It is important to highlight what ToolBox DOES NOT DO and that is any contract input, enquiry display or
COB.
Why should I use it:
Since some advanced Desktop functionality is technically difficult to replicate under a Browser architecture,
ToolBox, and its Plug-Ins have been designed to replace them.
It provides the Rich User Interface that users demand and allows the users to intuitively interact with it.
ToolBox fits neatly within the T24 architecture as it uses the same communication protocol/channel as T24
Browser.
Users will be able to use ToolBox just by specifying the URL that you use for your T24 Browser. Its that
easy!!!
The two pre-requisites for ToolBox are:
1. Microsoft .NET framework
2. T24 Browser.
Note: T24
ToolBox communicates with the T24 web server using the http protocol,
sending and
receiving XML messages. The T24 web server will use the T24 connector to rely these
messages to the T24 system.
What is it:
ToolBox can be viewed as a container/placeholder for specialised T24 Tools & Utilities.
It provides the user with a rich user interface (UI) that allows them to interact with T24 to access certain
functionality.
It is designed to be expandable and employs the concept of Plug-Ins. The ToolBox framework will allow
3rd parties to write their own Plug-Ins.This will be possible as and when the strategic decision is made
by Temenos.
What does it do:
Currently ToolBox encompasses a few of the well known Desktop designers such as the Enquiry Wizard.
DevStudio contains a set of productivity tools including new Development Environment, a Visual Debugger,
Spy and Command Session all aimed at helping T24 Developers code, debug and maintain T24. The
T24 Monitor contains tools to monitor TCS and test the connectivity path to T24 through TCS.
It is important to highlight what ToolBox DOES NOT DO and that is any contract input, enquiry display or
COB.
Why should I use it:
Since some advanced Desktop functionality is technically difficult to replicate under a Browser architecture,
ToolBox, and its Plug-Ins have been designed to replace them.
It provides the Rich User Interface that users demand and allows the users to intuitively interact with it.
ToolBox fits neatly within the T24 architecture as it uses the same communication protocol/channel as T24
Browser.
Users will be able to use ToolBox just by specifying the URL that you use for your T24 Browser. Its that
easy!!!
The two pre-requisites for ToolBox are:
1. Microsoft .NET framework
2. T24 Browser.
Note: T24
ToolBox communicates with the T24 web server using the http protocol,
sending and
receiving XML messages. The T24 web server will use the T24 connector to rely these
messages to the T24 system.
Toolbox been a dot net based program, naturally requires the Microsoft dot net
framework (Release 3.5) to execute. It uses browser/tcs to communicate with T24 and
hence we should have a browser/TCS/JBOSS configured, up and running to use
Toolbox.
Connection URL :Toolbox uses browser s connectivity to talk to T24. The URL that
we use is the same as what we use to connect browser to our T24 area. As you may
notice, this URL is however keyed in as distinct parts comprising of the IP Address,
Port Number and URL Address (comprising of the path to our servlet)
Toolbox may be configured to store multiple URLs.
Toolbox may be configured to multiple profiles. Each profile would have its own url to
connect to.
10
The main Toolbox window is presented in the form of a collection of tabbed screens.
Choosing a tab , brings up a window with a collection of icons relevant to that
operation.
11
You may right-click on any plug-in icon to bring up its context menu.
12
Note utilities provide a quick and easy way of doing things. You could still achieve
the same result the traditional Globus way by adding records to the relevant
applications such ENQUIRY, VERSION and EB.COMPOSITE.SCREEN
13
14
The enquiry id given must be unique. Giving the name of an existing enquiry results in
an error.
15
In order to create an Enquiry using the wizard click on the Enquiry wizard. Enter the
name of the enquiry (E.g.. AC.TOOLBOX.ENQ) and then click on the next button on
the top left corner of the screen to proceed with the creation of the enquiry record in
T24 through toolbox
16
17
18
Set additional header texts if you need a change of the existing ones.
19
This allows you to change your mind about the enquiry. At this stage the enquiry has
not been committed. You may change any of the settings by going back to the
previous screens.
You cannot use enquiry wizard to make changes after you have clicked on Create
Enquiry as the enquiry record would have then been committed.
Note you may open the enquiry through the Enquiry application and make changes
of course
20
21
22
Screen Id must follow the standard naming convention for a Version in T24. i.e.
application-name,version-name
23
24
25
26
27
The Screen Builder offers most options available in the VERSION application that can
be used to customize the property of a field to be displayed.
Text The text that must be displayed as the field label
Tool Tip The text that will be displayed if the mouse cursor is moved over the field
label
Drop Down Setting Allows us to attach an existing enquiry so that the ID of the
application that it is based on is returned as the value of the field in the version. A
selection criteria can also be set. This is described in detail in Task 1 (Version section)
Enrichment Specifies whether the enrichment text must be displayed or not
Mandatory Input in mandatory in this field if set to True
No Change Value in the field cant be changed once the record is authorized
No Input No input is allowed at anytime, must be populated by the system if required
Hot Field If set to true, the validation routine attached to the field is executed
immediately
28
Specify the screen layout or the order in which the fields of the version must be
displayed
29
30
Composite screen builder helps create composite screen . These screens may be
viewed through browser alone.
31
32
33
A composite comprises of one or many html frames. Each frame may be used to
house an application screen, an enquiry, a menu etc
The screen above shows us the options for the frame layouts depending on the
number of frames
34
35
The best thing about the Tool Box is there is help-text built in where ever possible.
The initial content can be one of the following.
Enquiry
Transaction
Menu
Url (if not prefixed with http:// they may not behave as intended).
Banner
Blank
Dynamic content is what will appear in the frames when the user starts navigating e.g.
committing
transactions, viewing enquiries etc. This can be one of the following
All Content, all transaction and enquiry screens will appear in the specified frame
All Enquiries, all enquiries will appear in the specified frame
No Enquiries, all content except for enquiries will appear in the specified frame
Specific Enquiry, the frame will only ever contain the specified enquiry
Allow Scrolling Scroll bars will appear is required when the value of this field is set to
true
Frame Name Name of the frame, used for reference by other frames
36
Composite screens may viewed by typing COS <screen-name> at the T24 command
line
37
41