TEMENOS T24

Rules Engine

User Guide

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

Rules Engine

Table of Contents
Overview.................................................................................................................................................. 4
Setup ....................................................................................................................................................... 4
Rule Designer Main Screen ................................................................................................................. 6
Rules Designer Script Screen .......................................................................................................... 7
Header Pane .................................................................................................................................... 8
Application Menu: ................................................................................................................................ 8
Icons ................................................................................................................................................. 8
Variables Pane ..................................................................................................................................... 9
Contexts: .............................................................................................................................................. 9
Creating a Context ........................................................................................................................... 9
Simple Context ............................................................................................................................... 10
Complex Context ............................................................................................................................ 11
Direct Complex Context ................................................................................................................. 11
Derived Complex Context .............................................................................................................. 12
Deriving Similar to j-descriptor .................................................................................................... 12
Using Subroutine ........................................................................................................................ 13
Sample Routines Examples ....................................................................................................... 14
Adding Context ............................................................................................................................... 14
Enter Context Name: ...................................................................................................................... 15
Remove Context............................................................................................................................. 15
Insert Context Variable to Text ....................................................................................................... 15
System Variables: .............................................................................................................................. 16
System Variables Explained .......................................................................................................... 16
Insert System Variable to Text ....................................................................................................... 17
Rule Variables .................................................................................................................................... 18
Add Rule Variable .......................................................................................................................... 18
Remove Rule Variable ................................................................................................................... 19
Insert Rule Variable to Text ............................................................................................................ 20
Embedded Rule ................................................................................................................................. 20
Add Embedded Rule ...................................................................................................................... 21
Remove Embedded Rule ............................................................................................................... 22
Insert Embedded Rule to Text ....................................................................................................... 23
Functions ........................................................................................................................................... 24
Operators ....................................................................................................................................... 25
Insert Function to Text.................................................................................................................... 26

TEMENOS T24 User Guide

Page 2 of 43
Rules Engine

Comment to Text ........................................................................................................................... 27

Static Processing ................................................................................................................................... 28
Rule Structure .................................................................................................................................... 28
Validate Rule .................................................................................................................................. 29
Save Rule ....................................................................................................................................... 29
Saving the Rule to T24 ................................................................................................................... 30
Saved Rule ..................................................................................................................................... 31
Test Harness ...................................................................................................................................... 32
Rules Engine Output .......................................................................................................................... 33
EB.RULES ...................................................................................................................................... 33
EB.RULES.VERSION .................................................................................................................... 34
EB.RULES.HIERARCHY ............................................................................................................... 35
Locked rule in use by other user ........................................................................................................ 36
History of Rules .................................................................................................................................. 37
SMS ................................................................................................................................................... 39
Rules Designer Help about Version................................................................................................... 43

TEMENOS T24 User Guide

Page 3 of 43
Rules Engine

Overview
Rules Engine allows definition of complex business rules to support decision processing and scoring.
This needs to be generic so as to allow it to be deployed anywhere within T24 / ARC. Where a rules
based decision is required or where a score needs to be calculated.
The business rules language is procedural/imperative in style. It is helpful to think of it in terms of a
machine state consisting of a control part representing the instructions to be executed and a data part
consisting of the structure being manipulated by the instructions. Rules Engine has been designed to
be used by non-technical ‘power users’. Where previously a routine would need to be coded to make
a complex calculation or decision, The Rule Designer can be used by a business user to write a rule
expressing the logic required to make the correct decision or find the right score
Examples of where the Rules Engine can be used at the moment is in the CR Sales Opportunity
module, where it can be used to determine whether an opportunity is appropriate for a customer or not
and if so, what value/probability can be placed on that opportunity for a customer.
Another instance where a rule can be used is in process workflow, where a rule may determine the
correct status of a PW activity or process.
There are many places within T24 where a decision or score is made – along with Sales Opportunity
and process workflow, In future, the Rules Designer may be used in these places. This guide
describes the process of the business rules language and covers some simple usage through rule
composition.

