PROCESS WORKFLOW

Application Overview

T24 Process Workflow is aimed at grouping various businesses and banking procedures into a
logical process of activities. This grouping enables allocation of work to different users, ensuring
vital tasks are left out causing a breakdown or delay in the process chain.
Individual activities are defined at micro level defining rules, statuses and user groups, which can
all be reused. These activities are then set out in a pre-defined sequence allowing a customized
business processed to be followed.

This module does not carry any business functionality but can be used to define and tune the flow of
business supported by other T24 modules.

Application Design

[Link]

Figure 1 – [Link]

An [Link] record must be set up for the [Link] and [Link] tables,
with an ID format of the following:
For [Link] table – ‘PW’YYJJJnnnnn. Where YY = Year, JJJ = Julian date and nnnnn =
sequence number.

For [Link], the setup is the same but for the prefix of ‘PA’. – ‘PA’YYJJJnnnnn.

Once the [Link] record has been committed and authorised a LOCKING record will be
created for [Link] and [Link] containing the start Id’s for
each file.

If these records are not set up correctly, when launching a new [Link] record in T24
Browser, a blank screen will be displayed.

To correct this, reset the LOCKING records by correcting and recommitting the [Link]
record for PW. The Cache file for Browser, [Link], will also need to be cleared of all
records pertaining to [Link].

LOCKING

Figure 2 - LOCKING

LOCKING records for [Link] and [Link] will be

automatically created once the [Link] record for PW has been committed and authorised.
COMPANY

Figure 3 - COMPANY

The [Link] table (only) must be entered into the [Link] field on the COMPANY
record to enable automatic creation of ID’s.
[Link]

Figure 4 – [Link]

Status codes are defined separately and attached to [Link] records. They are needed to
define the default status or starting status of an activity ([Link] on the
[Link] record) e.g.. PENDING, and are also used to set the [Link], in
conjunction with a [Link], on the [Link] record when the conditions of the rule
has been met.
[Link]

Figure 5 – [Link]

This table is used to group Users or Account Officers together and is attached to either the
[Link] or [Link] record. A User/Account Officer is then automatically allocated to
an Activity, spreading the workload systematically between all users/ Account Officers within the
[Link] group.

This helps Users/Account Officers in identifying their daily work by using an Enquiry to drill down
and launch their specific tasks.
[Link]

Figure 6 – [Link]

Transition rules are attached to activities via the [Link] or the [Link]
table. These rules determine when the status of an activity changes and the status further determines
if and when a subsequent activity can appear on the [Link] list for a user and hence be executed.
[Link]

Figure 7 – [Link]

These records are used to map data from one activity record to another. The Mapping ID is attached
to the [Link] record where the data is to be mapped to. EG. If in a process a CUSTOMER
record is created, then an ACCOUNT record for that customer and you wish to map certain data
from the customer record to the account record, the [Link] record will be attached to the
[Link] for the account activity.

Please refer to the Data Mapping Worked Example for further information.
[Link]

Figure 8 – [Link]

This table can be used to define common field links to map data to be attached to the
[Link] table. This table allows data links to be re-used.

Please refer to the Data Mapping Worked Example for further information.
[Link]

Figure 9 – [Link]

These records determine the status, transition rules, duration, data mapping and so on of an activity.
The TARGET field defines which T24 application will be launched when the activity is executed; it
details how the application will be run i.e. how the application is usually executed from the
command line. The TARGET can also be an [Link] or [Link]. See
the [Link] user guide on how to create user defined tables within T24.

Please refer to the Data Mapping Worked Example for further information.
[Link]

Figure 10 – [Link]

This table allows the linking of activities together in a logical business flow. It defines when an
activity is enabled depending on pre-required Activities and their Statuses or Transition Rules. So
[Link] helps not only in defining the activities to be a part of the process, but
the sequence and the stage at which they have to appear in the process.

ENQUIRY

