Version Routines: Technical Courses

Version Routines
Days 5-7 – Sessions 1-4

Introductory Session
Dates
DD/MM/YYYY Technical Courses
Venue
xxxx
Version Routines
Objectives
 Why Version Routines

 Various Types of Version Routines
 Steps to create Version Routines & Error Shots
3 Thesys Training Centre

Session Plan – Day 5
 Session 1
• Introduction & Validation Routine
 Session 2
• Workshop
 Session 3
• Input Routine & Authorisation Routine
 Session 4
• Workshop

 Session 1
• Check Record Routine
 Session 2
• ID Routine
 Session 3
• Auto Field Routine
 Session 4
• Workshop

 Session 1
• Before Auth Routine & After Unauth Routine
 Session 2
• Version Control
 Session 3
• Updating Local reference fields using routines
 Session 4
• Workshop

Why Version Routines?
 For Additional Validations During

• Generation of ID
• Record Level
• Field Level
• Commit level
• Authorization level
 For Defaulting Values

Common Variables
 ID.NEW
 ID.OLD
 ID.NEW.LAST
 R.NEW
 R.OLD
 R.NEW.LAST
• Available in I_COMMON

ID.NEW
 Common variable defined in I_COMMON

 Dynamic array
 Contains the ID of the currently opened record
 When record is closed/committed/authorised value is flushed

R.NEW
 Common variable defined in I_COMMON

 Dimensioned array
 Contains 500 dynamic arrays
 Holds the currently opened record
 ‘R’ in the variable name stands for ‘Record’

R.NEW
 Definition in I_COMMON : DIM R.NEW(C$SYSDIM)

 C$SYSDIM = 500
 No application in T24 has more than 500 fields

ID.NEW.LAST
 Defined in I_COMMON
 Dynamic array
 For unauthorized record - ID of the unauthorized record is
held

R.NEW.LAST
 Consists of 500 dynamic arrays
 Holds the currently opened record (If the record is
unauthorized)
 Definition in I_COMMON
• DIM R.NEW.LAST(C$SYSDIM)

ID.OLD
 Dynamic array
 For authorized record
• Holds the ID of the authorized record
 Enables to check if the current record is authorized

R.OLD
 Consists of 500 dynamic arrays
 Holds the current authorized record (if any)
 Holds the actual live record (If it exists)
 Definition in I_COMMON
• DIM R.OLD(C$SYSDIM)

COMI
 Global variable
 Defined in I_COMMON file
 Contains the last entered value in any application/version

Types of Version Routines
 Validation Routine
 Input Routine
 Authorization Routine
 Auto Field Routine
 Id Routine
 Check Record Routine
 After unauth Routine
 Before Auth Routine

Validation Routine
 Why Validation routine?

 When Validation Routine is called?
 Where do we Attach the routine?
 Mandatory Prerequisites.
 How to Create Version Routines – Scenario.

Why validation routine?
 To perform Field level validations.

 To perform validation as soon as the data entered.

When Validation Routine is called?
 In the version to which we attach the routine
 When the users comes out of the field for which we have
validated

Where do we Attach the routine?
 Attached to the specific field of the version.

 Field to be validated is specified in Validation.Fld
 Routine used to validate is specified in Validation.Rtn

Mandatory - Prerequisites
 Entry in PGM.FILE
 Entry in EB.API

Scenario
 Create a version for Account with the following fields

• Customer name
• Category
• Currency
 Write a Validation Routine to Validate the Currency as USD.

Write the Validation Routine

Compile and Catalogue

PGM.ENTRY

EB.API

Create the Version

Run the Version
 Attribute is not set to Currency

 Validation Routine is called only on validation

Set the Attribute

Run the Application
 Attribute is set to currency as HOT.VALIDATE

 Routine called immediately after exit from Currency
 Thus becomes field level Validation

HOT.FIELDS Vs HOT.VALIDATE
 In browser field level validations are done when field is

• HOT.FIELD
• HOT.VALIDATE
 Hot fields are shown with a next to them.

 Hot Validates are show with a next to them
 Hot fields can be used to default other field values
 Hot validate can be used for validation only
 When Hot validate is given immediately validation is done for