Setup
Rule Designer allows users to construct simple rules through an intuitive graphical interface. To open
rule designer follow the process below:

Open T24 Toolbox and Sign on to the T24 Toolbox.

Option 1: Clicks T24Rules TAB, Double click on the Icon Rule Designer
Option 2: In the Menu Bar Click on Go To then click T24 Rules open Rules Designer
Rule Designer where the user can generate rules.

TEMENOS T24 User Guide

Page 4 of 43
Rules Engine

T24 Tool Box

TEMENOS T24 User Guide

Page 5 of 43
Rules Engine

Rule Designer Main Screen

The Rule Designer main screen divides in three areas:
1. Recent Rules
2. Actions
3. Help
Recent Rules opens all the rules which have previously been opened or constructed.
Actions are short cuts for creating new rules, opening rules saved to T24 database or opening rules
saved to local disk database.
Help gives access to contents of help file.

Rule Designer Main Screen

TEMENOS T24 User Guide

Page 6 of 43
Rules Engine

Rules Designer Script Screen

The Rule Designer GUI is where users can construct rules which are implemented in T24 / ARC.
The Rule Designer GUI consists of five main areas:
1. Application menu
2. Variable pane
3. Script pane
4. Error pane
5. Description Pane

Script Pane

Application Menu

Variables Pane

Error Pane

Rule Designer GUI Interface

TEMENOS T24 User Guide

Page 7 of 43
Rules Engine

Header Pane
The Header pane contains the name of the rule, a short description.

Rule Designer Application Menu

Application Menu:
Menu Pane includes File, Edit, Rule, Tools, and Help.

Icons
New Rule opens a blank page to create a new rule
Open Rule allows the user to open an existing saved rule on the local disk drive.
Open Rule from T24 it allows opening saved rule from T24
Save rule to the local disk drive
Save rule to T24
Print Rule
Comment on selected line
Uncomment the Selected line
Increase Indenting
Decrease Indenting
Edit Rule Description allows editing the Description of a saved rule.
Validate rule (Short key F8), allows validating rule.
Run Test Harness GUI (Short key F5) to check the functionality of Valid Rule.

TEMENOS T24 User Guide

Page 8 of 43
Rules Engine

Variables Pane
The Variable Pane contains all ingredients for writing the rule.

Rule Designer Variable Pane

The CONTEXT and system variables are classified in Alpha character, Numeric, Date

Contexts:
All rules have to take place within a specific CONTEXT the context details the data that is being
tested by the rule to give a true/false answer, a score and/or a message.
For example, if the rule was based on whether customer has been at the bank for longer than a
specified period, or was resident in a particular country, the context would be based on CUSTOMER.
If the rule was based on whether an account had a balance higher than a particular amount, or was a
particular type of account, then the context would be based on ACCOUNT.

Creating a Context
In order to evaluate the rule we need pass context data. Within each of the calling process we will
only need to define the rule we wish to access and the source of ID to the T24 / ARC business object
(main application) with which the interface can build the context data.
The application EB.CONTEXT allows the definitions of contexts for use within rules. A single context
can link together multiple tables, as long as they share the same ids – for example, CUSTOMER,
CUSTOMER.SECURITY and CUSTOMER.CHARGE. In addition, derived contexts can be added to
an EB.CONTEXT. If we need to find additional data about a table which is not directly held on the
table – for example, the average balance of an account for that month, or the geographic block of a
customer’s residence

TEMENOS T24 User Guide

Page 9 of 43
Rules Engine

Simple Context

The simple EB.CONTEXT record has in its ID only. Field PRIMARY TABLE linked to Context
Variable in RULE DESIGNER can access any of the field in the table CUSTOMER for evaluation of
the rules.

Simple EB.CONTEXT, Creating CUSTOMER Context

TEMENOS T24 User Guide

