Welcome to the learning unit on Enquiries- Fast Path –Images.

This learning unit

teaches you about drilldowns, workflows and fast path enquiries in T24.

CUS-Enquiries-Fast Path-Images 1
 The conventions used in this learning unit are,

1. Applications in T24 are represented in BOLD UPPERCASE letters.

2. The fields in the applications are mentioned in UPPERCASE letters.

3. This learning unit is example based. First an example output will be shown then
you will be taught the steps to create the Version. At the end of each section a
workshop is given to test your level of understanding.

CUS-Enquiries-Fast Path-Images 2
 After completing this course you will be able to -

1.Create Drill Down Enquiries in T24.

2.Understand Context Based Workflow in T24.

3.Create Fast Path Enquiries.

CUS-Enquiries-Fast Path-Images 3
 1. ENQUIRY application fetches reports from the applications in T24. ENQUIRY
application allows you to extract and view data from T24

2. Can you view the customer information of a particular customer from an enquiry
based on the LD.LOANS.AND.DEPOSITS application?

The user should be given a link to drilldown to the customer information. This link
should be specified in the enquiry that is based on the LD.LOANS.AND.DEPOSITS
application.

3. In T24 you can navigate from one enquiry to another

4. The process of linking two or more enquiries is known as drilldowns

CUS-Enquiries-Fast Path-Images 4
 This task aims at teaching you drilldown enquiries.

Assume that you have created an Enquiry for the LD.LOANS.AND.DEPOSITS

application. From its output is it possible to link to another enquiry based on the
CUSTOMER application so that you can also view customer details? Yes this can be
done. This is what is known as a drill down.

The enquiries to which you can link to must be defined in the parent enquiry record
itself. In this example the parent enquiry is based on the LD.LOANS.AND.DEPOSITS
application. From this parent enquiry invoke the child enquiry that is based on the
CUSTOMER application .

The requirement of the task is as follows:

1. Create an Enquiry based on the LD.LOANS.AND.DEPOSITS application with the

following fields - @ID , CUSTOMER.NO, CURRENCY, AMOUNT, MATURITY.DATE &
INTEREST.RATE

2. Using this Enquiry invoke another Enquiry which is based on the CUSTOMER
application. The Enquiry based on the CUSTOMER application has the following fields
– CUSTOMER.NO,MNEMONIC, SHORT.NAME & NATIONALITY.

CUS-Enquiries-Fast Path-Images 5
 The parent Enquiry is based on the LD.LOANS.AND.DEPOSITS application. Specify
the field name & field value for the fields - @ID , CUSTOMER.NO, CURRENCY,
AMOUNT, MATURITY.DATE & INTEREST.RATE

Note : The field name of the MATURITY DATE field is FIN.MAT.DATE

CUS-Enquiries-Fast Path-Images 6
 Next you will create the child enquiry which is for CUSTOMER application. Specify the
following fields – CUSTOMER.NO, MNEMONIC,SHORT.NAME & NATIONALITY.
Ensure that you specify the value for COLUMN field. Authorize the child Enquiry.

CUS-Enquiries-Fast Path-Images 7
 You have now created the parent enquiry and the child enquiry. Now you will learn
how to invoke the child enquiry from the parent enquiry. Amend the parent enquiry as
stated .To enable drilldown feature use the field ENQUIRY.NAME .

ENQUIRY.NAME – Specify the ID of the child Enquiry that has to be invoked.

SEL.CRIT – The specific customer record is chosen based on the customer id. The
customer id acts as a link between these two enquiries. The FIELD.NAME for
CUSTOMER.NO field is CUSTOMER. The value of CUSTOMER.NO is passed from
the parent enquiry to the child enquiry. Specified value is CUSTOMER.NO EQ
CUSTOMER, where CUSTOMER.NO is the field in child enquiry and CUSTOMER is
the field defined in this parent enquiry. The value in these two fields are checked using
the ‘EQ’ operand. When values in these two fields are equal the enquiry system
launches the customer report. This serves as the selection criteria for launching the
child enquiry.

