Learning Community

Core Banking
AA Technical Customisation

Guide (R18) (English)

2019 Q2

-'.��, TEMENOS
 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Table of Contents
Table of Contents ............................................................................................................................... 2
History ............................................................................................................................................... 4
Introduction ....................................................................................................................................... 5
Your Course ............................................................................................................................................................... 5
Objective and Learning Outcomes ........................................................................................................................ 5
Adding Local Fields to AA .................................................................................................................... 6
Adding Missing Field to AA ....................................................................................................................................... 6
Adding Missing Field to AA .................................................................................................................................... 6
Local Reference Fields ............................................................................................................................................... 6
Local Reference Fields ........................................................................................................................................... 6
Demo ..................................................................................................................................................................... 6
Practice......................................................................................................................................................................8
Practice 1 ............................................................................................................................................................... 8
Customizing AA Screen Layout with Versions ...................................................................................... 9
Scenario.....................................................................................................................................................................9
Scenario ................................................................................................................................................................. 9
ACTIVITY.PRESENTATION .......................................................................................................................................... 9
ACTIVITY.PRESENTATION ...................................................................................................................................... 9
Demo ...................................................................................................................................................................14
Points to Remember............................................................................................................................................17
Practice....................................................................................................................................................................18
Practice 1 .............................................................................................................................................................18
Enhancing Functions With Named Activities ..................................................................................... 19
Product Tracking .....................................................................................................................................................19
Product Tracking..................................................................................................................................................19
Activities .................................................................................................................................................................. 20
Generating Activities ........................................................................................................................................... 20
Automatic Generation ............................................................................................................................................ 20
Automatic Generation ......................................................................................................................................... 20
Named Activities ..................................................................................................................................................... 21
Named Activities ................................................................................................................................................. 21
Activity Logs ............................................................................................................................................................ 23

Guide (R18) (English) 2019 Q2 2

 . $TEMENOS
Core Banking Technical Customisation Learning Community

Activity Logs......................................................................................................................................................... 23

Guide (R18) (English) 2019 Q2 3

 . $TEMENOS
Core Banking Technical Customisation Learning Community

History
Author Version Release Date Comments

TLC CaTS 1.0 19-Apr-19 Initial document.

Guide (R18) (English) 2019 Q2 4

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Introduction
Your Course
Objective and Learning Outcomes
• This course will allow you to:
■ Manage Local Reference Fields, customise AA screens, manage the ACTIVITY.PRESENTATION property
class and named activities.
• In particular you will be able to:
■ Attach local reference fields to a property class.
■ Create property and product condition for ACTIVITY.PRESENTATION.
■ Explain how ACTIVITY.PRESENTATION works.
■ Describe Activity and Activity Classes.
■ Manage named activities.
Here's the timetable. We've just started on the Introduction lesson. Following this we'll cover Adding Local Fields
to AA, Adding Versions to AA and Enhancing Functions With Named Activities.

Figure 1 Timetable

Guide (R18) (English) 2019 Q2 5

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Adding Local Fields to AA

Adding Missing Field to AA
Adding Missing Field to AA
• Consider a scenario where you wish to store sector information of the customer with the arrangement rec­
ord. But the CUSTOMER property class does not have a SECTOR field. What can be done?

Local Reference Fields

Local Reference Fields
• Is it possible to add user-defined fields to a property class like you add local reference fields to an application?
• The answer to the question is YES. Adding local reference fields to a property class is similar to adding local
reference fields to an application.
• You will now learn the steps involved to do the same.
• Properties in AA share the same set of fields among five different applications like:
■ AA.PRD.DES. < PROPERTY.CLASS> - Designer
■ AA.PRD.PRF.<PROPERTY.CLASS> - Proofing
■ AA.PRD.CAT.<PROPERTY.CLASS> - Catalogue
■ AA.ARR. < PROPERTY.CLASS> - Arrangement
■ AA.SIM.< PROPERTY.CLASS> - Simulation
• AA allows automatic replication of the Local Reference Fields to the files.
Adding a field to a property means to replicate the same across all the four files. Instead of doing so, AA allows you
to add the Local Reference field just to one file and Core Banking automatically replicates the field to all the other
files. This is how the whole Core Banking architecture for AA works.