Page 10 of 43
Rules Engine

Complex Context
Whenever the detail in a single table is insufficient to evaluate the rules, we need to have a complex
EB.CONTEXT. The id of any complex contexts should contain a delimiter ‘*’ – e.g.
CUSTOMER*COMPLEX. We have two types as below.
1) Direct Complex Context
2) Derived Complex Context

Direct Complex Context

To access data directly from more than one table, the tables that share a common ID can given in the
field PRIMARY TABLE and field LINKED TABLE linked to Context Variable in RULE DESIGNER
can access the field in the table for evaluation of the rules.

Direct Complex Context

TEMENOS T24 User Guide

Page 11 of 43
Rules Engine

Derived Complex Context

When required information cannot directly get from the given tables, it needs to be derived. This can
be achieved in two ways as below.
1) Deriving Similar to j-descriptor
2) Using Subroutine

Deriving Similar to j-descriptor

Based on Primary key of a table, the desired value can be got in turn by linking to other tables whose
primary keys are obtained from the previous record.

Derived EB.CONTEXT

TEMENOS T24 User Guide

Page 12 of 43
Rules Engine

DATA LABEL.1: New derived field which can be directly used in the RULES DESIGNER for
generating rules as any other field of the table.
SELECTION.PR.1.1: The value of the field is derived as similar to j-descriptor

The above image, Field DATA LABEL.1 (NEW.CUST.DERIVED) will hold the value of field
LABEL.DESCRIPTION.1 (DELIVERY.POINT) in the table DEPT.ACCT.OFFICER. System will use
the value in the field ACCOUNT.OFFICER from the table CUSTOMER and read the corresponding
record in DEPT.ACCT.OFFICER to fetch the value of DELIVERY.POINT

Using Subroutine

Complicated values can be very well achieved by writing a subroutine which returns the desired value.

Derived EB.CONTEXT with Subroutine

TEMENOS T24 User Guide

Page 13 of 43
Rules Engine

DATA ROUTINE.1: Where the Routine attached

DATA.ARG.TAB.1.1: Table name where the argument is a field.
DATA ARGUMENT.1.1: Field name of the table whose value is passed as an argument
MULTI.VALUE.ACT.1: Returned argument is multi – valued action to perform on it.

About Routines

For every routine only one Data Argument can be passed or written

Adding Context
1. Expand the “Contexts” list from the variable pane
2. Double click on the “…” element of the list

Through either of the two options, a window appears (See picture below)

Adding Context

The user may either enter the name of the context or perform a simple search from the defined
Contexts.

TEMENOS T24 User Guide

Page 14 of 43
Rules Engine

Enter Context Name:

1. The user enters the context name and clicks OK
2. The user double -clicks on an item, or simply selects an item and clicks OK.

Remove Context
There are two ways to perform this step:
Option 1:
1. Expand the “Contexts” list from the Variables pane
2. Select the context to be deleted
3. Click the “Delete” button

Option 2:
1. Expand the “Contexts” list from the Variables pane
2. Right click on the context to be deleted
3. A pop-up menu is shown.
4. Select “Remove Item”
Note: a context can only be removed from a rule if it is not being used in the rule anywhere.

Insert Context Variable to Text

Assume that the variable to be added is “CUSTOMER>SALARY” and that it belongs to the
“CUSTOMER” context. Then, there are five ways to add “CUSTOMER>SALARY” to the script:

Option 1:
1. Simply type “CUSTOMER>SALARY” to the script

Option 2:
1. Expand the “Contexts” list from the Variables pane
2. Expand the “CUSTOMER” context
3. Double click on the “CUSTOMER>SALARY” element of the list.

Option 3:

TEMENOS T24 User Guide

Page 15 of 43
Rules Engine

1. Through predictive text. As the user start typing “CUSTOMER>SALARY”, a list will appear
with all the currently defined variables that start with the specific characters.
“CUSTOMER>SALARY” will be one of these variables. The user can therefore select the
variable from the list before completing typing the text.