the other fields too

Hot Field Example
 Create a Version for Account with the following fields

• Customer
• Category
• Currency
• Mnemonic
 Make Customer as hot field. On coming out of customer the

Mnemonic field should be updated as
<CUS><Number of Accounts>

Solution

Solution

PGM.FILE

EB.API

Create version

Create version

Create version

Run the Version

Run the Version

Run the Version

Scenario
 Create a version for the FUNDS TRANSFER application with

the following fields
• Transaction Type
• Debit Account Number
• Debit Currency
• Debit Amount
• Debit Value Date
• Credit Account Number
• Credit Currency

Scenario
 As soon as the Debit account number is entered, Validation

Routine should check whether it is a savings account
otherwise it should throw an error “DEBIT ACCOUNT IS
NOT A SAVINGS ACCOUNT’

Routine

Version

Version

Output

Workshop 2
 Create a version in FT with mandatory fields if the debit

amount is greater than working balance then display error
Message.

Input Routines
 Why Input routine?

 When Input Routine is called?
 How to Create Input Routines – Scenario.

Why Input Routines
 Update local files

 Provide additional validation at input stage
 Provide override processing

When do Input Routines Called
 Gets invoked when committing a transaction

 All validations might have been completed

Where do we attach Input Routine

 Entry in EB.API

Scenario
 Create a Version for Funds Transfer version with the

mandatory field. Write an Input routine to check if the
CREDIT CURRENCY and the DEBIT CURRENCY match. If
not an error message, “Credit and Debit currency mismatch”
needs to be displayed when the user commits the record.

Routine

Attach routine to the Version

Validate

Commit

Workshop 1
 Create a version for Account with mandatory fields and the

following validations done in input routine
• Account should be savings
• Customer should be an individual

Routine

Version

Output

Authorisation Routine
 Why Authorisation routine?

 When Authorisation Routine is called?
 How to Create Authorisation Routines – Scenario.

Why Authorisation routine
 To update local files
 To provide additional validation at authorization stage
 To provide override processing

When Authorisation Routine is Called
 Time of Authorisation of Transaction

 After Field level validations.
 After standard default processing is done.

Where do we attach the Routine

How to create Authorisation Routines -
Scenario
 Once a record in a version of the FUNDS.TRANSFER application
is authorised, details from the transaction need to be extracted and
written on to a flat file named TRG.FT.DATA for interface
purposes.
 ID of the record in the flat file needs to be the FT id
 Following field’s values need to be stored in the flat file all
delimited with a single space
 Credit Account Number
 Debit Account Number
 Value Date
 Debit Amount
 Debit Currency

Solution
 Creates a Sequential File

 File created for updation

Routine

Compile and Catalogue

Create the Version

Commit the Version

Value in TRG.FT.INTERFACE

Workshop 1
 Create version for Account application and input a record

using the version.
 When the record is authorised using the version it has to
check for
• If the Currency is USD or GBP then Nationality or residence of
the customer should be US
• Else
it should display a error message “WRONG CURRENCY
ENTERED FOR THIS CUSTOMER”

Solution

Attach the routine

Authorise

Scenario
 What happens if no of authorisers is two

• First Authorisation will not call authorisation routine
• Its called during Second authorisation

Second Authorisation

After First Authorisation

Error Handling
 Should include Override-1 field in the Version

Error Handling

Auto Field Routine
 Why Auto field routine?

 When auto field Routine is called?
 How to Create Auto field Routines – Scenario.

Why AutoField Routine
 To perform any special editing to a record.

 To modify the record as soon as id is fetched.

When Autofield Routine is called?
 After id of the record is input.

 After record is fetched
 Before it is displayed.

 Entry in EB.API

Where do we Attach the routine
 To the field Auto New Content

How to Attach routines- Scenario
 Create a Version for Account which mandates the account

officer to 1 if the sector is 1001 or else 2

Routine

Attach the Routine

Run the Version

Workshop
 Create an FT version which displays value date to be 1st

January of the current year.

