Image Management

Module Overview
The Image Management (IM) product in T24 allows the display of images, opening of document files, media files and other files by their asso-
ciated 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 asso-
ciated 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.

l Setup
l Static Processing
l Enquiry
l Cloud-based Image Management

Image Management - Release R13.00 -Page 2 of 12 - (c) Temenos Systems 2013 05/07/2013
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.

Im a ge s
First we create a new record in IM.DOCUMENT.UPLOAD and enter the IM.DOCUMENT.IMAGE reference in the UPLOAD.ID field.

The next field FILE.UPLOAD is used as a normal data field or by clicking the camera icon next to it can be used to import an image file.

If the camera icon is used then some other windows will open to allow you to select a file and the field will be populated with a unique ref-
erence. If not used you may simply type the file name in. Once the record is validated the details will be used update the IM.DO-
CUMENT.IMAGE record in field IMAGE and this application will have done its work.

Let’s load the signature we need to store.

IM.DOCUMENT.UPLOAD to import image

File Upload box and Standard Windows browse box to find/select a file.

1. Enter the location manually

2. Use the Browse option

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.

Using the import icon

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 vis-
ual confirmation that it is the correct record and is viewable.

IM.DOCUMENT.UPLOAD record

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.

Unique Id of imported image file

Reference file linkage

Image Management - Release R13.00 -Page 3 of 12 - (c) Temenos Systems 2013 05/07/2013
So now we have a logical search when locating an image/file.

If we start with the image reference we selected ‘23067’, being the account number we can see the IM.DOCUMENT.IMAGE id. This in turn will
have the image file name and a further link to the IM.IMAGE.TYPE where we store the location (directory) of the files.

Later we will need to decide where to access them and how, but next we’ll do a similar transaction for a hyperlink file.

H y pe r link s
To set up a link to a record (other than an image file) we need to consider the following:

l Where are these files to be stored?

l How are they categorised?
l Can they be opened with a PC application by the user?
l Where to reference them?

First we setup an appropriate IM.IMAGE.TYPE

Hyperlink image type

Next we enter the IM.DOCUMENT.IMAGE record which acts as the linkage.

PDF Image record

We now need to link the actual PDF to this record.

Hyperlink item name

IM.DOCUMENT.IMAGE location has been updated

We can use the ENQUIRY to find the hyperlink image based on the IMAGE.TYPE we entered.

Using Enquiry to find hyperlink

ENQUIRY shows one result – with option button

Hyperlink is displayed instead of an actual image

PDF displayed in browser window.

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 asso-
ciated correctly with an installed application. For example a file called sample.txt may be associated with Notepad for one user but Word

Image Management - Release R13.00 -Page 4 of 12 - (c) Temenos Systems 2013 05/07/2013
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.

Image Management - Release R13.00 -Page 5 of 12 - (c) Temenos Systems 2013 05/07/2013
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 win-
dow 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 appli-
cation).

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.

FIELD.DISP.TYPE set as IMAGE

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.

Image Management - Release R13.00 -Page 6 of 12 - (c) Temenos Systems 2013 05/07/2013
Sa m ple IMA GE.LIST EN QU IR Y

Part 1 of 2 IMAGE.LIST ENQUIRY

Image Management - Release R13.00 -Page 7 of 12 - (c) Temenos Systems 2013 05/07/2013
 Part 2 of 2 of IMAGE.LIST ENQUIRY

In the above screen the fields used to link to the DISP.IMAGE ENQUIRY are highlighted.

Image Management - Release R13.00 -Page 8 of 12 - (c) Temenos Systems 2013 05/07/2013
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.

Inte r ne t Ex plor e r 7
To ensure that the T24 Browser site has been given a ‘Trusted’ status open the ‘Security’ Tab under the ‘Internet Options’ dialog.

Security settings tab

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.

Internet Explorer indicating trusted site

Fir e fox 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 pos-
sibilities, including:

l Allowing sites to detect your operating system by checking default installation paths
l Allowing sites to exploit system vulnerabilities (e.g., C:\con\con in Windows 95/98)
l 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("capabil-
ity.policy.policynames", "localfilelinks");

Image Management - Release R13.00 -Page 9 of 12 - (c) Temenos Systems 2013 05/07/2013
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 loca-
tion 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 , SIG-
NATURE, VIDEO, FORMS etc would each have their own unique sub-directory.

The storage location can be set either using:

l Standard drive letter and path

l Full path
l Relative path to the web server (browser) root for Unix.

Ma ppe d D r iv e
Typically in Windows environments drives are accessed by mapping directories to a familiar drive letter.

Drive letter based location

The above record is based on the storage location being accessible using a mapped drive reference ‘U:’ and the directory ‘/im.images/photos/’.

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 ‘U:’.

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 con-
vert where required.

Image Management - Release R13.00 -Page 10 of 12 - (c) Temenos Systems 2013 05/07/2013
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 Pa th
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.

Location based on full network path

The browser will evaluate this full path just as if it were prefixed with a default drive letter.

R e la tiv e Pa ths
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.

File A c c e s s Pe r m is s ions
When setting up the image system and secure file locations it should be noted that there are certain permissions needed to allow the files to be
uploaded/viewed by the user and/or web server.

The user uploading a file of course needs access to the file. However, the web server will be writing the file to the secure storage location for
the file type, when the user then needs to view the image the web server will only provide a link to the secure location – the user needs to have
access rights to view files from this location 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 infor-
mation.

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.

l We have signatures for one ACCOUNT which we want to display

l The IM.DOCUMENT.IMAGE id has no relevance to the account.
l We have yet to link the signature image
l We need to retrieve the signature based on the ACCOUNT number later on.
l We need to display the actual image.

So first we input the IM.DOCUMENT.IMAGE record.

Record for Photos of Account 23067

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 (23067).

The other fields are informational, such as the description and the type of media.

Image Management - Release R13.00 -Page 11 of 12 - (c) Temenos Systems 2013 05/07/2013
Note: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.

Image Management - Release R13.00 -Page 12 of 12 - (c) Temenos Systems 2013 05/07/2013