Option 4:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”
3. Select “Context variable”
4. A list appears with all the context variables. Select “CUSTOMER>SALARY”.

Option 5:
1. Press Ctrl+Shift+C
A list appears with all the context variables. Select “CUSTOMER>SALARY”.

System Variables:
The System elements hold information representing the system state during the Rule Evaluation

Rule Designer System Variables

System Variables Explained

Variable name Content

TODAY Today's date

TEMENOS T24 User Guide

Page 16 of 43
Rules Engine

OPERATING.COMPANY Current Company where the user has Logged in

CURRENT.OPERATOR Current logged user
LOCAL.COUNTRY.OF.BANK Bank’s local country
SECOND.WORKING.DAY The date of the next working day
RULE.STATUS Used within the rule to indicate to the calling process if the test
passed or failed
RULE.MESSAGE Used within the rule to return a narrative indicating to the calling
process why the rule failed.
RULE.SCORE Used within the rule to return a score to the calling process in
those case where the rule is calculating a score

RULE.ERROR Used within the rule to return a string id, for lookup in the
EB.ERROR table, used for internationalisation of messages

System Variables

Insert System Variable to Text

Assume that the variable to be added is “RULE.SCORE”. Then, there are five ways to add
“RULE.SCORE” to the script:

Option 1:
1. Simply type “RULE.SCORE” to the script

Option 2:
1. Expand the “System Variables” list from the Variables pane
2. Double click on the “RULE.SCORE” element of the list.

Option 3:
1. Through predictive text. As the user starts typing “RULE.SCORE”, a list will appear with all the
currently defined variables that start with the specific characters. “RULE.SCORE” will be one of
these variables. The user can therefore select the variable from the list before completing typing
the text.

Option 4:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”

TEMENOS T24 User Guide

Page 17 of 43
Rules Engine

3. Select “System variable”

4. A list appears with all the context variables. Select “RULE.SCORE”.

Option 5:
1. Press Ctrl+Shift+S
2. A list appears with all the system variables. Select “RULE.SCORE”.

Rule Variables
Rule variables are variable names that are used solely for that specific rule.

Add Rule Variable

There are two ways to perform this step:

Option 1:
1. Open “Rule” from the main menu
2. Open “Add Rule Properties”
3. Select “Add Rule variable”

Option 2:
1. Expand the “Rule Variables” list from the Variables pane
2. Double click on the “…” element of the list

TEMENOS T24 User Guide

Page 18 of 43
Rules Engine

Through either of the two options, the following window appears:

Adding Rule Variable

The user must enter the name and enter the description fields.

Remove Rule Variable

There are two ways to perform this step:

Option 1:
1. Expand the “Rule Variables” list from the Variables pane
2. Select the variable to be deleted
3. Click the “Delete” button

Option 2:
1. Expand the “Rule Variables” list from the Variables pane
2. Right click on the variable to be deleted
3. A pop-up menu is shown.
4. Select “Remove Item”

TEMENOS T24 User Guide

Page 19 of 43
Rules Engine

Insert Rule Variable to Text

Assume that the variable to be added is “VARIABLE.A”. Then, there are five ways to add
“VARIABLE.A” to the script:

Option 1:
1. Simply type “VARIABLE.A” to the script

Option 2:
1. Expand the “Rule Variables” list from the Variables pane
2. Double click on the “VARIABLE.A” element of the list.

Option 3:
1. through predictive text. As the user starts typing “VARIABLE.A”, a list will appear with all the
currently defined variables that start with the specific characters. “VARIABLE.A” will be one of
these variables. The user can therefore select the variable from the list before completing typing
the text.

Option 4:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”
3. Select “Rule variable”
4. A list appears with all the context variables. Select “VARIABLE.A”.

Option 5:
1. Press Ctrl+Shift+R
A list appears with all the system variables. Select “VARIABLE.A”.