Demo
• Create a local reference field called (UST.SECTOR for the CUSTOMER property class.
• Create a local reference field called CUST.SECTOR.
• Attach the local reference field to the CUSTOMER property class.
• Check if the field has been attached to the CUSTOMER property.
Proof the product. After proofing the product and before publishing the product, record gets created in an applica­
tion called AA.PRODUCT.TRACKER.PROOF with the changes. If you notice, a product called MORTGAGE.OFFER has
been proofed and record is created in AA.PRODUCT.TRACKER.PROOF as the condition for tracking property
NEWARRFEE has been changed.

Guide (R18) (English) 2019 Q2 6

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• Create a local reference field in the LOCAL.TABLE application.

OC L ABLE CUST. SECTOR ( odel. Bank R 3)

GB Oescripti on Sec or or cu omer

GB Short ame CUST.SECTO
·mum Char s
Curr No 2
lnpu tter.1 .28 PUTTE OFS B O SE TC
Date Time. 06:06 2 EB 06.
Authoriser 28 OFS. B TC
Co Code G -00 od Ban 13
Dept Code nip n n

Figure 2 Local Reference Fields

Attach the local reference field to the AA.PRD.DES.< PROPERTY.CLASS> file. If you see here, the local reference field
CUS.SECTOR has been added to AA.PRO.DES.CUSTOMER file.

LOCAL. EF.TABLE, AA.PRO.DES.CUSTOMER PRODUCT DESIG ER CUSTO ER

Local Table No.1 CUST.SECTO CUST.SECTOR

Curr No
lnputter.1 -
428 I PUTTER OF -BRO SERT
Date Time.1 2 FEB 1406:05 12 FEB 14 06:05
Authoriser 428 PUTTER-OFS-BRO SERTG
Co Code GB-00 -000 odel Ban R13
Dept Code fmple, ,entation

Figure 3 Local Reference Fields

Guide (R18) (English) 2019 Q2 7

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

When the LOCAL.REF.TABLE record is authorised for the designer, standard selection records of the property's
proof, catalog and arrangement files are rebuilt along with the designer record. To see this local reference field in
an arrangement, you should add it to appropriate versions. You will learn how to do this in the coming few slides.
Note: When local reference field is added for an application, the same field is added to all the applications for which
the field "Local Ref Master" in FILE.CONTROL record is set to the current Application name.

-
STANDARD.SELECTIONIAA.PRD.DES.CUSTOMERI (Model Bank R13)

Usr Field Name.1 [cusr.sEcroRI

-
Usr Type.1 STANDARD.SELECTIONIAA.SIM.CUSTOMERI (Model Bank R13)
�
Usr Field No.1.1 ILOCAL.REF<l,l>I
Usr Field Name.1 ICUST.SECTORj
Usr Val Prog.1.1 [1N2 I Usr Type.1 �
-
Usr Display Fmt.1 isR I STANDARD.SELECTIONIAA,PRD.PRF.CUSTOMERI (Model Bank R13)
Usr Field No.1.1 ILOCAL.REF<l,l>I
Usr Single Mult.1 �
Usr Val Prog.1.1 [1N2 I Usr Field Name.1 [cusr.sECTORI
Usr Lang Field.1 �
Usr Display Fmt.1 isR I Usr Type.1 �
Usr Single Mult.1 Usr Field No.1.1 ILOCAL.REF<l,l>I
Usr Lang Field.1 � Usr Val Prog.1.1 [1N2 I
Usr Display Fmt.1 [SR I
Usr Single Mult.1 �
Usr Lang Field.1 �
lsTANDARD.SELECTION�RD.CAT.CUSTO� (Model Bank R13)

Usr Field Name.1 [cusT.SECTORI STANDARD.SELECTION[AA.ARR.CUSTOMERI (Model Bank R13)

Usr Type.1 �
�---� Usr Field Name.1 lcusT.SECTORI
Usr Field No.1.1
Usr Val Prog.1.1 Usr Type.1 �
� ---�
Usr Display Fmt.1 Usr Field No.1.1

Usr Single Mult.1 Usr Val Prog.1.1

Usr Lang Field.1 INJ Usr Display Fmt.1
� -��--�----------,
Usr Single Mult.1
Usr Lang Field.1 �
Figure 4 Local Reference Fields

Practice
Practice 1
• User wants to capture change in commitment amount in an user defined field. Create a user defined field
that will capture the required information when an activity is being performed in an arrangement.
• Use LOCAL.TABLE and LOCAL.TABLE.REF application to create local reference field and attach it to the prop­
erty class. Name the field as AMOUNT.CHANGE.

♦.♦
•♦

Guide (R18) (English) 2019 Q2 8

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Customizing AA Screen Layout

with Versions
Scenario
Scenario
You created a local reference field called (UST.SECTOR. This field does not appear while creating an arrangement
How will you add the local reference field to the version using which you create an arrangement?

llew Arrangement Audit

Arrangement IAAD8009DLDFY! NE\f\f. CUST = t-,AA SHIPPING co 1IPANY OF PANAMA

Customer i I 100724j /!.AA SHIPP! L, COMPANY OF PANAM.ll.
Product I PERSONAL.LOAN.2WI Pe sonal Loan
Activity ILENDING-NEW-ARRANGEMENT I
Customer I Account Officers I Limit I Account I Commitment I Principal Interest Penalty Interest I ft, ein am

Customer

Primary Owner l 1007241 AAA SHIPPING COMPANY OF PANAMP..

Owner.1 j100724 I :y AA.fl, SHIPPING COMPANY OF P.ll..NAM.�
Figure 5 Scenario

ACTIVITY.PRESENTATION
ACTIVITY.PRESENTATION
You will now learn about certain property classes starting with ACTIVITY.PRESENTATION. What is a Version and why
is it used? A version is used to allow users to enter data in a custom designed screen rather than in the original
application screen where all fields of the application appear one after the other. What is an ACTIVITY.PRESENTA­
TION property class? This class is used to attach version to an activity dynamically.
• What is a Version?
• Why do we use Version?
• What is ACTIVITY.PRESENTATION property class?
Using ACTIVITY.PRESENTATION property class versions can be attached at three different levels. Versions can be
attached at the Property Class level, Property level or at the Activity level for an arrangement. If versions are at­
tached at all the levels then priority will be first set to the one attached at the Activity level, then Property level and

Guide (R18) (English) 2019 Q2 9

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

the least specific will be the version attached at the Property Class level. Depending upon the Product and Activity
Core Banking will decide which version should be invoked.
• ACTIVITY.PRESENTATION property class allows users to attach versions at three different levels:
■ Property Class
■ Property
■ Activity
• Purpose - Required version can be displayed based upon the activity being triggered.

Least Specific Most Specific

Property Class Property Activity

Figure 6 ACTIVITY.PRESENTATION

We will now see how to use the ACTIVITY.PRESENTATION property class. The first step is to define the required
versions. Might have come across two sets of applications. One prefixed with AA.ARR.XXX and another prefixed
with AA.PRD.DES.XXX. The next question that you might get is to which file should you create versions. You should
be clear by now that the files prefixed with AA.PRD.DES.XXX are used to define product conditions for a property
class. The files prefixed with AA.ARR.XX hold the actual arrangement details. While performing activities on ar­
rangements, the files prefixed with AA.ARR.XXX are used. Hence we must create versions of the AA.ARR.XX appli­
cations for ACTIVITY.PRESENTATION. To understand how ACTIVITY.PRESENTATION property class works create
three versions for AA.ARR.CUSTOMER file.
• AA.PRD.DES.XXX
• AA.ARR.XXX

AA.PRO.DES.CUSTOMER L

Id Description Reserved Owner Primary owner

ltHl:RMEOIAR.V-20071205 INTERMEDIARY
HEGOTIABLE-20000101 Negotiable
STAHOAR0-20071205 STANOARO
T24.UPOATES-20001130 T24 Updates

AA.ARR.CUSTOMER L
Id Activity Action Owner Primary owner
AA07346GH62R-CUSTOMER-20071212.1 LENDING-NE\I\J-ARRANGEMENT UPDATE 100315 100315
AA07346P7KYT-CUSTOMER-20071212.1 LENDING-NE\I\J-ARRANGEMENT UPDATE 100224 100224
AA07346QHSLQ-CUSTOMER-20071212 .1 LENDING-NE\I\J-ARRANGEMENT UPDATE 100224 100224
AA07346TNZLV-CUSTOMER-20071212.1 LENDING-NE\I\J-ARRANGEMENT UPDATE 100283 100283
AA080090NSC5-CUSTOMER-200801 09.1 PROXY .SERVICES-NE\I\J-ARRANGEMENT UPDATE 100367 100367

Figure 7 ACTIVITY.PRESENTATION

Guide (R18) (English) 2019 Q2 10

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

You can see three versions here. AA.ARR.CUSTOMER,PC is for the CUSTOMER property class. AA.ARR.CUSTOMER,P
is for the CUSTOMER property and AA.ARR.CUSTOMER,ACTIVITY is for the CUSTOMER update activity. What you
see here is a set of three simple versions where only one field has been added. For better understanding and iden­
tification, the text for the field ACTIVITY displays the level at which the version has been created. After creating the
versions, the next step is to attach the version to a product. For this we will create a product condition.
VERSIOI L ,.p.. ,,f'./R IJ�T .1 1.@J!

Records Per ?age 1

Fields Per Line lw.Jltll
Language Cod e.1 1 English
Field No.1 ACTIVITY
Column . 1 1 � 1-.AAR ClfSTOMER.PijOP�_

1--Text Char Max . 1 �

-----
Text. 1 . 1
-----------...ords Per Page
VERSION FOR CUSTOMER PROPERTY CLASS �
1
s Per Line lhllti
Enridim Char. 1 � guage Code.1 1 English
Table Column. I
I
1 1 34j d llo . 1 ,ACTIVITY
Table Lfne . 1 0 Jmn . 1

I
Tsl
I
Text Char Max.1
. :-::-� R CUSTOMER.A 1 (200912.001 Model Bank)
Text. 1 . 1 VERSI ON FOR. CUSTOMER PROPERT 1
Y

Enrichm Char.1 401 Per Page fT

Table Column . 1 1 134] �r line �ltf
Table line .1 e Ctlde, I � English
'-------=------------'
Field No. 1 :ACTIVITY
Column. I

I Text Char Max . 1

Text. I . 1
' Enrlchm Char. I
VERSION FOR CUSTOMER ACTIVlN

I
I Tab le Column. 1
Table Line. I
Figure 8 ACTIVITY.PRESENTATION

Use the Product Conditions menu item from the Admin Menu. A list of property classes will be displayed. Create a
new Product Condition for ACTIVITY.PRESENTATION property class called CUSTOMERAP. If you look at the new
record, it allows you to attach a version for a Property Class, Property or Activity and these fields can be multi­
valued. Any number of versions can be attached at all the three different levels. SUPPRESS.SEE.MODE : When this
field is set to "Yes" in the Product Condition, and an activity is performed on the arrangement, only properties for
which the activity allows user input will be displayed in the arrangement screen. All other properties which are
normally opened in "No Input" mode will be hidden from user view. Eg., When the user performs an activity say
LENDING-DECREASE-COMMITMENT ( LENDING-DECREASE-TERM.AMOUNT Activity Class) the properties which be­
long to TERM.AMOUNT and PAYMENT.SCHEDULE property class will only be opened in Input mode.

Guide (R18) (English) 2019 Q2 11

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

When the field SUPPRESS.SEE.MODE is set to YES in ACTIVITY.PRESENTATION product condition only properties
for which user input is possible is shown to the user, other properties are hidden from user view.

Classes Product Condllions

Om li> Clm �,iptfon

ACCOUHi Account S\Alx
ACCOUITTJ!ll;. Accounon1 U.k
ACTMTY,APt ,lctMty !.JII
ACTMTY.OiARGES ActMty C!Ytp,
AC!lVil'Y,/MPf'INC ActMty Mapi,11111
ACTMTY.MruAGlHC Ac tM ty Me<"'l"'f
ACTMIY.Pllt$E MTlOII Ac:1Mtv P,•1"'<>1ion ••1
ie-!
�----------� .!l

if24 EDITOR
i '-l4re -'dlons _ _3 •'•
Pl'l>duet Ca,,dl11oM - ACTMTY PR1SOOAl1(lfl CIJSTOMfllPR£smTAT10N-l013Gl22 (Model Bani()

GIi De«rlp�O<I
Suw r•» $e-c Mod. r
Oetoult Vtll>CS Il NCiQtiaiKln lwlc> H� I
A<tivity I Property Sim Vco(on

Property

Property 01»

=::..:.=:=.::.:..,.; =..:.==:e., = {""'All

.c.·..,_.O,c.:::
ll lo.::,
l09.c-·12 ,e,..,,J; :.__�----------------------------- ;91
,,,,Q_,,:f • ,:!
Figure 9 ACTIVITY.PRESENTATION

Guide (R18) (English) 2019 Q2 12

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

If you notice, for the property class CUSTOMER, AA.ARR.CUSTOMER,PC version has been attached. For the property
MYCUST, AA.ARR.CUSTOMER,P version has been used. For the CUSTOMER update activity (LENDING-UPDATE-MY­
CUST), AA.ARR.CUSTOMER,ACTIVITY version has been attached. What you have to notice here is that, for a single
activity multiple versions can be attached for different properties. For the CUSTOMER update activity two versions
have been attached, one for the CUSTOMER property and another for the ACCOUNT property.

ram · s -· .d �
'ons • ACTIVITY PRESENTATION 12 (Model Bonk)

• rEST PRE.SNTATioN
r

Activity Version Sim Ve!'lion

�UST- Q AA.AAR.CUSTOMER,ACTIVITY
[A;CCOUNT
___ {g IAA.ll_JlR.ACCOLl':l�IMPlf

AA.ARR.CUSTOMER,P

AA.ARR.CUSTOMER.PC

Figure 10 ACTIVITY.PRESENTATION

Attach the product condition to the property of ACTIVITY.PRESENTATION property class for the appropriate prod­
uct. After the adding the product condition, proof and publish the product.
Product Design�r PROD . FOR.ACT. PRES-201 3�322 (Model Ban k R1 3)

_L!>rodu ct Desi gn er jI Property Con di ti ons lf Vqri ati d� l Lcatculati on Sou re� Au di i j
Property Conditions Arrangement Link Effective Variation
�OUN� -
PERSONAL LOAN
- - -'
���-Tracki_llg;
ACCOUNTI NG LENDING Tracking
ACTIVITY . MAPPING' LE N DI NG
PRESENTATION CUSTOMERAP'
MYCUST NEGOTIABLE ,Non Tracking
PR I NCI PALINTj FIXEO. RATE. 5% 'Non Trackin�
·�.PR I NCf PAL DECREAS� �RI N CI PAL. DECREASE �racking_
SCHEDULE 'C ONSTANT. BI WEEKLY (Non Trackin_g,
COMM ITME NT MY.TERM .AMOUNT ,Non Tracking,
Figure 11 ACTIVITY.PRESENTATION

You will now see the different versions being triggered by T24 dynamically based upon the Arrangement Activity.
Create a new arrangement. The version for CUSTOMER property has been attached. Always the most specific ver­
sion will be invoked. If you remember, versions have been attached at all the three levels (Property class, property
and Activity). T24 will first check for the activity. When you create a new arrangement, the activity is LENDING­
NEW-ARRANGEMENT. You have not attached any version for this activity. So, T24 will move to the next level, that
is the Property. You do have a version attached at the CUSTOMER property level. T24 will fetch that version and
display it to the user.

Guide (R18) (English) 2019 Q2 13

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

If you would have not attached any version at the property level, T24 would check if there is any version attached
for the Property Class and display it. If versions are not available at all the three levels, T24 will display the default
screen.
[a IEIICilllt:D.. t::i lr,rore Actions ... 3 m
�w Arrangement[AAACT1 308 1 4BKBYZ01j (Model Bank R13)

j New Arrangement IQ�

Arrangement [AA130812YC58J Customer 1100301 Allegra
Product �d for Act Presentati on Variation Currency USQ] US Dollar
Pricing Pricing P(an

I
(N'ev, Activity For Arraneementj Effective Date [22 MAR 2013/

Reason

61
MY CUSTOMER PROPERTY Account I Commitment I Principal In terest Schedule

MY CUSTOMER PROPERTY -----------'------------------------1

VERSION FOR CUSTOMER PROPERTY

AA.ARR.CUSTOMER,P

Figure 12 ACTIVITY.PRESENTATION

Consider that you are trying to update the CUSTOMER information for an arrangement. The activity that would be
triggered will be LENDING-UPDATE-CUSTOMER. You have attached a version for CUSTOMER property and a version
for ACCOUNT property for this activity. If you see here those two versions have been invoked by T24 dynamically.
Note: The Field ACTIVITY with text AA ARR SIMPLE VERSION is added to the version AA.ARR.ACCOUNT,AA.SIMPLE
in model bank version AA.ARR.ACCOUNT,AA.SIMPLE.
isArrangement
�1'11
-..
@i&i@fr!fflAA 1 308 1 ZYC58 (ACCOUNl)
-.
-.-,.
-.-.,
-..
-,.
-.-.-------------------�

Customer A l l egra ( 1 0030 1 )

C ustomer CHANGE.PRIMARY ACTIVITY FOR MYCUST I!;(, TI Simulate ..:J

UPDATE ACTIVITY FOR MYCUST

--..Ea-
Back to: New User Ac tivi ti es :=:

"' More Actions ... 3 en

Arrangement Activity!AAACT1308 1 12R6SFWH! (Model Bank R13)

J Arrangement Ac tivity �A�dit-i

Arrangement /AA13081ZYC58[ 65420 Personal Loan
Customer [100301[ Allegra
Product jProd for Act Presentatio n! Currency �
Activity [UPDATE ACTIVITY FOR MYCUill Effective Date [22 MAR 20l31

- GB Narrative

MY CUSTOMER PROPERTY I Account I Princieat I n terest I Schedule I Commitment

1 MY CUSTOMER PROPERTY
VERSION FOR CUSTOMER ACTIVITY <J:tt: N0tN&UPDATE·MYCUST I
Account
1 - - · - · - · - · - · - · - · - · -i
AA.ARR.CUSTOMER,ACTIVrTY I
Ac count Type !Persona l Loan1
AA ARR SIMPLE VE.R SION /ENDI NG·NEW·ARRANGEMENlj
Ac c o u n t Number � ·-·-·-·-·-·-·-·-·-·-·-·-·7 AA.ARR.ACC:OU NT,MS IMPLE I
Figure 13 ACTIVITY.PRESENTATION

Demo
• Attach the local reference field CUST.SECTOR to the version AA.ARR.CUSTOMER.
• Attach this version to activity LENDING-NEW-ARRANGEMENT in ACTIVITY.PRESENTATION product condition.

Guide (R18) (English) 2019 Q2 14

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• Create a version for AA.ARR.CUSTOMER and add the CUST.SECTOR field.

• Attach the version to the LENDING-NEW-ARRANGEMENT activity in ACTIVITY.PRESENTATION product con-
dition.
• Attach condition to product. Proof and publish.
• Create an arrangement.
• Create a version for AA.ARR.CUSTOMER and add the CUST.SECTOR field.

Rec ords Per Page 1

Fields Per line 1
Field N o . 1 0 ER xx.o
Field N o . 2 PR I R .0 ER P I ER
Field N o . 3 0 H E R . PAR OTHE . P
Field N o . ROLE -ROLE
Field N o . 5 L LRE F-1 CUST. ECTO
No Of Au th 1

Figure 14 ACTIVITY.PRESENTATION

Guide (R18) (English) 2019 Q2 15

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• Attach it to the LENDING-NEW-ARRANGEMENT activity, add the product condition to the product. Proof /
Publish.
Product Conditions · ACTIVITY PRESENTATION CUST.SECTOR.AP-�01 �03221 (Model Bank R 1 3 )

G B Desc ription Version f o r Cust secto_!j

J Default Values I r·Negotiation Rules

ii Audi t
I
Activity / Property Activity Version Sim Version

..
LENDING·NEW·ARRANGEMENT �YCUST [AA.AR R.CUSTOMER.AA
Property
Property Cl ass

I More Actions ...

Product Designer PR�D..:.��AP.TASK-20130322 (Model Bank R13)

Produc t Designer Property Conditions 1 Variation �ulation Source 11 Audi t

Property Conditions A rrangement Link Effective Variation
ACCOUNli PERSONALLO� f'IE_n Tra ckL'}�
ACCOUNTI NG LEN cfu&_] racking:
[
ACTIVITY.MAPPI NG [ENDING tack i ng

MYCUST NEGOTIABL.6 Non Tra cking

----- --
PR I NCI PALI N - --
F IXEO.RATE.5%
-· �N-�a.cxing;
PR.PRIN�R�§ iT�cki ng
'SCH E·our:io1 ONSTANT.BIWE EKLY Non - ---,
- Track ing
COMM ITM ENT, MY.TERM.A!::1OU_!!!i Non TrackT.!'.�

Figure 15 ACTIVITY.PRESENTATION

• Create an arrangement to see if your version is triggered correctly.

More Actions ...

' - -- ---
New Arrangement AAACT1 3081 B73Z7JK1 (Model Bank R1 3)

J N e w Arrange m e n t u_
..._1_A_ i t......_______________________________
d_ _
Arrangement �l ��1f.3.!'1_1Jj Customer At-1O EA
Produc t Varia tion Currency @so US Dollar
Pricing Pricing Plan
Ac tivi ty New Activity For Arrangement Effec tive Da te f22 MAR 20131

El
Rea.son

MY CUSTOMER PROPERTY Ac count l Commi tment I Principal In te rest I Schedule

MY CUSTOMER PROPERTY------------------------------------1
Owner. 1 ! 100500

Primary Owner 100500 Oft[;

O th e r Party. 1 I Appropria te version triggered
Role . 1
Cus t Sec tor
Figure 16 ACTIVITY.PRESENTATION

Guide (R18) (English) 2019 Q2 16

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• When activity for change principal interest is triggered, the version with CUST.SECTOR is not triggered.

Arrangement Activity • AAACT1 308 1 228T55BG , (Model Bank R 1 3)

J Arrangeme n t Ac tivily J-I_ u d_

A_ l't�I___________________
Arrangement I AA1308JP�1J 65-139 Personal Loan
Customer f 100500 ANDREA
Produc t -----
Prod for Act Presentation Task• Currency USD
Ac tivity Change Pri ncipa l I nterest Effec tive Date 1 22 MAR 2013
GB Narrative

Principal In terest I Schedule I Account I MY CUSTOMER PROPERTY I Commitment

MY CUSTOMER PROPERTY -----------------------------�

Ac tivity, LEND I N G- N EW-ARRANGEMENT
Ac tion . 1 UP DATE,

Owner.1 OREA
Primary Owner OR
Changed Fields. 1 0WNE
Nego tiated Flds. 1 OWNER
Id Comp 1 M._l�P 3M!J

Id Comp 2 MYCUST
Figure 1 7 ACTIVITY.PRESENTATION

Points to Remember
ACTIVITY.PRESENTATION product conditions should always be set to tracking as ACTIVITY.PRESENTATION property
class is 'TRACKING.ONLY'. The product conditions are merging. Example - If a child product has a version set for
activity LENDING-DISBURSE-COMMITMENT but not for activity LENDING-DECREASE-COMMITMENT and a version
for LENDING-DECREASE-COMMITMENT has been set in the parent product. When LENDING-DECREASE-COMMIT­
MENT activity is performed for the child product, the version defined in the parent product will be used. A version
defined at the child level will override whatever is defined at parent level. If not specified at the child level version
defined at the parent level will be used and hence the product conditions are said to be merging. A product condi­
tion defined for the child product will always override the parent product. ACTIVITY.PRESENTATION property class
is merged in a mutually exclusive manner when product is proofed. Remember, during publish, the records from
... PRF ... applications are simply written to the ...CAT... application. Versions cannot be defined in ACTIVITY.PRESEN­
TATION. The versions should define only screen layout. When creating versions for files prefixed with AA.ARR.XXX
all fields that accept version routines will become no input fields. Routines can be attached for arrangement activ­
ities using the ACTIVITY.AP! property class.
• ACTIVITY.PRESENTATION product conditions should always be tracking.
• The product conditions are merging.
• Child product condition override parent product condition.
• Product Conditions are merged when product is proofed.
• Version routines cannot be defined.

Guide (R18) (English) 2019 Q2 17

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Practice
Practice 1
• Create a version for AA.ARR.TERM.AMOUNT and add the AMOUNT.CHANGE local reference field created in
the previous practice.
• Attach version to the LENDING- DECREASE-COMMITMENT activity using appropriate product condition.
• Proof and publish the product. See if version is triggered according to activity being performed.

Guide (R18) (English) 2019 Q2 18

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Enhancing Functions With Named

Activities
Product Tracking
Product Tracking
We have seen how Activities are associated with Properties. We have also seen Property Classes define the char­
acteristics of the Property. AA.ACTIVITY.CLASS record defines the list of Actions to be applied on the given list of
property classes for a given process in the activity. Lets take the property class TERM.AMOUNT. Actions which can
be performed on this property class can be found in the actions tab of the property class record. When the user
performs an activity we have to perform a set of actions on a particular property. This information is available in
ACTIVITY.CLASS. So when the user performs a disbursement on an arrangement, the activity class LENDING-DIS­
BURSE-TERM.AMOUNT (why TERM.AMOUNT because disbursement happens for the amount field, which is part of
this property class) will be accessed, through corresponding activity LENDING-DISBURSE-COMMITMENT (where
COMMITMENT is the instance of TERM.AMOUNT property class used in the product). All activity classes perform
some action on a property class. That is why the ID of an activity class is Product Line-Process-Property Class name.

Figure 18 Product Tracking

Guide (R18) (English) 2019 Q2 19

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Activities
Generating Activities
Two ways to create activities and one of them is Automatic Generation of activities while the other is using Names
Activities.
• Automatic Activity generation
• Named Activities

Automatic Generation
Automatic Generation
Automatic Generation of activities: Modify Product Group and set the field Rebuild Activities to Yes. This process
creates all the standard Activities for each Property meaning:
• It picks up all the properties for the product group, and,
• For each of the properties, gets the appropriate property class name
• For each of the property classes, gets the appropriate activity class name
• Based on the activity class, builds the activities.
• For activities which are generated automatically, the field SYSTEM.ACTIVITY in the AA.ACTIVITY file will be
set to YES.
For example, in the above screen shot of product group PERSONAL.LOANS, note that a property named ACCOUNT
has been used. It belongs to a property class ACCOUNT. Hence, the associated activity class records for ACCOUNT
will be picked up and the activities will be generated. The user can and should change the descriptions of each
Activity as this is what appears on enquiries such as the Activity Log (This does not create user-friendly descriptions
for the activities. It is recommended to modify the activity descriptions once all the Properties have been gener­
ated.
• Amend Product Group.
• Set Rebuild Activities to Yes.
• For each activity generated in AA.ACTIVITY file, the field SYSTEM.ACTIVITY will be set to YES.
mm- I More Actions ... V I �
Product Group 1pfRSQUALLOAUS. (Model Bank)

GB Descrfptlon • Pll!rscnal Loan�

PcDOnal LOllnS

Full Description ,.

®111-1 Otio O v,-,

f Prope1tl., 1rfud1t_J_
Prope-rtfes Mand.atory
ACCOUNT ACCO\INl ,.,3
ACCOUNTING ACCOUNTING
c'CTlVITI-API
1 ACTIV1TY.CHAR.G£S , AcnVITY.CHAR.GES

Figure 19 Automatic Generation

Guide (R18) (English) 2019 Q2 20

Core Banking Techn ·ical Custom1sat1on
. . $ TEMENOS
Lea rn i n g Com m u n ity

Named Activities
Named Activities
An activity generated automatically by the system is of the form <PRODUCT LINE>-<PROCESS>-<PROPERTY>. This
activity will be common for all the products using a specific property for a given product line. For example, LENDING­
DECREASE-COMMITMENT activity will be common for any product that is using the COMMITMENT property. If the
bank attaches additional functionality to existing activities, it will affect all the products on which this activity is
performed. For this reason the concept of named activities has been introduced where activities can be created
based on an existing activity and additional functionality can be added using ACTIVITY.AP! property class.
• System generated activities follow the form:
• <PRODUCT LINE>-<PROCESS>-<PROPERTY>
• To add additional functionality to an activity, routines can be attached to an activity with the help of ACTIV­
ITY.AP! property class.
• Named activities are used to create activities based upon existing activities and also attach additional func-
tionality.
Manually create a record in AA.ACTIVITY and provide meaningful description in the DESCRIPTION and FULL.DES(
fields. LINKED.ACTIVITY: Use the LINKED.ACTIVITY field to specify the activity to which you wish to link the new
activity. In our case it is LENDING- DECREASE-COMMITMENT. This specifies that the new activity being created will
basically perform the actions defined in the LENDING-DECREASE-COMMITMENT activity and in addition the rou­
tines added using ACTIVITY.AP! property class will also be executed. Note: As mentioned earlier the activity we
attach in the Linked Activity field, should have the SYSTEM.ACTIVITY field set to YES.

I More Actions . . .
AA . ACTIVITY LEN D I NG - DECREASE-COMMITMENT (Model Bank)

GB Desc ri ption Decrease Commitment

Full Desc SYSTEM CREATED
System Activit� Yes I
Product Line LEN D I N G Lending
Process I d DECREASE
Property COM M ITMENT
Curr No l

The activity we atta c h in the Li n ked Activity field should have the
SYSTEM.ACTIVITY fie l d set to YES .
Figure 20 Named Activities

Guide (R18) (English) 2019 Q2 21

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Can you see the new created named activity listed in the list of activities for LENDING-DECREASE-TERM.AMOUT
property class?
Classes Activities

Product Line Activity Class 0 Activity O 0

LENDING-CREDIT-ACCOUNT � & L.J DECREASE.COlr\/,UMENT
LENDING-CREDIT ·ARRANGEMENT � � I..J �om�G-DECREIIE-COM!lllMOIT
LENDING-CREDIT-INTEREST � �
LENDING-DEBIT-ACCOUNT � rg LJ
LENDING-DEBIT ·ARRANGEMENT � �
LENDING-DEBIT-INTEREST � � u
LENDING·DECREASE·TERM.A/KJUNT � rJ L
Figure 21 Named Activities

Highlight 1: Try and open an arrangement, in the list of new activities under "Term Amount" can you see the named
activity that you created just now. Highlight 2: Did you also notice that the linked activity LENDING-DECREASE­
COMMITMENT is also existing as part of the new activities available for "Term Amount". This holds that for an
arrangement the activity LENDING-DECREASE-COMMITMENT can be performed and if you wish to perform some
extra actions then the named activity DECREASE.COMMITMENT can be invoked.

Arran ement Overview

I Arr<1ngement: AA08009R87V6
Cut:torne r : PAIIAMA CITY
�
Pr oduct: Personal Loan
S1art Date: 09 JAii 2008
Account: 38369
Title: Per sonal Loan
C ut r ency: USO

Pending Activities
-----,
Date Activity > >
N,;> Actlviies P�ding

New Activity
Arrangemenl
0Account Static
�Balance maintenance
Charge Definition
@Customer
�lnlerest Celculstlon
§ Accounl Limit
�Officers
1
--,I
�Peyment Schedule
� Term Alnounl ,-
l o-
ec-
,e
-.1-
se
_C_
o_
m_n_
1it_
m_e,-
,t-
A1_
n_
ou_
n_
t

I
CHAIIGE.TERM ACTIV ITY FOR COMMITMEIIT
DECRfASE ACTIVITY FOR COMMITMEIIT 12
IIICREASE ACTI VITY FOR COMM.I TMEIIT
[Jrerm Ainounl

Figure 22 Named Activities

Guide (R18) (English) 2019 Q2 22

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

Activity Logs
Activity Logs
Application for triggering an activity on an arrangement is AA.ARRANGEMENT.ACTIVITY. Details of these activities
are also stored in AA.ARRANGEMENT.ACTIVITY. A record is created in this application for every activity performed
on the arrangement. To view a list of activities that have been performed on an arrangement in the sequence of
occurrence. AA.ACTIVITY.HISTORY is a log of all the activities that have occurred on an arrangement.
• Application for triggering an activity an arrangement AA.ARRANGEMENT.ACTIVITY.
• An application called AA.ACTIVITY.HISTORY maintains a log of all activities that have been performed on an
arrangement.
ID of AA.ACTIVITY.HISTORY is the arrangement id. EFFECTIVE.DATE : This field is used to specify the effective date
on which an activity has been performed. The value for this field is picked from the EFFECTIVE.DATE field of AA.AR­
RANGEMENT.ACTIVITY application. ACTIVITY.REF : This field is used to specify the activity id from AA.ARRANGE­
MENT.ACTIVITY application of the activity that was triggered. ACTIVITY: field is used to specify the name of the
activity that was performed on a specified EFFECTIVE.DATE. It's value is picked from AA.ARRANGEMENT.ACTIVITY's
ACTIVITY field. It is sub-valued to record various activities performed on the same date.
� AA Activity Historv - Windows Internet Explorer -=··

Effec tive Date . 1 20 MAR 20 1 3

Ac tivi ty Ref. 1 . 1 CT130817QW6VF5Tj
Ac tivity. 1 . 1 i[EN DI N G-ISSUE.CHASER-0\'E RDUE-: 'DEL · PAYM EN Issue Overd ue Chase r (Delinque n t)
System Date. 1 . 1 2 MAR 2013i 12 MAR 201 3
Ac t Status. 1 . 1 uth
lnitiation. 1 . 1 \schedu le d �
Ac tivi ty Ref. 1 . 2 CT130TTOK6Y79T
Ac tivity. 1 .2 JLEN DI N G,, ssu E. CHASER-OVER DUE ♦ DEL· PAYM EN1j Issue Overd u e Chaser (Detin quen t)
System Date . 1 .2 22 MAR 20 1 3
Ac t Status. 1 .2
lnitiatio n . 1 .2
Effec tive Date.2 06 MAR 20 1 3
Ac tivi ty Ref.2.1
Ac tivi ty.2. 1 i[END1 NG-I SSUE. CHASER-OVER DUE• DEL• PAYM EN'f Issue Overd ue Chaser (Delinque n t)
System Date.2.1 2 MAR 2013i 12 MAR 201 3
Ac t Status.2. 1
lnitiati o n . 2 . 1
Ac tivi ty Ref.2.2
Ac tivity.2.2 ILEN Dl NG-1SSUE.CHASER-OVER DU�· oEL· PAYMENT, Issue Overd u e Chaser {Detin que n t)
System Date.2.2 !22 MAR 20131 12 MAR 20 1 3
�-----�--�-----------------------------
Ac t Status.2.2 uth-rev 1=:J

Figure 23 Activity Logs

Guide (R18) (English) 2019 Q2 23

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• SYSTEM.DATE: field holds the Core Banking's date when an activity was triggered.
• ACT.STATUS field indicates the current status of the activity. Some of the statuses are
■ UNAUTH - Activity is currently unauthorised
■ UNAUTH-REV - The activity has been reversed and is yet to be authorised.
■ UNAUTH-CHG - The activity has undergone a change in its unauthorised state
■ AUTH - The activity has been authorised.
■ AUTH-REV - The activity has been reversed and authorised.
■ DELETE-REV - The activity was reversed and later reversal was deleted.
■ DELETE - The activity has currently been deleted.
• INITIATION : This field indicates how the activity was triggered. Few of the important initiation types are
■ SCHEDULED - The activity was executed as part of a scheduled COB job.
■ TRANSACTION - The activity was triggered by an external transaction
■ USER - The activity was triggered manually by the user.
■ SECONDARY - The activity was triggered as a secondary activity from another (primary) activity.

e AA Activity H"tstory - Windows Internet Explorer -

I More Acti _on_s_._. . __f]

lAA.ACTIVITY. H I -STORY [Mt3 05 6l2.2Q4 , (Mo del Bank R1 3) --------------------�

Effec tive Date . 1 20 MAR 20 1 3

Ac tivi ty Ref. 1 . 1 CT130Sl 7QW6VFS j
Ac tivi ty. 1 . 1 [LENDIN G-ISSUE. CHASER-OVER DU E-;-D EL• PAYM EN"J'. lssue Overdue Chase r (Delin q u e n t)
Syste m Date . 1 . 1 22 MAR 2013
Ac t" Status. 1 . 1
lnitiati o n . 1 . 1
Ac tivity Ref. 1 .2
Ac tivi ty. 1 . 2 JLEN DI NG"ISSUE.CHASER-OVERDUE•D�l:::_PAYME lssue Overdue Chaser { Delin quen t)
System Date . 1 . 2 22 MAR 201 3
Ac t Status. 1 .2
lnitiati o n . 1 .2
Effec tive Date .2 06 MAR. 20 1 3
Ac tivi ty Ref. 2 . 1
Ac tivi ty.2. 1 (IT�NG-ISSUE.CHASER-OVERDUE·DEL·PAYMENT lssu e Overdue Chase r (Delinqu e n t)
Syste m Date . 2 . 1 �-�� 22 MAR 2013
Ac t Status.2 . 1
lnitiation . 2 . 1
Ac tivi ty Ref.2 . 2 CT130655 RZ1WRH
Ac tivity.2.2 JLENDI NG-ISSU!�HASER-OVERDUE•D�l:::_PAYMEN ' lssue Overdue Chaser ( Delin q u e n t)
System Date.2.2 Ji2 MAR 20131 22 MAR 201 3
l:!c t Status . 2.2 �r�:_ v-�------------------------------�

Figure 24 Activity Logs

Guide (R18) (English) 2019 Q2 24

 · Custom1sat1on
Core Banking Technical . . $ TEMENOS
Learning Community

• ACTIVITY.ID : This field is used to specify the activity that has been performed on this arrangement. It is
updated from ACTIVITY in AA.ARRANGEMENT.ACTIVITY. The field ACTIVITY.ID to TOT.ACT.CNT are part of
this activity subset. The subset indicates details with respect to the activity.
• ACT.DATE : The effective date on which this activity was performed on an arrangement. It is sub-valued if the
same activity has been performed on multiple dates.
• ACT.COUNT : Indicates the number of times this activity was performed on a single date. When an activity is
performed more than once, then the ACTIVITY.ID and ACT.DATE remain the same - but the count alone is
incremented. Deletion or reversal would decrement the count accordingly.
• TOT.ACT.AMT : This field holds the total number of times an activity has been performed on an arrangement.
• ACTIVITY.AMOUNT: Indicates the amount that was transacted by the above activity on that effective date.
Amounts are always in arrangement currency.
e AA Activity H"tstory - Windows Internet Explorer

I I.lore ctions ___ .d

I AA .ACTIVfTY.HISTORY i AA1 3056l22Q4 (Model Bank R1 3 )

I Ac t Status.6.6 Auth
lni ti a ti o n . 6. 6 U�
Ac tivi ty l d . 1 LEN D I NG-NE '11-ARRANGEMEN w Ac tr,i • For Arrangemen t
Ac t Date . 1 . 1 25 FEB 101
Ac t C.ou n t. 1 . 1 11
To t Ac t C n t. 1 . 1
Ac tivi ty l d . 2 LEN D I NG-O IS-BURSE-IDMM ITM ENT Disbur..emen t
Ac t Date.2. 1 r25 FEB 2013 25 FIB 201 �
Ac t Am o u n t.2. 1
Ac t Co u n t.2. 1 [lj
To t Ac t Am t.2. 1 ;75,000.00
Tot Ac t C n t. 2 . 1 j
Ac.tivi ty l d . 3 �N D I NG: ISSU. ! B_ llL- 0 1S-BURSEMENTFEE, lzu Bill (Oruiursernenl Fe e)
Ac t Date . 3 . 1
Ac t C o u n t. 3 . 1
To t Ac t Cn t. 3 . 1
_
25 FEB 2013
___, 25 FEB 201 }

0
Ac tivi ty l d . 4 --- -
LE ND I NG· MAK EOUE- D ISBURSEMENTF EE -
Ac t Date . 4. 1 '25 FEB 2013- 25 FEB 201 1
Ac t C o u n t.4. 1 iii
To t Ac t Cnt.4. 1 ·1
I Ac tivi ty l d . 5 LEN D I NG-S ETTlf-SETTlfMENT Se tl.e �ia lnslTuc t:ions

R-13 - R_13; C) 1 I INPUTTER I Model Bank R 13 I 22-MAR-20ll l 1390-48-0-1342-3

Figure 25 Activity Logs

•••♦

Guide (R18) (English) 2019 Q2 25