---
title: "Image Enquiry - Formpipe's Temenos Integration Guide"
slug: "image-enquiry"
description: "The Image Enquiry function is used to return images to a T24 screen - predominantly, a customer’s photo and signature to the Single Customer View. "
tags: ["T24 integrations", "Image enquiry", "BrowserWeb", "Customer photo", "Customer signature", "Document download", "Temenos"]
updated: 2026-03-03T14:23:48Z
published: 2026-03-03T14:23:48Z
canonical: "kb.lasernetgroup.com/image-enquiry"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Image Enquiry

## Image Enquiry

The **Image Enquiry** function is used to return images to a T24 screen. This is predominantly used to return a customer’s photo and signature to the **Single Customer** View. The images (customer photo and signature) are securely stored in the Autoform DM archive and referenced by a unique key.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (38)(2).png)

### Overview

The data servlet integration files are held in `autoform-dataservlet-4.*-bin.zip`. The servlet details will need to be added to the relevant `web.xml` file, and the data servlet jar will be placed in the correct folder.

To use the data servlet to display images in the T24 browser, **T24 Enquiries** need to be created. These can then be used in the SCV to view the customer photo and signature. Details on creating these Enquiries can be found in the following sections of this guide.

### Configuration and Integration

1. Copy `efs-dataservlet-4.*.jar` to `BrowserWeb.war/WEB-INF/lib`.
2. Update `BrowserWeb.war/WEB-INF/web.xml` with the basic configuration found in `web.xml` in the interface distribution.
3. Consult `web-full.xml` for an example that includes all configurable parameters for the interface, along with explanations for each. For instance, copy `web/error.jpg` to `BrowserWeb.war/WEB-INF/` folder and set as `init-parameter`.

### Logging

Debugging is configured in `BrowserWeb.war\WEB-INF\classes\log4j.properties` (or jboss-specific log config file) by setting the `com.efstech` category to **DEBUG**.

#### Password Encryption

- Use CLI to encrypt passwords.

The DM password for all integrations can be encrypted using the CLI for our crypto-utils library by following these steps:

1. Obtain the **CLI** jar from the interfaces release package. It should be named `crypto-utils-1.0.0-cli.jar` or similar.
2. Run the jar file as `java -jar crypto-utils-1.0.0-cli.jar` encrypt, for example, to use the key **MyKey** to encrypt the DM password `DM_PASS`, you would run it as: `java -jar crypto-utils-1.0.0-cli.jar encrypt DM_PASS MyKey`.
3. The output from this command is the encrypted DM password. This should be surrounded with `ENC()` and placed in the relevant properties file (for example, `NoFileEnquiry.properties`) for the interfaces release jar. For instance, `dm.password=ENC(AX23DKJCL2LKJDLKJ436)`.
4. The encryption key (**MyKey** in this example) must be set as an environmental variable with the name `EFS_T24_INTERFACES_KEY`.

- Change the encryption profile.

Both the CLI and the interfaces enable an alternative encryption profile to be selected if there is a perceived need to use something other than the default.

To do so, the name of the desired encryption profile should be passed to the CLI, and the interface - if configured- must match; otherwise, password decryption will fail.

For the CLI, the profile name can be selected by adding `-c` to the end of the command. For the Interfaces, it is passed as the **EncryptionConfig** parameter.

The possible profiles are the following:

- **pbkdf2hmacsha1withaes128cbc**: The default profile, used if nothing is explicitly set.
- **pbkdf2hmacsha1withaes256cbc**: Provides higher bit strength AES.

The second profile provides higher strength AES, but this requires the environment to support this. A standard JDK will not support anything above 128bit without either the unlimited-strength JCE profile enabled or a third-party library such as BouncyCastle. As such, it should only be used if required and with the understanding that additional work must be done to ensure the environment supports it.

### Usage

#### Customer Photo

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-5T4ST3G3.png)

Create a new T24 Enquiry called **AUTOFORM.PHOTO** using the command **ENQUIRY, AUTOFORM.PHOTO**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (1)(3).png)

Several Browser tools, such as the **AUTOFORM.PHOTO** browser, enhance the Lasernet Group interfaces. For details on how to configure this tool, navigate to the [Browser Tools](/v1/docs/browser-tools) section.