Embedded Rule
Stores list of Nested Rules and can be used in current rule evaluation. . Any rule that has been
previously written can be used in any other rule – however, if an ‘embedded rule’ uses a new context,
then the master rule must also have that context – for example, my rule
‘CUSTOMER.CREDIT.RATING’ may use both CUSTOMER and ACCOUNT as contexts. If I have
another rule called MORTGAGE.RISK.REVIEW based on the MG.MORTGAGE context, but which
also uses the CUSTOMER.CREDIT.RATNG rule, then the MORTGAGE.RISK.REVIEW rule will need
to have the contexts CUSTOMER and ACCOUNT as well, in order to have all the information
necessary to resolve the rule.

TEMENOS T24 User Guide

Page 20 of 43
Rules Engine

Add Embedded Rule

There are two ways to perform this step:
Option 1:
1. Open “Rule” from the main menu
2. Open “Add Rule Properties”
3. Select “Add Embedded Rule”

Option 2:
1. Expand the “Embedded Rules” list from the Variables pane
2. Double click on the “…” element of the list

Through either of the two options, a window appears (see picture below)

Search for Embedded Rule

The user may either enter the name of the rule or perform a simple search.

Enter Rule Name:

The user enters the rule name and clicks OK

TEMENOS T24 User Guide

Page 21 of 43
Rules Engine

Perform simple search:

1. The user may enter a search word and click on the search button next to the text area.
2. Once the search button is pressed, a list of selected items is presented and the window is
expanded (see image below)
3. The user double -clicks on an item, or simply selects an item and clicks OK.

Adding Embedded Rule

NOTE: If no text is entered, the search button will return all the available rules.

Remove Embedded Rule

There are two ways to perform this step:

Option 1:
1. Expand the “Embedded Rules” list from the Variables pane
2. Select the rule to be deleted
3. Click the “Delete” button

TEMENOS T24 User Guide

Page 22 of 43
Rules Engine

Option 2:
1. Expand the “Embedded Rules” list from the Variables pane
2. Right click on the rule to be deleted
3. A pop-up menu is shown.
4. Select “Remove Item”

Insert Embedded Rule to Text

Assume that the embedded rule to be added is “RULE.A”. Then, there are five ways to add “RULE.A”
to the script:

Option 1:
1. Simply type “RULE.A” to the script

Option 2:
1. Expand the “Embedded Rules” list from the Variables pane
2. Double click on the “RULE.A” element of the list.

Option 3:
As the user starts typing “RULE.A”, a list will appear with all the currently defined variables that
start with the specific characters. “RULE.A” will be one of these variables. The user can therefore
select the rule from the list before completing typing the text.

Option 4:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”
3. Select “Embedded rule”
4. A list appears with all the embedded rules. Select “RULE.A”.

Option 5:
1. Press Ctrl+Shift+E
2. A list appears with all the embedded rules. Select “RULE.A”.

TEMENOS T24 User Guide

Page 23 of 43
Rules Engine

Functions
The Script Statements that can be used to construct the rule.

Rule Designer Functions

TEMENOS T24 User Guide

Page 24 of 43
Rules Engine

Operators
The following operators will be supported. They are listed in precedence order, with the most tightly
binding operators listed first.

Description Operator Example

Logical negation not not(i eq 10 or i lt 7)
Unary sign operator - RULE.SCORE = -10
Multiplying operators * / RULE.SCORE = i * j / k
Binary adding operators + - RULE.SCORE = I + j – k
Comparison operators
Equals eq s eq "fred" or i eq 10
Not equals ne s ne "fred" and i ne 10
Less than (numbers only) lt i lt 10
Less than or equals (numbers only) le i le 10
Greater than (numbers only) gt i gt 10
Greater than or equals (numbers only) ge i ge 10
In range (numbers only) rg i rg 10 20
Not in range (numbers only) nr i nr 10 20
Like (strings only) lk S lk "...A..."
Unlike (strings only) ul S nl "...A..."
Boolean and and i lt 10 and j rg 10 20
Boolean or or i lt 10 or j nr 10 20