LABEL.FIELD- Here you will specify the field which is used to invoke the child enquiry.
The field CUSTOMER is the field name for CUSTOMER.ID field. The value two(2) is
defaulted by T24. It denotes the column position of the field in this Enquiry.

NEXT.DESC – Specify the hyperlink to invoke the child Enquiry. Authorize the
Enquiry.

CUS-Enquiries-Fast Path-Images 8
 1. When you launch the parent enquiry, you will see the output looks different. The
loan details are displayed in each row but at the end of every row there is a
hyperlink. Use the link to launch the child enquiry.

2. The child enquiry displays the specific customer as the value of the field
CUSTOMER is passed from the parent enquiry to the child enquiry.

CUS-Enquiries-Fast Path-Images 9
 The given workshop tests your understanding on drilldown enquiries. The requirement
is stated below:

1. Create an Enquiry based on the ACCOUNT application and display the following
fields – CUSTOMER,MNEMONIC,CATEGORY & CURRENCY

2. Create an Enquiry based on the FUNDS.TRANSFER application which displays

the following fields – TRANSACTION.TYPE, DEBIT.ACCT.NO,
DEBIT.CURRENCY, DEBIT.AMOUNT, CREDIT.ACCT.NO, and
CREDIT.AURRENCY

3. The user should be able to view the FT details of a particular account from the
account enquiry

CUS-Enquiries-Fast Path-Images 10
 You can link enquiries using the drill down facility. Can you link an enquiry to a
version? For example, if a bank clerk is looking at an enquiry output based on the
CUSTOMER application, he must be able to click on a hyperlink that allows him to
create an ACCOUNT record for a particular customer. This is known as Context
Based Workflow in T24.You can also invoke versions from your enquiry. This section
teaches you how to create Context Based Workflows.

The requirement of the task is as follows:

1. Create an Enquiry based on the CUSTOMER application and display the following
fields @ID, and SHORT.NAME.

2. Create a version based on the ACCOUNT application and display the following
fields CUSTOMER, CATEGORY, MNEMONIC, CURRENCY & ACCOUNT.TITLE.

3. Using this Enquiry invoke a Version that creates an Account. The Customer Number
and Short Name must be defaulted into the version

CUS-Enquiries-Fast Path-Images 11
 You must first create the Version and Enquiry records that need to be part of the
workflow.

CUS-Enquiries-Fast Path-Images 12
 The task requires that values from the enquiry to be passed to the fields in the version.
The values for the fields ID and ACCOUNT.TITLE is passed to the version from the
enquiry. Therefore these fields will be populated automatically once you launch this
version.

AUTOM.FIELD.NO – In this field you specify the field name for which you want to
default the values.
AUT.NEW.CONTENT – The field AUT.NEW.CONTENT holds the value to be
defaulted. Here as you are passing the value from the enquiry, specify the content in
the following format APPLICATIONNAME>FIELDNAME.

CUS-Enquiries-Fast Path-Images 13
 How do you make an Enquiry invoke an application or a version?

ENQUIRY.NAME – In this field you can specify an enquiry or an application name that
will be invoked next. You can specify the function followed by the application name. To
invoke an application in SEE mode you can append the function ‘S’ along with the
application. As you are going to invoke a version that will create customer accounts,
specify ACCOUNT,TRG.VERSION1 I F3. ACCOUNT,TRG.VERSION1 is the version
to be invoked. F3 is specified for auto-id generation.

SEL.CRIT - The customer ID should be automatically populated in the Account

record. You can pass the Customer ID by specifying the field name in the field
SEL.CRIT. The format is (Application name) > (Field name). Field name should be
defined in this enquiry. In this field you will mention CUSTOMER >
CUSTOMER.NUMBER , where CUSTOMER is the linking application between the
Enquiry and the version and CUSTOMER.NUMBER is the field name for @ID field in
this Enquiry. For specifying additional selection criteria, use the format – (Any variable
name) > (Field Name)

