Loading ...
Loading ...
Loading ...
T24 Application Development
Creating an Application
Naming
The name of the application must be meaningful, should give some indication as to its purpose and
should be prefixed by the product code of the application, where the product code should exist on
EB.PRODUCT e.g. CR.CAMPAIGN.DEFINITION, PW.ACTIVITY, etc.
Note: The file name cannot exceed 40 characters, to allow for the addition of the company mnemonic
and the $NAU or $HIS suffix.
Step 1 - Defining the Application
Having decided on the product and name of the application, the first step is to define the high level
properties of the application. The example “TEMPLATE”, which ships with each release of T24, holds
the properties for the application. Whilst there is tooling support for the creation of new applications,
this section explains the mechanics behind the GUI.
Property Example Explanation
name CR.CAMPAIGN.OPPORTUNITY Full application name including the
product prefix. Must be the same as
the application name
title Campaign Opportunities Screen title
stereotype H See “Stereotypes”
product CR The product of the application. Must
be an entry on EB.PRODUCT
subProduct CAMPAIGN The sub product of the application.
Must be an entry on
EB.SUB.PRODUCT
classification INT See “Classifications”
systemClearFile Y Flag to indicate if the file should be
cleared down when running the
SYSTEM.CLEAR.FILES utility.
Should be set to YES for any
transient (i.e. financial) applications
relatedFiles CUSTOMER
CR.CAMPAIGN.DEFINITION
A space delimited list of related files.
Used in creating the data model
isPostClosingFile Y or blank. Only required when the
application is required for use by
Post Closing. Normally this should be
left blank.
equatePrefix CR.CD Used to create the insert for the
application that contains the equated
field names
idPrefix CRCD If set, invokes EB.FORMAT.ID to
produce transaction reference style
keys
TEMENOS T24 User Guide Page 4 of 34
Loading ...
Loading ...
Loading ...