Function Operators

TEMENOS T24 User Guide

Page 25 of 43
Rules Engine

Insert Function to Text

Assume that the function to be added is the following statement:

if ( )
then
else

Then, there are five ways to add this function to the script:

Option 1:
1. Simply type the function to the script

Option 2:
1. Expand the “Functions” list from the Variables pane
2. Double click on the “if…then…else” element of the list.

Option 3:
1. through predictive text. As the user starts typing “if…”, a list will appear with all the currently
defined variables that start with the specific characters. “if…then…else” will be one of these
variables. The user can therefore select the functions from the list before completing typing the
text.

Option 4:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”
3. Select “Function”
4. A list appears with all the functions. Select “if…then…else”.

Option 5:
1. Press Ctrl+Shift+F
2. A list appears with all the functions. Select “if…then…else”.

TEMENOS T24 User Guide

Page 26 of 43
Rules Engine

Comment toText
There are three ways to add a comment to the script:
Option 1:
1. Simply type “//” in front of the text to be the comment

Option 2:
1. Open “Tools” from the main menu
2. Open “Insert to Editor”
3. Select “Comment”

Option 3:
Press Ctrl+Shift+C

TEMENOS T24 User Guide

Page 27 of 43
Rules Engine

Static Processing
Rule Structure
The typical structure of a business rule may be seen below.

Simple Rule

TEMENOS T24 User Guide

Page 28 of 43
Rules Engine

Validate Rule
On pressing icon Validate Rule or Key F8 the Rule is validated and Display a Message Box as below

Validated Rule
This confirms that a valid rule has been written – the syntax is correct, and the rule can be evaluated.
If there are problems with the validation, these will be shown in the Error pane, which will indicate the
first issue with the rule to be corrected.

Save Rule
Rule is saved in two modes
1. Save the Rule to T24
2. Save the Rule on selected location

TEMENOS T24 User Guide

Page 29 of 43
Rules Engine

Saving the Rule to T24

On clicking the icon save Rule to T24 a window is displayed as below. In the Description box a
description should be given related to that valid rule.

Saving Rule to T24

Note: That when a rule is saved to T24, it is validated first to ensure that the rule can be used. It is not
possible to save an invalid rule to T24 – all issues must be resolved before it can be saved.

TEMENOS T24 User Guide

Page 30 of 43
Rules Engine

Saved Rule
After giving a description for the validated rule click the save button which give a message box the
Rule has been saved.

Rule Saved

TEMENOS T24 User Guide

Page 31 of 43
Rules Engine

Test Harness
The Test Harness is designed to enable the user to test their rule and ensure that it is giving the
expected results, before putting it to use. The user is able to enter sample data without accessing T24
data, to see the output that would be generated if this data was supplied from T24 through the
contexts.
The results for the Valid Rule will be displayed in the Test Harness. On Pressing icon Run Test
Harness or key F5 Test Harness window is displayed.

Rule Designer Test Harness

TEMENOS T24 User Guide

Page 32 of 43
Rules Engine

Rules Engine Output

The backend server routine which retrieves and saves data to the T24 rules tables. The server routine
also merely passes which validates the rule passing the result back to the server routine which passes
this result back to the GUI
The below tables can only be created/updated through the rules engine. They are however stored
within T24 as standard T24 tables.

EB.RULES

EB.RULES is a system maintained file which holds the versions of each rules created in the Rules
GUI. The key to this file being a unique basic description of the underlying rule each time the rule
changed and saved the version/date is written to this file.

EB.RULES

TEMENOS T24 User Guide

Page 33 of 43
Rules Engine

EB.RULES.VERSION