CUS-Enquiries-Fast Path-Images 14
 Sub value the SEL.CRIT field and specify the value to populate the ACCOUNT.TITLE
field in the version. In the screen shot the specified value is
ACCOUNt.TITLE.1>ST.NAME where ST.NAME is the name of the SHORT.NAME
field.

LABEL.FIELD – The field in the enquiry whose value is passed to the version must be
mentioned in this field.
Note: The number in the screen shot next to the value CUSTOMER.NUMBER defaults
when the enquiry record is committed. It denotes the position of that field in the
enquiry.

The text that acts as a hyper link is specified in the field NXT.DESC.

Now authorize and execute your enquiry.

CUS-Enquiries-Fast Path-Images 15
 1. Launch the parent Enquiry, you can see a link ‘Open Account’ . When you click on
the hyper link the enquiry invokes the version in turn.

2. As soon as the version is invoked , it creates a new account for the customer. The
CUSTOMER.NO and SHORT.NAME for the customer is passed to the version
from the parent enquiry.

CUS-Enquiries-Fast Path-Images 16
 This task aims at teaching you Fast Path enquiries in T24.
Fast path enquiries allow you to authorise, input, delete and reverse records using
enquiries.

Let’s say Account officer1 has privileges to authorise Funds Transfers with
Transaction type as ‘AC’ and the Debit Amount as 10,000. There may be many
records that match this criteria. Is there is a way in T24 to authorise a group of records
in one go and that too from an enquiry output? Yes you can. This is done using Fast
Path Enquiries in T24.

The requirements of the task is as follows:

1.Create an Enquiry based on the FUNDS.TRANSFER$NAU file. Display the

following fields @ID,TRANSACTION.TYPE, DEBIT.ACCT.NO, CREDIT.ACCT.NO ,
DEBIT.AMOUNT & RECORD.STATUS.

2. The enquiry should also allow you to perform the following function on the records
2.1 Authorize
2.2 Delete

CUS-Enquiries-Fast Path-Images 17
 The enquiry is based on the FUNDS.TRANSFER application. This example shows
the creation of a Fast Path Enquiry for the FUNDS.TRANSFER application . The
enquiry will display the following fields - @ID,TRANSACTION.TYPE,
DEBIT.ACCT.NO, CREDIT.ACCT.NO , DEBIT.AMOUNT & RECORD.STATUS.

FILE.NAME – When you input a FT transaction, the FT record moves to INAU status.
So you need to select the records from INAU status. The enquiry is based on the
$NAU file of the FUNDS TRANSFER application, only then you can authorize the
records. FILE.NAME field holds the value as FUNDS.TRANSFER$NAU. This is the
main file which will be processed by the enquiry . It should be a valid entry on
F.FILE.CONTROL .

FIXED.SELCTION – The FUNDS.TRANSFER$NAU file may also contain records that

are in hold status. Hence in the FIXED.SELECTION field you specify the condition to
select FT records that are in INAU status.

Specify the other required fields of the enquiry.

CUS-Enquiries-Fast Path-Images 18
 ENQUIRY.NAME –The enquiry will be used for authorizing and deleting FT records.
In the ENQUIRY.NAME field you specify an application or enquiry that has to be
invoked. Now to authorize the FT records the Enquiry system need to know the ID. To
invoke an application specify the application name followed by the function and the id
of the application file. For example, here we specify ‘FUNDS.TRANSFER A @ID’,
where FUNDS.TRANSFER is an application and A denotes the authorization function.

ENQUIRY.NAME is a multi-value field. Multi value and specify ‘FUNDS.TRANSFER

D @ID’ for deleting records. In the LABEL.FIELD specify the field which will be
displayed in the enquiry report. Specify @ID as the field. The user can select the
record from the generated report based on the chosen id.