Launching of activities takes place through a drilldown ENQUIRY of the [Link] file,
allowing a user to automatically launch the activities from the enquiry.

A basic [Link] and [Link] ENQUIRY comes as part of the T24 PW module.

Specified key words in these enquiries allows Process Workflow to function and care must be taken
to not delete or change vital fields in the basic ENQUIRY, [Link].
See the below example of the important fields involved.
A [Link] field on the ENQUIRY record, as in the above example, must contain the data ‘PW’,
along with the [Link] being set to ‘PWACTIVITY’.

And an [Link] field on the ENQUIRY must contain the launch functions as in the above
example.
If the ENQUIRY is not set up correctly intermittent problems will occur, with activity status’s and
[Link] records not being updated, and mapping not working.
[Link]

Figure 11 – [Link]

The first step in setting up and starting a process is by creating a [Link] record. This
contains the [Link] record that defines and determines the flow of activities
to be executed.

Once the [Link] record has been committed in Authorise mode, for each activity set up on
the [Link] record that has no [Link] attached to it, a
[Link] record will be automatically generated, thus only allowing activities to be
executed once previous tasks or activities have been performed. These [Link] record
IDs along with some detail are written to the [Link] record.
ENQUIRY

Figure 12 – Enquiry Process Workflow status

Now that the process has been created, running the ENQUIRY, [Link] displays all
activities and their statuses that can be or have been executed. Drilldown on the enquiry will allow
the chosen activity to be executed automatically.
 Figure 13 – Enquiry PROCESS ACTIVITY TXN

The standard [Link] ENQUIRY allows activities to be listed per user, which allows a specific user to
concentrate on their allocated tasks.
[Link]

Figure 14 – [Link]

This file contains the records of all activities that can be or have been executed. Once an activity
has been executed the [Link] field contains the ID of the record of the T24 or
[Link] application that was executed.

Upon completion of an activity, the system scans through the [Link] record
and creates [Link] records for all activities that could be started if their [Link]
has been met.

[Link] Id’s are automatically generated by the system (as long as the [Link]
record has been set up, see ‘Setting Up of the System’ document for PW), these records cannot be
created manually.
Data Mapping Worked Example

Taking into account that the [Link], [Link], [Link], [Link] and
[Link] records have been created.

In the following example we will be mapping data from an ACCOUNT application to a

[Link] application.

Two [Link] records are created; one to launch an Account application; the other to launch a
Funds Transfer application.

Figure 1 – [Link] Record

Figure 2 – [Link] Record

A [Link] record is created, this will detail where the data is to be extracted from and where
it is going to.

[Link] details what type of T24 application this record is going to be attached to, in this case it
is an FT application.
[Link] any description can be chosen so long as it matches it’s corresponding field
[Link].
[Link] : This field dictates what data is being mapped and where it is coming from. In this
case the field CURRENCY in the [Link] record [Link].
[Link] is the data is being mapped to, this field must exist in the application detailed in the
[Link] field, in this case [Link].

Figure 3 – [Link] Record

The [Link] record is attached to the appropriate [Link] record in the [Link]
field.

Figure 4 – [Link] Field

A [Link] is created with the two [Link] ’s listed.

 Figure 5 – [Link] Definition

A new [Link] is created.

Figure 6 – [Link] Definition

A composite screen with the ENQUIRY [Link] is launched.

The PW serial numbers are the [Link] ID.

The PA serial numbers are the [Link] ID

We can see that the Account Activity is first in the launch list.

Figure 7 – Account Activity

The [Link] launches an ACCOUNT record that is populated and committed, note
the currency is CHF.

Figure 8 – Account Record

Once the Account record is committed and the Enquiry refreshed, the [Link]
activity has the committed record’s ID displayed.

Figure 9 – [Link] activity

The [Link] activity is activated and launches a FT application.

On launch of this record the Currency type is mapped from the Account activity to the
[Link] field, the record may now be populated and committed.

Figure 10 – FT Record (Debit Currency field)