When a rule is saved in the GUI a record will be written to the file EB.RULES.VERSION, if the rule is
edited on a different day to the original rule then a new rule record will be written with the current date
as the new version number. This is so that versioning can be applied to rules, and specific versions of
rules can be called where appropriate.
The ARC / T24 output which the rules engine produces upon evaluation of a business rule.
EB.RULES.VERSION shows the rule structure in XML format.

EB.RULES.VERSION

TEMENOS T24 User Guide

Page 34 of 43
Rules Engine

EB.RULES.HIERARCHY

EB.RULES.HIERARCHY when a rule is saved a record will also be written containing one field which
will contain a chain of all the rules nested rule keys and the nested rules nested rules.
This is again necessary for rules versioning, where the user can work out how the changing of one
rule may impact the processing of other rules. For example, if a rule is updated to add a new context,
then all rules which use that rule may also need to be updated, to ensure they can still provide the
necessary data to run that rule

EB.RULES.HIERARCHY

TEMENOS T24 User Guide

Page 35 of 43
Rules Engine

Locked rule in use by other user

When rule is locked and in use by another user a standard T24 record lock error message will be
passed back to the GUI displaying to the user and the rule is opened in Read-Only mode to the
current user with disable save Rule to T24 icon button.

Example:
Once the rule is opened by an existing user and the same rule is used by another user an error
message is prompted as the rule is locked by User [AUTHORISER] as below example

Rule Locked By another User [AUTHORISER]

TEMENOS T24 User Guide

Page 36 of 43
Rules Engine

Locked Rule in Read-Only mode displayed to current user

History of Rules
When saving the rules from the GUI, in the backend server routine the EB.RULES.VERSION$HIS
record automatically updated using the standard OFS mechanism and writes the record to the
database. Rules are non-inputtable via T24 but all AUDIT fields should be maintained when changing
a record.
T24 Rules table EB.RULES.VERSION$HIS updates as the rule each time updated and saved in GUI
is shown with an increment in version of history suffixed.
As below example [Cust.Salary*20001130; 13] Shows the changes made to Field Prompt, Old Value

TEMENOS T24 User Guide

Page 37 of 43
Rules Engine

EB.RULES.VERSION$HIS

XML.1 = New value of RULE.SCORE = 25

TEMENOS T24 User Guide

Page 38 of 43
Rules Engine

RESERVED 10 = New string to RULE.MESSAGE = “Customer in Group A”

SMS
Standard T24 security should be handled by the OFS mechanism when writing and retrieving rules
records. The user logged into Toolbox the standard OFS mechanism should check the USER record
for any SMS settings and restrict the user accordingly passing any SMS messages back the GUI.
The Standard T24 Security handled by the OFS mechanism when retrieving T24 rules tables
EB.RULES, EB.RULES.VERSION, EB.RULES.HIERARCHY has prompted with Error message
Security Violation as the applied SMS setting to USER

SMS setting on EB.RULES

TEMENOS T24 User Guide

Page 39 of 43
Rules Engine

SMS setting on EB.RULES.VERSION

SMS setting on EB.RULES.HIERARCHY

TEMENOS T24 User Guide

Page 40 of 43
Rules Engine

Below example shows the SMS setting on TOOLBOX

The applied SMS setting to the USER, as the user saved a new designed rule [JointAC] See Figure:
30 Rule Designer Saved Rule.

Saved Rule JointAC to Rule Designer

TEMENOS T24 User Guide

Page 41 of 43
Rules Engine

After Saving Rule to Rule Designer GUI the same rule user tries to open the rule [JointAC] but can’t
find the rule [JointAC] See Figure:31 Load Rule from T24 as the SMS setting are applied on the
USER

Load Rule from T24

TEMENOS T24 User Guide

Page 42 of 43
Rules Engine

Rules Designer Help about Version

Rule Designer Help About

The System Information of Rules Designer such as:

GUI Release
Rules Engine
T24 Release
These components explain the Version on which the users currently working.

TEMENOS T24 User Guide

Page 43 of 43