The options of the ATTRIBUTES field determines the behavior of the enquiry. In order
to use the Fast Path ENQUIRY function, the user needs to specify ‘FASTPATH ‘ in the
ATTRIBUTES field. Attributes are only processed with graphical user interface.
Authorize the created enquiry.

CUS-Enquiries-Fast Path-Images 19
 As soon as you execute your Fast Path enquiry it will display you the FT records.
Besides each id is a check box and a status icon. The status icon displays amber flag
before processing any transaction. Use the check boxes to select the required records
for processing. Select the checkbox and choose the appropriate fast path action and
click on the push button. The result of the fast path action is displayed on the status
icons. If the action is successful the flag turns green else it turns red to indicate failure
of the process.

Note : The check box will be displayed only when you specify value as ‘@ID’ in
LABEL.FIELD while creating the Fast Path Enquiry.

CUS-Enquiries-Fast Path-Images 20
 1. If the FT record is authorised T24 displays a message stating that the record was
authorised successfully. You can view the message only for the last record that
has been authorised.

2. You can view the status icon turned green denoting the success of both the
transactions.

CUS-Enquiries-Fast Path-Images 21
 This task teaches you to edit field values as they are part of an enquiry output display.

Take a scenario where the bank suddenly decides that all customers who belong to
sector one thousand one (1001) are to moved to sector one thousand (1000) . Editing
the field values can be done in the application. Is it possible to edit fields using
enquiries?

Yes you can edit fields using enquiries. This section teaches you to create editable
enquiries in T24.

1.Create an enquiry for the CUSTOMER application with the following two fields - @ID
and SECTOR.

2. In the enquiry output screen make the field SECTOR as an editable field, meaning
the person executing the enquiry is allowed to change the value displayed on the
screen for the field SECTOR and then save the changes to the database. Use
CUSTOMER live file.

CUS-Enquiries-Fast Path-Images 22
 You must remember that you can edit only LIVE records. Thus a $NAU or $HIS cannot
be part of the file name the enquiry is based on.

FIELD.DISP.TYPE – For the field SECTOR , choose ‘EDIT’ as the option for
FIELD.DISP.TYPE field. Now the field SECTOR becomes editable when the enquiry is
launched.

ENQUIRY.NAME - Specify the application that will be invoked next. You need to edit
LIVE records. Hence specify the input mode. Then specify any user defined text in
NXT.DESC field. Since it is a FAST PATH enquiry, choose FASTPATH option for the
ATTRIBUTES field. Authorize the created enquiry.

Authorize and execute the enquiry.

CUS-Enquiries-Fast Path-Images 23
 1, 2. When you launch the enquiry , you will be able to view LIVE customer
records. Select the check box for any one of the customer, then edit the SECTOR
field of that customer. After modifying the record select the fast path action and
click the push button.

3. T24 displays you a message to indicate the status of the process. You can see
the modified value in the SECTOR field.

When you refresh the Fast Path Enquiry output, you will not see the records that
you edited since they are now in INAU status and the enquiry is based on the LIVE
file only. Authorize the customer record and execute the Fast Path enquiry to see
the modification. You can edit more than one field in a record using Fast Path
enquiries.

CUS-Enquiries-Fast Path-Images 24
 This workshop aims to test your level of understanding of fast path enquiries in T24.

1. Create an enquiry for the SECTOR application with the following two fields –
DESCRIPTION & SHORT.NAME. Make the SHORT.NAME field as editable one

2. The Enquiry should also allow you to perform the following function on records
displayed
2.1 (A)uthorise
2.2 (R)everse

CUS-Enquiries-Fast Path-Images 25
 This task teaches you how to display images as part of enquiry output in T24.

A bank wants to keep track of the loan amount of all its customers. When the enquiry
that displays the loan amount is launched, the accounts with an amount above one
lakh (100000) must be marked out in the output. This status is indicated by displaying
an image in the first column of that row. To do this task follow the given steps.

1. Create an enquiry based on the LD.LOANS.AND.DEPOSITS application that

displays the fields
1.1 ID
1.2 CURRENCY
1.3 AMOUNT

2. The enquiry must display an image in the first column (indicating critical) if the
balance is above 100000 (lakh);

CUS-Enquiries-Fast Path-Images 26
 You will execute the enquiry only for customer accounts. Therefore specify ‘AMOUNT
NE NULL ‘ in the FIXED.SELECTION field. This condition will fetch only the customer
accounts. The next condition is to retrieve records that has a numeric value in the field
AMOUNT. Hence multi-value the FIXED.SELCTION field and specify ‘ AMOUNT NE
‘’(NULL) ‘ in that field.
OPERATION - mention AMOUNT in the OPERATION field.
COLUMN – The value in AMOUNT field is checked against a constant value.
Therefore you will not specify the column value for this field as the value for AMOUNT
will be checked against a constant value which is shown in the next slide.
The OPERATION field can hold different values.
Second multi-value of OPERATON field specifies the condition to check if AMOUNT
is greater than one 100000(lakh) . The OPERATION field takes different type of
values. In this field you can specify a constant with in quotes as shown here.
COMMENTS - The field COMMENTS gives a description of the associated field.
Third multi-value OPERATION field specifies the path of the image to be displayed.
Images must be stored inside BrowserWeb.war. Ensure that you specify the entire
path of the image enclosed in quotes from BrowserWeb.war.
Next you will specify the condition in the fourth multi-value OPERATION field. You
need to check the value of two fields using an ‘IF’ statement. The value that you
specify here checks the value of two fields, namely AMOUNT and the other field that
holds the constant value. GT is the operand used. If the condition is true then the
image is displayed. The image is displayed from the path mentioned in the previous
OPERATION field. Specify the COLUMN field’s value as 1 as the image has to be
displayed in the first column.

CUS-Enquiries-Fast Path-Images 27
 FIELD.DISP.TYPE - When the condition is true the image is to be displayed, therefore specify
the option as ‘IMAGE’ for the field FIELD.DISP.TYPE .

CUS-Enquiries-Fast Path-Images 27
 Specify the other fields for your enquiry and also the value for COLUMN field for each
field. Authorize and execute your enquiry to view the generated enquiry report.

CUS-Enquiries-Fast Path-Images 28
 1. Launch the enquiry using the ENQ command.

2.The output displays the critical image for the records with LOAN AMOUNT greater
than 100000.

CUS-Enquiries-Fast Path-Images 29
 Context sensitive enquiries supply the enquiry with context sensitive data obtained
from the application currently being edited.

It replaces the need to specify enquiry selection criteria via the enquiry selection
screen.

When enquiries are loaded depending on the application opened, those enquiries are
termed ‘Application Level Context Enquiries’.

If enquiries are triggered when a user tabs out of a particular field in an application
those enquiries are termed as ‘Field Level Context Enquiries’.

The CONTEXT.ENQUIRY application in T24 is used to create such context based

enquiries.

Context-enquiries can be setup to auto-launch another ENQUIRY or APPLICATION or

a VERSION.

CUS-Enquiries-Fast Path-Images 30
 Context-Enquiries may be triggered in a number of ways:
•On opening a particular application, version or ENQUIRY
•On entering some data in a field,
•On committing a record.

Application context enquiries are invoked when an application is launched.

If a context based enquiry is setup for a particular Application in T24 then it would
appear under the ‘Deal Menu’ dropdown where all other default enquiries related to
the application are also loaded. The user may execute these enquiries by simply
selecting it from the dropdown.

Lets understand how to make a pie chart enquiry (TRG.DISP.TYPES.ENQ.PIE)

available as a context enquiry for the LD.LOANS.AND.DEPOSITS application in T24.

CUS-Enquiries-Fast Path-Images 31
 Create a record in CONTEXT.ENQUIRY application for the LD.LOANS.AND.DEPOSITS application and
attach the pie chart enquiry (TRG.ENQ.DISP. PIE) in this record as shown.