ID Routine
 Why ID routine?
 When ID Routine is called?
 How to Create ID Routines – Scenario.

Why ID Routine?
 To manipulate the id of the record.

When is it called
 As soon as id of the record is entered

 Before fetching the Record

Where do we attach routine
 In the version Application

 Id routine field.

Mandatory Prerequisites
 Entry in EB.API

How to attach the routine - Scenario
 Create a version for the Enquiry application with all the

mandatory fields
 Create subroutine that will get executed as soon as the id of
an enquiry is entered and prefixes the id of the enquiry with
‘THE.TRG’ provided it is not a %Enquiry or an Enquiry-List.

Routine

Create Version and attach routine

Run the version

WorkShop 1
 Create a version for acct application when a new Account is

created, check if the 3rd and last digit does not have the
same no. if the nos. are same then increment the no. by
one.

Routine

Attach the routine

Output

Workshops
 Write a version routine that will check and not allow ID nos.
less than auto generated FT ID for the new FT.
 Create a version for customer application when a new
customer is created and an ID is given it should be prefixed
with 'CU'.

Check Record Routine
 Why Check Record routine?

 When Check Record Routine is called?
 How to Create Check Record Routines – Scenario

Why Check Record Routine
 To alter field attributes.

 Alteration to be done after validation id.

When Check Record Routine is Called
 After the ID is supplied and validated.

 Get invoked with the following functions being performed
• I(Input)
• D(Delete)
• A(Authorise)
• R(Reverse)

Where do we attach the routines?
 Attached to the field CHECK.REC.RTN

How to attach Routine
 Write a subroutine that will restrict any user trying to open a

Live Customer Record which was not input and authorised
by him and will display an error message “Access
Restricted”

Routine

Routine

Attach the routine

Run the Version

Workshop
 Write a version routine for the Account to decrease amount

by 5 if account is not opened by inputter or authoriser.

AfterUnauth routine
 Why AfterUnauth routine?

 When AfterUnauth Routine is called?
 How to Create AfterUnauth Routines – Scenario

Why AfterUnauth
 To perform any operation after Input Routine

 After Committing the record.
 Without affecting the existing record

When is it called?
 While Committing a new/existing record

 After the record been written into the $NAU file.

Where do we attach routine

How do we attach- Scenario
 When a transaction is committed using a version of the FT

application, the user should be taken to another version in
order to input the charges (if any).

 Entry in EB.API

PGM.VERSION
 Common variable
 Contains the name of the currently opened version.
• Example : CUSTOMER,INPUT
– APPLICATION : CUSTOMER
– PGM.VERSION :,INPUT

INPUT.BUFFER
 Common variable.
 Any input that a user wishes to execute from the command
line.
• Example
– INPUT.BUFFER = C.U:”CUSTOMER I” : C.F

– C.U : Ctrl U Enter -> will go to the command line
– C.F : Ctrl F Enter(F3) -> Used to obtain a new id

V$FUNCTION
 Common variable.
 Contains the function that is being currently chosen by the
user.

Routine – Reflection Mode

Attach the Routine

Execute the version – Reflection Mode

After Commit – Reflection Mode

Routine – Browser Mode

Attach the Routine

Execute the version

Commit

Workshop
 Create a version for Account as soon as a new Account is

created a teller version is called to deposit LCY amount

BeforeAuth Routine
 Why BeforeAuth routine?

 When BeforeAuth Routine is called?
 How to Create BeforeAuth Routines – Scenario

Why Before Auth
 To Perform Any operation after Commit

 To perform Operation before Authorise

When BeforeAuth is called?
 During authorization of an INAU record.

 Called before Version Auth routine is executed.
 Before.Auth – Before F.WRITE.
 Changes made to R.NEW will reflect in the record written
AUTH routine – After F.WRITE

Where to Attach the Routine?
 BeforeAuth Rtn.1 field of the Version

 Entry in EB.API

How to Attach Routines - Scenario
 While authorizing a customer record, the user should be

given the option to fill in any special comments with the
customer record like “Special Customer”.
 Write a routine that will prompt the user to enter free text
while authorizing a customer record.
 Once the text is entered by the user, the data needs to be
updated in the field TEXT in the Customer application.
 If no text is entered by the user then the message “No text
entered. Proceeding with other processing” should be
displayed and the record should get authorized.

Routine

Attach the routine

Attach the routine

Workshop
 Write a routine for an FT version such that

• if
the debit Currency is a foreign currency then debit amount is
converted to local currency equivalent
• and currency should be changed to local currency.

Version Control
 Why Version Control?

 Features of VERSION.CONTROL.
 Fields in VERSION.CONTROL.
 Fields that would be affected by VERSION.CONTROL

Why VERSION.CONTROL?
 To make a subroutine available to set of Versions

 To make a subroutine available to the Application

Features of the VERSION.CONTROL
 Can attach subroutines to application level.

 To execute these subroutine
• EXC.INC.RTN is yes for Versions
 Id of the VERSION.CONTROL
• APPLICATION NAME
• APPLICATION NAME,VERSIONTYPE
 Subroutine at version level have higher priority over
VERSION.CONTROL level

Fields in VERSION.CONTROL

Fields that have impact in Version
 EXC.INC.RTN
• ‘Yes’
– Routines specified in VERSION.CONTRL will be
invoked.
• ‘No’ or ‘Blank’ – Routines wont be invoked.
 VERSION.TYPE
• Id of the VERSION.CONTROL application

Example
 Create a record in the VERSION CONTROL to update the

currency field in the Account application with type TRG to
local currency

Routine

Attach to ACCOUNT,TRG of
Version.control

Version linked with Version.control

All product names and other company names used herein are for identification purposes only and may be
trademarks or registered trademarks of their respective owners. Errors and omissions excepted,
all specifications are subject to change without notice.
© 2009 Thesys Technologies Incorporated. All rights reserved.
FOR MORE INFORMATION

Visit : www.thesys.co.in
email : marketing@thesys.co.in

Version Routines: Technical Courses

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Version Routines: Technical Courses

Uploaded by

Copyright:

Available Formats

Version Routines

Days 5-7 – Sessions 1-4

 Why Version Routines

3 Thesys Training Centre

4 Thesys Training Centre

5 Thesys Training Centre

6 Thesys Training Centre

 For Additional Validations During

7 Thesys Training Centre

8 Thesys Training Centre

 Common variable defined in I_COMMON

9 Thesys Training Centre

 Common variable defined in I_COMMON

10 Thesys Training Centre

 Definition in I_COMMON : DIM R.NEW(C$SYSDIM)

11 Thesys Training Centre

12 Thesys Training Centre

13 Thesys Training Centre

14 Thesys Training Centre

15 Thesys Training Centre

16 Thesys Training Centre

17 Thesys Training Centre

 Why Validation routine?

18 Thesys Training Centre

 To perform Field level validations.

19 Thesys Training Centre

20 Thesys Training Centre

 Attached to the specific field of the version.

21 Thesys Training Centre

22 Thesys Training Centre

 Create a version for Account with the following fields

 Write a Validation Routine to Validate the Currency as USD.

23 Thesys Training Centre

24 Thesys Training Centre

25 Thesys Training Centre

26 Thesys Training Centre

27 Thesys Training Centre

28 Thesys Training Centre

 Attribute is not set to Currency

29 Thesys Training Centre

30 Thesys Training Centre

 Attribute is set to currency as HOT.VALIDATE

31 Thesys Training Centre

 In browser field level validations are done when field is

 Hot fields are shown with a next to them.

32 Thesys Training Centre

 Create a Version for Account with the following fields

 Make Customer as hot field. On coming out of customer the

33 Thesys Training Centre

34 Thesys Training Centre

35 Thesys Training Centre

36 Thesys Training Centre

37 Thesys Training Centre

38 Thesys Training Centre

39 Thesys Training Centre

40 Thesys Training Centre

41 Thesys Training Centre

42 Thesys Training Centre

43 Thesys Training Centre

 Create a version for the FUNDS TRANSFER application with

44 Thesys Training Centre

 As soon as the Debit account number is entered, Validation

45 Thesys Training Centre