Introduction

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.
The following is a sample setup explaining the functionality of IM
module. Please refer to the Browser User guides for further details.

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 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.

BNK R05BASE TYPE OF IMAGE SEE

IMAGE.NAME........ PIC
------------------------------------------------------------------------------
1. 1 GB DESCRIPTION. TEST PICTURE
2 DEFAULT.DRIVE..... C:
3 PATH.............. \Images\
5 CURR.NO........... 1
6. 1 INPUTTER....... 26_PREETHA1
7. 1 DATE.TIME...... 11 JAN 07 14:12
8 AUTHORISER........ 26_PREETHA1
9 CO.CODE........... US-001-0001 BNK R05BASE
10 DEPT.CODE......... 1
------------------------------------------------------------------------------
12 JAN 2007 10:02:51 USER (30 NOV) PREETHA1 [9,24] PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS

In the above example, the scanned images would be stored in the

“Images” folder of the C drive.

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.

• We have an image associated to a CUSTOMER which we want to display

• The IM.DOCUMENT.IMAGE id has no relevance to the customer.
• We have yet to link the image
• We need to retrieve the image based on the CUSTOMER number later
on.
• We need to display the actual image.

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

BNK R05BASE DOCUMENT IMAGE SEE

KEY............... IM-00335-00001
------------------------------------------------------------------------------
1 IMAGE.TYPE........ PIC TEST PICTURE
2 IMAGE.APPLICATION. CUSTOMER
4 IMAGE.REFERENCE... 50013
5 SHORT.DESCRIPTION. PIC FOR CUSTOMER ABU DHABI NATIONAL OIL COMPANY
6. 1 GB DESCRIPTION. PIC FOR CUSTOMER
9 MULTI.MEDIA.TYPE.. IMAGE
20 CURR.NO........... 1
21. 1 INPUTTER....... 11_PREETHA1___GTS
22. 1 DATE.TIME...... 11 JAN 07 12:14
23 AUTHORISER........ 11_PREETHA1_OFS_
24 CO.CODE........... US-001-0001 BNK R05BASE
25 DEPT.CODE......... 1
------------------------------------------------------------------------------
12 JAN 2007 10:13:09 USER (30 NOV) PREETHA1 [9,24] PAGE 1
ACTION
AWAITING PAGE INSTRUCTIONS

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
CUSTOMER, and that the reference we will store the link as is the
CUSTOMER number (50013).
The other fields are informational, such as the description and the
type of media.
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.

Images

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
reference. If not used you may simply type the file name in. Once the
record is validated the details will be used to update the
IM.DOCUMENT.IMAGE record in field IMAGE and this application will
have done its work.

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

Sample IMAGE.LIST ENQUIRY

In the above screen the fields used to link to the DISP.IMAGE ENQUIRY
are highlighted. The output of the enquiry would be as follows:

After Drilldown, the image can be viewed as follows: