Topic T24 Document Output

Consultants Funsho Agbalu

Amos Odebiyi
Ramon Yisau
Bolaji Ajiboye
The document output module is used to create, request and process documents in T24.
The set up is as below:
The folder in bnk.run is:

Figure 1:T24DocumentOutput folder

BulkRunReports: contains an excel file of documents requested in bulk. If I request a

document for customers with accounts of a certain category, an excel file will be created
containing info about these files.

CompiledDocuments: contains .jasper files for each document. Documents are built on
T24, when a build happenes, a new .jrxml file and an xml file with a mapping of the fi is
created by T24 and placed in JrxmlDocuments folder.

Images: Images to be used by documents

Pdf: Stores generated pdfs

Repository: Contains pdfs too.

Xml: An xml file mapping the data source to variable is generated too after document
trigger.

A build only generated the sample xml and .jrxml file NOT the pdf or xml. The sample
xml contains a structure of the data sources and their variable. We connect it to the
adapter of the .jrxml when we import it to Jasper. We shall see more below.
  Minor but important configurations

Add an Outward Carrier called ‘DOPRINT’ as seen above in table DE.PARM

Add DE.PRODUCT record as seen above.

In the .profile of your environment, ensure document put’s jar is referenced as a

CLASSPATH, also add the .jar of the different fonts you intend to use in your document
design.
Also change $JAVA_HOME as below
Ensure a .ttf file of the fonts you want to use are stored in the /jre/lib/fonts directory of
your Java installation. “arial.ttf” above is kept in /usr/java/jdk1.7.0_80/jre/lib/fonts.

Next, copy DocRepoWebApp.war to the /server/default/deploy directory of your

JBoss installation like below
Now open a file called web.xml in
/<yourjboss>/server/default/deploy/DocRepoWebApp.war/WEB-INF
In this file, set the values for

- DocRepoRootPath: the root path for document repository. It is <your-t24-

home>/T24DocumentOutput/Repository
- WorkDocRepoRootPath: this is where the pdfs are stored. <your-t24-
home>/T24DocumentOutput/pdf
- WaitNoAttempts: How many times the services BNK/DO.PROCESS.LOCAL &
BNK/DO.PROCESS.BULK should read before returning an error. These services
should be set to AUTO as seen below.
Figure 2:DO.PROCESS.LOCAL in TSA.SERVICE

Figure 3:DO.PROCESS.BULK in TSA.SERVICE

Also ensure that the BATCH records are as below:

Figure 4:DO.PROCESS.LOCAL in BATCH

Figure 5:DO.PROCESS.BULK in BATCH

  DO.PARAMETER:
This table is used to set general parameters for the Document Output module. It must
be set up as below;

Figure 6: The Header & Footer tab contains information about the Header & Footer section of every document to be created.

Figure 7: Address Mapping tab contains info on the address to be included on each document
Figure 8: Some documents are produced by T24's DE module, in Delivery Settings tab, we set the print Server URL
  DO.DATA.SOURCE
A data source is where we intend to get the data we intend to present as information on
our document. Below, is a simple data source for getting Customer, Category and other
stuff.

T24 Source File field contains the T24 table where we get data from

 Customer field contains the field in the T24 source file that contains the customer
record
 Field name contains the name of the field as we want it specified when we are
creating our document.
 Type contains the type of data in the field where we will get our data from
 Source field is the field in the T24 Source file (ACCOUNT in this case) where we
will get data from.
 Conversion contains any relevant conversions. For example, we use the category
field here to read the CATEGORY table to get the description of the category of
each account.

This is how a simple data source works, now let’s examine a more complex data source.
Below we see the data source records for a dynamic table, external images and a jBase
routine.
In this case study, we are building a document for loan applicants which will be
produced after a customer completes his or her loan application.
EM.LO.APPLICATION is the module used for Loan Origination, we will use this table
as a base table.

Note that there are other platform for collecting data, T24 Delivery option is for
DELIVERY module related data, T24Environment is that which is mapped from T24
environment, like current date and time, used to map data from user input during
document generation, External is stuff from outside T24 db, like an excel file or an
image. User Input is for data that will be inputted by the user during document
generation. Only one Source Type applies per DO.DATA.SOURCE record. However,
you can one document can have multiple data sources. We shall see this in our
document.

Figure 9:Complete Data Source Record for EM.LO.APPLICATION

Figure 10:Images Data Source

Above, we have the data source for the image we will use in our document. It is the
bank’s logo. Don’t forget to put this image in the /T24DocumentOutput/Images folder
in bnk.run. A screen shot of this folder is in figure 1.
Figure 11:In this data source, we are getting data via some routines

The data source above makes use of some routines to get some data. The routines must
be prefixed with DO.XX.CONV and must also have an EB.API record. The T24 source
file is the file from which we intend to find the data we are looking for. Here, it is
AA.ARRANGEMENT. We are going to use arrangement ID in our primary data source
called GCLoans to link to this data source called GCArrngements and use the routines
to calculate charge amount, total payment per installment, term in days. Therefore, to
be able to link two data sources, they should have at least one field in common.
Next, we will attach these data sources to:

Figure 12:Our main data source is linked to another data source

Here, Images is added as another data source. We linked GCLoans to GCArrangements

using the arrangement ID.
  Document Trigger
A document is triggered in 2 ways;

1. Manually – to request a document manually as in below

Figure 13:DO.REQUEST.DOCUMENT

This ID of DO.REQUEST.DOCUMENT is the ID of our document. In WelcomeLetter,

the data source base file is CUSTOMER, so our data source ID will be the Customer ID
of the customer the document belongs to. If we are to request for a large number of
documents, we do a bulk request as below:
Figure 14: DO bulk request

When doing a bulk request, Action – determines whether this is a test run or a real run.
Selection Type – determines the type of selection we are making. If criteria, then the
below is presented. List – is a select list, Command – use a command Routine – is for a
routine based selection
Figure 15:Criteria based selection

Here, we choose the T24 Source File if applicable Then the Criteria Name is a
description of this criteria, after this, we add Field/Operand/Value in a select format.
Eg: CUST.TYPE EQ ‘I’ to request for individual customers alone.
 2. DO.DOCUMENT.TRIGGER:
We can also trigger a document using this table. It’s ID is the version that will trigger
the document. For example, if we want the document triggered after a customer is
created; the id of our record is the customer version we will use to create a customer. In
our case study, we want the document to trigger after Loan Creation stage of
EM.LO.APPLICATION. We had to do it at this stage because it is when AA assigns an
arrangement ID to our loan application. So the ID for our document trigger record is
EM.LO.APPLICATION,LOAN.CREATION.

Figure 16:DO.DOCUMENT.TRIGGER record. ID is the version that triggers the document.

Above, the DO.DOCUMENT.TRIGGER record for the version has 2 documents. The
first document is SMELoan, the function that triggers it is when an “input” is
committed. Other functions are Authorization.Input, Authorization.Revrsal, Reversal.
We can also make use of Field/Operand/Value as a criteria. For example, we chose to
generate SMELoan when PRODUCT.ID in EM.LO.APPLICATION is equals
InstitutionalLoan. So when the loan applied for is InstitutionalLoan, this document is
generated otherwise, nothing happens.
Finally:

Open VERSION.CONTROL record for EM.LO.APPLICATION as seen above.

Figure 17:VERSION record

We must ensure that this program; DO.VI.TRIGGER.DOCUMENT is attached as an
Authorization routine in the version concerned.

In Jasper:

After building a document in DO.DOCUMENT, T24 generates a .jrxml file and a sample
xml file and places them in /T24DocumentOutput/JrxmlDocuments. From there, we
will export them to our Jasper. The design phase is described in the Part II of this
tutorial.