The record ID for the CONTEXT.ENQUIRY application differs based on how the enquiry is triggered

1. For application level – Application name (Eg. LD.LOANS.AND.DEPOSITS)

2. For a field in an application – Application name-Field name (Eg. LD.LOANS.AND.DEPOSITS-
AMOUNT)
3. For Versions – Application name,Version name (Eg. LD.LOANS.AND.DEPOSITS,TRG)
4. For fields in a version – Application name,Version name-Field name (Eg.
LD.LOANS.AND.DEPOSITS,TRG-AMOUNT)

•Enquiry Name- Holds the general description of the record

•Sel Field- Holds a valid T24 enquiry name that will be listed in the ‘Deal Menu’ section when the respective
application is launched.

•Operand- Holds the operand to be used on the field specified in ‘Sel Field’

•Target Frame- Used in relation to composite screens.

•GB Enq Desc– The description of the enquiry that will be displayed in the ‘Deal Menu’ section.

•Auto Launch- If set to ‘Y’, will automatically launch the enquiry when the application is opened. Only one
enquiry can have this field set to ‘Y’.

In the illustration , Auto Launch is not set for the pie chart enquiry.

CUS-Enquiries-Fast Path-Images 32
 Launch the LD.LOANS.AND.DEPOSITS application and in the ‘Deal Menu’ dropdown,
the context sensitive enquiry is also listed. Execute the enquiry.

The output of the context enquiry designed earlier is shown. When launched, the
results of the ENQUIRY will be displayed in a separate window.

CUS-Enquiries-Fast Path-Images 33
 Field Level context enquiries are attached to certain fields in an application or a
version.

Fields that have Auto-Launching context enquiries have the icon shown next to the
field label.

Let us attach the pie chart enquiry to the ‘CURRENCY’ field of the
LD.LOANS.AND.DEPOSITS application. When the user tabs out of the currency field,
the pie chart enquiry has to be launched.

CUS-Enquiries-Fast Path-Images 34
 The pie chart enquiry TRG.ENQ.DISP. PIE is shown. The selection field mentioned in
the context enquiry must exist as a selection field in the enquiry for it to be launched.

CUS-Enquiries-Fast Path-Images 35
 The context enquiry is created to auto-launch the pie chart enquiry by setting the field
‘Auto Launch’ to ‘YES’.

When a user exits out of the CURRENCY field in the LD.LOANS.AND.DEPOSITS

application, the context enquiry is auto-launched and the enquiry result will be
displayed in a new window.

CUS-Enquiries-Fast Path-Images 36
 When tabbing out of the CURRENCY field, the context enquiry is triggered. The
example discussed, is only to illustrate how to auto launch field level context enquiries.

CUS-Enquiries-Fast Path-Images 37
 In order to disable auto launch of context based enquiries for a particular user in T24,
set the ATTRIBUTES field to NO.AUTO.LAUNCHES in BROWSER.PREFERENCES.
Although a context based enquiry exists for a particular field in a application it will not
get triggered if this attribute is set.

CUS-Enquiries-Fast Path-Images 38
 1. False

2. True

3. True

4. True

5. True

CUS-Enquiries-Fast Path-Images 39
 1. An Enquiry is a ‘SELECT’ executed in order to fetch data from T24

2. ATTRIBUTES field is set to FASTPATH to create Fast Path Enquiries

3. FIELD.DISP.TYPE field is set to EDIT if the fields value can be edited in the
enquiry output

4. FIELD.DISP.TYPE field is set to IMAGE to display an image.

CUS-Enquiries-Fast Path-Images 40
 In this learning unit you have learnt drilldowns, workflows, fast path enquiries and
graphs in T24.

You will now be able to,

1. Create Drill Down Enquiries in T24

2. Create Context Based Workflow in T24

3. Create Fast Path Enquiries

CUS-Enquiries-Fast Path-Images 41
CUS-Enquiries-Fast Path-Images 42