Image Management
Image Management
Image Management
User Guide
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Table of Contents
Overview.................................................................................................................................................. 3
Setup ....................................................................................................................................................... 3
Web Browser Configuration ................................................................................................................. 3
Internet Explorer 7 ............................................................................................................................ 3
Firefox 2.0 ........................................................................................................................................ 5
T24 IM applications .............................................................................................................................. 7
IM.DOC.IMAGE.PARAMETER ............................................................................................................ 7
IM.IMAGE.TYPE .................................................................................................................................. 7
Mapped Drive ................................................................................................................................... 8
Full Path ........................................................................................................................................... 8
Relative Paths .................................................................................................................................. 9
File Access Permissions .................................................................................................................. 9
IM.DOCUMENT.IMAGE..................................................................................................................... 10
Static Processing ................................................................................................................................... 12
IM.DOCUMENT.UPLOAD ................................................................................................................. 12
Images ............................................................................................................................................ 12
Hyperlinks ....................................................................................................................................... 16
Enquiry .................................................................................................................................................. 21
Launching images from ENQUIRY .................................................................................................... 21
Sample IMAGE.LIST ENQUIRY .................................................................................................... 22
Overview
The Image Management (IM) product in T24 allows the display of images, opening of document files,
media files and other files by their associated applications.
IM benefits the user by providing immediate access to digital copies of essential data such as
signatures, loan documentation, birth certificates or passports. There is no need to access the
physical document itself - indeed this may not be possible with items such as passports, or if the item
itself is stored somewhere for safekeeping.
Images can be displayed within the browser interface itself, whilst other file types are shown as
hyperlinks which can be used to open an associated application to display the file. In this way various
files such as Acrobat PDF, Word documents, spreadsheets can be made available to the end user.
Setup
Web Browser Configuration
Since the Image management process involves writing and reading files from your local or network file
system, permission must be given before Internet Explorer or Firefox is able to do this.
Internet Explorer 7
To ensure that the T24 Browser site has been given a ‘Trusted’ status open the ‘Security’ Tab under
the ‘Internet Options’ dialog.
To add T24 Browser as a ‘Trusted Site’ click the ‘Sites’ button. In the resulting dialog a list of all
added sites will be shown. Ensure that the webserver that is running the T24 Browser application is
specified:
Trusted sites
In the example above the URL to access the T24 Browser application is:
http://localhost:8080/BrowserWeb/servlet/BrowserServlet
To ensure that the T24 Browser site has been successfully added as a ‘Trusted Site’ the IE status bar
should display a ‘tick’ when accessing the T24 Browser application.
Firefox 2.0
For security purposes, Mozilla applications block links to local files (and directories) from remote files.
This includes linking to files on your hard drive, on mapped network drives, and accessible via Uniform
Naming Convention (UNC) paths. This prevents a number of unpleasant possibilities, including:
• Allowing sites to detect your operating system by checking default installation paths
• Allowing sites to exploit system vulnerabilities (e.g., C:\con\con in Windows 95/98)
• Allowing sites to detect browser preferences or read sensitive data
So that the Image Management process can function when using Firefox, the security check must be
disable when running T24 Browser.
The following instructions are for Firefox 2.0. If a different version is being used then refer to the
Mozilla documentation for instructions on how the security check can be disabled. For further
information and guides on how to configure the Firefox web browser at an administrative level please
see:
http://kb.mozillazine.org/Links_to_local_pages_don%27t_work
Ensure that ALL instances of the Firefox web browser have been shut and none are running.
Locate the ‘prefs.js’ file under the Firefox profile settings typically found in the following directory:
C:\Documents and Settings\<user>\Application Data\Mozilla\Firefox\Profiles
Edit the ‘user.js’ using notepad and add the following entries to it:
user_pref("capability.policy.localfilelinks.checkloaduri.enabled", "allAccess");
user_pref("capability.policy.localfilelinks.sites", "http://localhost:8080");
user_pref("capability.policy.policynames", "localfilelinks");
Replace the http://localhost:8080 entry with the required site name of the Browser web application. If
more than one site name is required then they can be added and separated by a space e.g.
user_pref("capability.policy.localfilelinks.sites", "http://localhost:8080
http://10.1.2.3:8080 http://10.4.5.6");
Note that any site name listed should not include the final / or anything else from the path part of the
URL.
Save the ‘user.js’ file and start Firefox. Firefox will no be able to resolve resources on the local file
system and network as required by Image Management.
T24 IM applications
The standard applications used by Image Management are:
Application Usage
IM.DOC.IMAGE.PARAMETER Image parameter settings (not currently used)
IM.IMAGE.TYPE A categorisation and location of type of images/files
IM.DOCUMENT.IMAGE The details of the record and link reference
IM.DOCUMENT.LOAD Uploads images to storage or links to non image files
IM applications
IM.DOC.IMAGE.PARAMETER
This application contains just one record called system and is reserved for future use.
IM.IMAGE.TYPE
The first settings to be made are to define the types or categories of files and images. The
IM.IMAGE.TYPE record is used to record the location of the files and allows the categorisation of
the files by types which makes the storage and retrieval to be setup in a logical fashion.
In a simple setup there could be just one record but this location would then contain all the images,
documents, pdf’s and other files in the one directory.
So a typical usage would be to place similar types together in special directories, so records such as
PHOTO, PASSPORT, SECURITY, SIGNATURE, VIDEO, FORMS etc would each have their own unique
sub-directory.
The storage location can be set either using:
Mapped Drive
Typically in Windows environments drives are accessed by mapping directories to a familiar drive
letter.
The above record is based on the storage location being accessible using a mapped drive reference
‘V:’ and the directory ‘/images/pics/’.
The ‘V:’ mapping could be pointing to a nested directory whose full path would be way too long for
practical use. So in fact the path shown above is in reality based on the starting position in the
directory structure signified by ‘V:’.
In a sense mapped paths can be thought of as being relative paths as the location is relative to the
mapped directory level.
The path should be prefixed with a ‘/’ and terminate with a ‘/’; these can be entered either in Windows
or Unix format (/ or \) as T24 will convert where required.
It is unlikely that images or links would be stored on the C: (or other local drives) but if required they
can be used as long as they are made shared - this is a security feature of most web browsers and not
a T24 requirement. If a link or image does not work as expected check that the location is accessible.
Full Path
When not using the DEFAULT.DRIVE field to indicate a mapped drive the full path can be used. The
browser used will evaluate the path and based on standard web criteria ascertain if the path can be
reached and the file displayed or linked to.
The browser will evaluate this full path just as if it were prefixed with a default drive letter.
Relative Paths
Precede path with one or two dots
If the path in the record is entered as either “.\secure\T24\images\acrobat\” or
“..\secure\T24\images\acrobat\” then this indicates that it is a path relative to the BrowserWeb root
location.
Note
Storing images or other related files in directories relative to the Browser is not recommended as a full
replacement of the Browser files is usually preceded by removal of the entire directory – this would
result in the loss of the image files as well.
IM.DOCUMENT.IMAGE
The IM.DOCUMENT.IMAGE application is where the individual file (or image) details are entered
and where we bring together key information.
The id of these records is a standard julian date type key; but it could just as well be any unique
reference as in itself it is not too useful. So the internal fields are more involved in deciding the usage
of the record and how to access it.
This is best explained with an example.
Note we associate the record with an IM.IMAGE.TYPE, this categorises the file type and more
importantly links to where the file will be stored.
We have indicated the image is associated with the application ACCOUNT, and that the reference
we will store the link as is the ACCOUNT number (40169).
The other fields are informational, such as the description and the type of media.
NB
It is not necessary to link the file with an application – the important feature is the image reference.
This becomes our retrieval key and a system file will be built which details all the images using this
reference. So we could have several image files associated with the same ACCOUNT record.
Alternatively we could have one or more records just accessible by the reference ‘BANKRULES’ so
users could retrieve them without concern about them being associated with any specific application.
Since the normal operation is where the records are associated then the later examples will be in that
form.
Now to load the file.
Static Processing
IM.DOCUMENT.UPLOAD
So far we have entered records which relate to where files are stored and how we plan to link to them
but we have yet to actually load a file or link to one.
The IM.DOCUMENT.UPLOAD application is used next. With this we can load an image file from
an import directory and store it with a unique id, or for certain file type simply specify the name of the
file we require a hyperlink for.
We’ll do the signature example first followed by a hyperlink to a Word document.
Images
If the Browse option is used the eventual selection (file name) is copied into the file selection field.
Once happy you have the correct file click on the import icon, illustrated below.
Next we will be returned to the IM.DOCUMENT.UPLOAD record, and if we have a valid image
record it will also be displayed so we have a visual confirmation that it is the correct record and is
viewable.
Note the new reference in the field FILE.UPLOAD differs from the image file name we imported.
The image file is now called and is located in the directory specified in the IM.IMAGE.TYPE used on
the IM.DOCUMENT.IMAGE record we selected.
Later we will need to decide where to access them and how, but next we’ll do a similar transaction for
a hyperlink file.
Hyperlinks
To setup a link to a record (other than an image file) we need to consider the following:
We can use the ENQUIRY to find the hyperlink image based on the IMAGE.TYPE we entered.
Note
The hyperlink will be displayed by browser but the resulting action when it is invoked (clicked on)
depends on the applications installed on the user pc; the associated event and application for the
extension of the file in the hyperlink.
It should be possible to link to Word documents; Excel files; media files such as video and sound as
long as the file extension is associated correctly with an installed application. For example a file called
sample.txt may be associated with Notepad for one user but Word for others. Where appropriate the
file will be loaded into a browser version of the application (Acrobat PDF viewer, Word viewer etc) just
as would happen when you open a linked file from the Internet.
Enquiry
Launching images from ENQUIRY
It should be noted that the ENQUIRY application has a special setting to allow an image or hyperlink
to be displayed.
The field FIELD.DISP.TYPE needs to be set as IMAGE, as this instructs the system to display the
link as either an image in a browser window for picture files; or to create a hyperlink for other file types
(which can be clicked on and hopefully load the file into the associated application).
In the example below the ENQUIRY is using the file IM.DOCUMENT.IMAGE but the actual
images are not on that file. The link is created using the KEY (or @ID) and the system knows to
locate the image based on the IMAGE setting in the ENQUIRY and resolving the filename and path.
You can of course have a front-end ENQUIRY to filter the results down since any ENQUIRY listing
that contains a large amount of images would take a while to open them all up for display and fill up
the screen.
If not already present in your system, or in the format you require the ENQUIRY IMAGE.LIST may
need inputting/amending to link to your new display ENQUIRY.
In the above screen the fields used to link to the DISP.IMAGE ENQUIRY are highlighted.