| Field | Value |
| --- | --- |
| Page Size | 4,99 |
| File Name | CUSTOMER |
| Selection Flds.1 | CUSTOMER.CODE |
| GB Sel Label.1 | Customer Number |
| Field Name.1 | SERVLETADD |
| Operation.1.1 | “./servlet/PDMDataServlet?” |
| Single Multi.1 | S |
| Field Name.2 | CUSTOMER |
| Operation.2.1 | IDESC CUSTOMER.NO |
| Single Multi.2 | S |
| Field Name.3 | IMAGE |
| Operation.3.1 | C SERVLETADD : “CUK=Photo” : CUSTOMER |
| Column.3 | 2 |
| Field Disp Type.3 | Image |
| Attribs.3.1 | No Header |
| Col Width.3 | 100 |
| Single Multi.3 | S |
| Field Name.4 | HEADER1 |
| Operation.4.1 | Customer |
| Column.4 | 1,1 |
| Field Disp Type.4 | Class-enq Data Label |
| Section.4 | Header |
| Col Width.4 | 100 |
| Single Multi.4 | S |
| Field Name.5 | CUSTOMER |
| Operation.5.1 | SELECTION CUSTOMER.CODE |
| Column.5 | 2,1 |
| Field Disp Type.5 | Class-enq H Data |
| Section.5 | Header |
| Col Width.5 | 100 |
| Single Multi.5 | S |
| Field Name.6 | ZERORECORDS |
| Operation.6.1 | Customer Photo not Captured |
| Column.6 | 1 |
| Display Break.6 | NONE |
| Field Disp Type.6 | Class-enq Norecs |
| Section.6 | Header |
| Col Width.6 | 100 |
| Single Multi.6 | S |
| Attributes.1 | No Selection |
| Attributes.2 | No Enquiry Favourites |
| Attributes.3 | Zerorecorddisplay |
| Attributes.4 | No Column Header |
| Attributes.5 | No Breadcrumbs |
| Attributes.6 | Single Background Colour |
| Tool Id.1 | AUTOFORM.PHOTO |
| GB Tool Text.1 | Take Customer Photo |
| Tool Id.2 | ENQ.REFRESH |

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (3)(4).png)

#### Customer Signature

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (4)(5).png)

Like the **Customer Photo**, the **Customer Signature** is securely stored as an image in the **Autoform DM Archive.** Create a T24 Enquiry **AUTOFORM.SIGNATURE** using **ENQUIRY, AUTOFORM.SIGNATURE** to retrieve this using the **Data servlet**.

| Field | Value |
| --- | --- |
| Page Size | 4,99 |
| File Name | CUSTOMER |
| Selection Flds.1 | CUSTOMER.CODE |
| GB Sel Label.1 | Customer Number |
| Field Name.1 | SERVLETADD |
| Operation.1.1 | “./servlet/PDMDataServlet?” |
| Single Multi.1 | S |
| Field Name.2 | CUSTOMER |
| Operation.2.1 | IDESC CUSTOMER.NO |
| Single Multi.2 | S |
| Field Name.3 | IMAGE |
| Operation.3.1 | C SERVLETADD : “CUK=SIG” : CUSTOMER |
| Column.3 | 2 |
| Field Disp Type.3 | Image |
| Attribs.3.1 | No Header |
| Col Width.3 | 100 |
| Single Multi.3 | S |
| Field Name.4 | HEADER1 |
| Operation.4.1 | “Customer” |
| Column.4 | 1,1 |
| Field Disp Type.4 | Class-enq Data Label |
| Section.4 | Header |
| Col Width.4 | 50 |
| Single Multi.4 | S |
| Field Name.5 | CUSTOMER |
| Operation.5.1 | SELECTION CUSTOMER.CODE |
| Column.5 | 2,1 |
| Field Disp Type.5 | Class-enq H Data |
| Section.5 | Header |
| Col Width.5 | 50 |
| Single Multi.5 | S |
| Field Name.6 | ZERORECORDS |
| Operation.6.1 | “Customer Signature not Captured” |
| Column.6 | 1 |
| Display Break.6 | NONE |
| Field Disp Type.6 | Class-enq Norecs |
| Section.6 | Header |
| Col Width.6 | 50 |
| Single Multi.6 | S |
| Attributes.1 | No Selection |
| Attributes.2 | No Enquiry Favourites |
| Attributes.3 | Zerorecorddisplay |
| Attributes.4 | No Column Header |
| Attributes.5 | No Breadcrumbs |
| Attributes.6 | Single Background Colour |
| Tool Id.1 | AUTOFORM.SCAN |
| GB Tool Text.1 | Scan Customer Document |
| Tool Id.2 | ENQ.REFRESH |

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (2)(4).png)

#### Optional Parameters for Image Enquiries

The size of the image returned from the DM server can be resized by the servlet. These are query parameters that can be added to the end of the HTTP request.

> [!NOTE]
> Note
> 
> Be aware that there is limit of characters in this field on R16, so you might use workaround for it. (for instance, with static **CUK C SERVLETADD : “CUK=201” : “&img-width=300”** or use two fields and merge it.)

For example, for **Customer Photo**:

`Operation.3.1: C SERVLETADD : “CUK=Photo” : CUSTOMER : “&img-width=100&img-height=100”`

For **Customer Signature**:

`Operation.3.1: C SERVLETADD : “CUK=SIG” : CUSTOMER : “&img-width=300&img-height=100” |`

### Document Download Usage

The **Document Download** interface extends the native **T24 Download function**, which is triggered from a drill-down that we add to the T24 Enquiry, which is used to return the list of documents. This drill-down is displayed as a **View** link.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (5)(4).png)

The drill-down is added to the **Enquiry** field of the **T24 Enquiry**. The format of this in the example used for the **AUTOFORM.DOCS Enquiry** is as follows:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (6)(8).png)

The **DOWNLOADID** has the following format (this is also configured in the **T24 Enquiry**): `CALC “DOCID=” : document.id : “|.pdf”`.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image (7)(7).png)

To make the document extension dynamic, follow these steps:

1. Add a **document.file.extension** field.
2. Add an **extension** field with the `Operation: CALC "|." : document.file.extension`.
3. Update the **DOWNLOADID** field to concatenate the two parts: `CALC "DOCID=" : document.id : extension`.