How To Use VERSION - contROL Application With VERSION

12/17/2018 How to use VERSION.CONTROL application with VERSION.
Temenos Support Forum (/SitePages/tsf.aspx) Portal Help shinewilson
Customer Support
Portal
(/SitePages/Home.aspx)
 MENU Entire Site Enter your keywords here 
How to use VERSION.CONTROL?

Introduction
This document explains the purpose and usage of the application 'VERSION.CONTROL.'
1) Usage of the elds NON.VERSION.RUN and EXC.INC.RTN in VERSION.CONTROL

 (/SitePages/Home.aspx)
NON.VERSION.RUN
 (/SitePages/T24Intelligence.aspx)
 When this eld is set to 'Y', it means that the routines say
VALIDATION.RTN/INPUT.RTN/AUTH.RTN/ID.RTN/CHECK.REC.RTN/AFTER.UNAU.RTN/BEFORE.AUTH.RTN that
 (/TCSPProfileCenter/infodefault.aspx)
are attached to a VERSION.CONTROL record of an application will be applicable to all its version as well the
 (/Support/DashBoard.aspx)
application.
When this eld is set to 'N', then the routines attached to the above elds will be triggered only for the
application version and not for the application.
EXC.INC.RTN
This eld will work together with the above said eld NON.VERSION.RUN. A routine triggeration can be either
allowed or restricted at the particular version record itself using this eld.
Example if the NON.VERSION.RUN eld is set to 'Y' in a VERSION.CONTROL record of CUSTOMER and
EXC.INC.RTN is set to N' in a particular VERSION record say CUSTMER,ABC means then the routine attached in
the VERSION.CONTROL will not be triggered for this particular version alone.
Example screenshots:
A sample VALIDATION routine is attached to the VERSION.CONTROL record CUSTOMER
CASE 1:
1. The eld NON.VERSION.RUN is set to "Y" in the VERSION.CONTROL record CUSTOMER
https://tcsp.temenos.com/HowTo/Versioncontrol.aspx 1/10
2. The eld EXC.INC.RTN set to "NO" in a particular version record (CUSTOMER,ABC)


3. When 'US' is given in the eld RESIDENCE , the routine de ned in the VERSION.CONTROL is called for CUSTOMER
application and not for the particular version (CUSTOMER,ABC) as shown below,

Please note, in the above case other than the version CUSTOMER,ABC the routine will be triggered for all other
CUSTOMER versions having EXC.INC.RTN set to 'Y'
CASE 2:
1. In the VERSION.CONTROL, the eld NON.VERSION.RUN is set as "N"
2. The eld EXC.INC.RTN set to "YES" in version record CUSTOMER,ABC


3.In this case when 'US' is given in the eld RESIDENCE the VALIDATEROUTINE de ned in the VERSION.CONTROL
was called for only the VERSION (CUSTOMER,ABC) and not for the application (CUSTOMER) as shown below,

2) Routines attached to the VERSION.CONTROL record of an application can be even made to trigger for a particular
group of that application versions alone using the eld VERSION.TYPE in VERSION record
This can be achieved by having the VERSION.CONTROL ID in the format APPLICATION, TYPE
The <TYPE> should be of three character and need to be attached in the VERISON record in the
eld VERSION.TYPE as shown in below screenshot.
3) Usage of the elds AUTOM.VALUE, AUTOM.TYPE, AUT.FLD.NO, AUT.NEW.CONT, AUTOM.INC.EX in

VERSION.CONTROL
This is an associated eld set, hence each eld has to be input mandatorily.
1) In either of the below two formats the eld AUTOM.TYPE can be used:
i. APPLICATION>FIELD.NAME
In this format, if the outcome of the about format matches with the value given in the eld
AUTOM.VALUE. If it matches then the eld name given in the eld AUT.FLD.NO will get defaulted with the
value given in the eld AUT.NEW.CONT
If the match fails, then the value will not get defaulted.
Also in this format, the APPLICATION can be either USER or COMPANY. This is because the AUTOM.TYPE
eld of the version. control record would be executed, before a record is opened using the respective
version. Hence only the common variables like R.COMPANY and R.USER would have been loaded with values.
If there is a requirement to access the eld values of any other applications, we request you to create a
routine and attach it to the eld AUTOM.TYPE of the version. Control record.
ii. Routine can be attached
In this format the attached routine output in the eld AUTOM.TYPE should match with the value given in the
eld AUTOM.VALUE. If it matches then the eld name given in the eld AUT.FLD.NO will get defaulted with
the value given in the eld AUT.NEW.CONT in the appropriate version.
If the match fails, then the value to be defaulted in the version/application will not get defaulted.
2) For the values that are to be defaulted using above elds into the particular version, the VERSION.CONTROL ID
should be of the format APPLCATION,TYPE as shown,

The above set up meant that, if the ID.COMPANY matches with the value set in AUTOM.VALUE, then the elds
de ned in AUT.FLD.NO will be defaulted in the appropriate VERSION, otherwise system wont default the value.
The above setup will default the value BNK as shown (setup will work in browser alone)

4) Usage of the Rest elds

Combined eld set - NOINPUT.VALUE, NOINPUT.TYPE, NOINPUT.FLD, NOINP.INC.EX
Combined eld set - NO.CHG.VALUE, NO.CHG.TYPE, NO.CHG.FLD, NO.CHG.IN.EX
Combined eld set- REKEY.VALUE, REKEY.TYPE, REKEY.FLD, REKEY.INC.EX
Combined eld set- MAND.VALUE, MAND.TYPE, MAND.FLD, MAND.INC.EXC
All the above combined eld set will follow the same setup as well as the format as that
of the AUTOM.TYPE eld explained earlier.
Usage of the elds NOINPUT.VALUE, NO.CHG.VALUE, REKEY.VALUE, MAND.VALUE are shown below,
SETUP:

NOINPUT FIELD:
In VERSION.CONTROL record
In a new FT Transaction:
REKEY MULTI FIELD SET:
We set the eld DEBIT.ACCT.NO as rekey eld. The No of auth should be 1 for this version. When we try to authorize
using another user it will ask you to re enter the values which are input by inputter already.
If the data entered by the Authorizer does not match with the Inputter data, then the record does not get
authorized. The rekey elds are marked in red to denote incorrect data. Once the entered value matches with the
correct data the record gets authorised.
In VERSION.CONTROL record

If the authoriser inputs the wrong values which is inputted by inputter, then it will throw the error message
as below
MANDATORY FIELD:
COPYRIGHT © 2018 TEMENOS HEADQUARTERS SA
(http://www.temenos.com/)
Best viewed in Internet Explorer 10 & above


How To Use VERSION - contROL Application With VERSION

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

How To Use VERSION - contROL Application With VERSION

Caricato da

Copyright:

Formati disponibili

12/17/2018 How to use VERSION.CONTROL application with VERSION.

Temenos Support Forum (/SitePages/tsf.aspx) Portal Help shinewilson

 MENU Entire Site Enter your keywords here 

How to use VERSION.CONTROL?

1) Usage of the elds NON.VERSION.RUN and EXC.INC.RTN in VERSION.CONTROL

2. The eld EXC.INC.RTN set to "NO" in a particular version record (CUSTOMER,ABC)

2. The eld EXC.INC.RTN set to "YES" in version record CUSTOMER,ABC

3) Usage of the elds AUTOM.VALUE, AUTOM.TYPE, AUT.FLD.NO, AUT.NEW.CONT, AUTOM.INC.EX in

ii. Routine can be attached

4) Usage of the Rest elds

REKEY MULTI FIELD SET:

Potrebbero piacerti anche