Scribd
Upload
38 views

Version Control

Uploaded by

Hmani Emna
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
38 views

Version Control

Uploaded by

Hmani Emna
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

TEMENOS T24

Version Control

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.


Version Control

Table of Contents
Overview.................................................................................................................................................. 3
Setup ....................................................................................................................................................... 4

TEMENOS T24 User Guide


Page 2 of 5
Version Control

Overview
VERSION.CONTROL is a T24 application that provides more flexibility when creating screen
versions. This application allows users to group VERSION records and to control field attributes
based on defined conditions. The user is able to use these features in conjunction with the VERSION
application.

VERSION.CONTROL is an addition to the VERSION application. It does not replace the


VERSION application.

TEMENOS T24 User Guide


Page 3 of 5
Version Control

Setup

One VERSION.CONTROL record can be linked to multiple VERSION records via the
VERSION.TYPE field on VERSION. The VERSION.TYPE forms part of the id of the
VERSION.CONTROL record. The other part of the VERSION.CONTROL record id is the
application name (e.g. ACCOUNT, CUSTOMER, etc).

In the example below, the id of the VERSION.CONTROL is CUSTOMER,CVF, where, ‘CVF’ is the
version type. This allows the user to group linked VERSION records. In this case all Customer
versions with the ‘CVF’ version type are grouped. Hence routines can be attached at one place,
namely on the VERSION.CONTROL record. If the routines exist in VERSION.CONTROL and
VERSION, then the routines in VERSION will be used.
The EXC.INC.RTN field on the VERSION record needs to be set ‘Yes’ for the routines on the related
VERSION.CONTROL to be executed. This field also enables the other features of
VERSION.CONTROL.

VERSION.TYPE field populated on VERSION record

VERSION.CONTROL

TEMENOS T24 User Guide


Page 4 of 5
Version Control

If the id of VERSION.CONTROL does not have the version type as part of its id and the field
NON.VERSION.RUN is set to ‘Y’, then the routines will be applied to the application (i.e. when the
application is used without any Version).
In the case where a VERSION.CONTROL record exists for an application and for a version (of the
same application), the routines in both of the VERSION.CONTROL records will be applied when the
VERSION is invoked.

For example: -
Two VERSION.CONTROL records exists namely, ACCOUNT and ACCOUNT,SAV, and version
ACCOUNT,SAVING is linked to ACCOUNT,SAV. If ACCOUNT,SAVING is ‘run’ then the Version Control
for ACCOUNT and ACCOUNT,SAV will be used.

It is also possible to set up a SYSTEM record in VERSION.CONTROL which is applied against all
Versions and Applications. The following fields can be set: -
INPUT.RTN, AUTH.RTN, ID.RTN, CHECK.REC.RTN, AFTER.UNAU.RTN, BEFORE.AUTH.RTN,
SYS.MSG.SUPPRESS, AUTO.COMP.CHANGE, COMPANY.ACCESS, BUSINESS.DAY,
MSG.SUPPRESS

VERSION.CONTROL is also be used to control the fields to be displayed and their attributes. For
example, a field can be made as ‘No Input’ or ‘Mandatory’ based upon the Branch/Department of the
user. Similarly a field can be displayed or hidden from the user based upon similar conditions.
The help text for the VERSION.CONTROL application explains the various fields and their usage.
Please refer to the help text for further information.

TEMENOS T24 User Guide


Page 5 of 5

You might also like