VERSION

1. How to connect VERSION.CONTROL with VERSION?

We need to enable Exc Inc Rtn as YES in version application.
2. What are the status if Number of auth is 2?
When number of auth is set to 2, two different users must authorize the
record. When the record is authorized for the first time, it moves to INA2
status. In order to make it as a LIVE record, the record has to be authorized
by a different user again.
3. How to give color to a field?
Predefined - We can give color to a field using attributes field in version
application.
Customized – Create a new class custom.css in BrowserWeb. Create an
entry in EB.ATTRIBUTES application with the class, Enter the ID of EB.
ATTRIBUTES record to the attribs field of version application.
4. What will happen if we raise overrides and error message in validation
and input routine?
Validation routine: The error messages and overrides will get raised once we
commit the record or tab out of the field.
Input routine: The error messages and overrides will get raised only when
committing or validating the record.
5. What to do if we want to run an application while running COB?
While creating a template routine we need to set C$NSOPERN to ALL. The
application which are coming under NonStop module can be run while
running the COB.
6. How to pass value from one application to another application?
We can pass value from one application to another application through Auto
New Content field.
7. Created a parent version with number of auth as 2. Child version posting
a OFS message with number of auth as 0. Now what is the number of
auth to post OFS message?
It will consider the number of auth as zero. Whatever auth field we are
mentioning in OFS message will be having the first priority.
8. Before unauth and after unauth differences.
 Before Unauth: Before Auth Routine allows you to do some processing
before writing the record to the live file, Invoked during the authorization
stage of an $NAU record, Invoked before the WRITE is made to LIVE file,
Any fields can be modified at this stage.
 After Unauth: This routine is called while committing a new record or
existing record after making the necessary changes. It is called after the
Version Input Routine, After Un auth Routine is used to edit a record written
to the $NAU file, Any changes made to R.NEW will not be reflected as it
has already been written to the $NAU file.

9. Is field no mandatory or not in VERSION?

 Field No is not mandatory if we give RECORDS.PER.PAGE and
FIELDS.PER.LINE value as 1 and 1.
 But we if give the RECORDS.PER.PAGE and FIELDS.PER.LINE value
as Multi for both the fields then Field No is mandatory.

10.OFS.addLocalRequest -In which version routine we can use it and in

which stage it is used?
 In BEFORE.AUTH.RTN and in Authorization Stage it is used.
 The user defined BEFORE.AUTH.RTN will be invoked the new public API
to add additional requests from the authorization of the master record.
Multiple requests can be added.
 Child requests can also add additional requests through the
BEFORE.AUTH.RTN applied to the version too. The local code in the
BEFORE.AUTH.RTN should be able to determine whether requests
processed to date in the bulk transaction are successful or not – this will
allow flexibility to only add additional requests when all previous requests
are successful.
11.In which stage you can raise an error, what happen if we raise an error in
auth routine?
We can raise an error in before authorization stage and if we raise an error in
auth routine, error will be raised but record will be authorized.
Ex:- an error message if Amount is less than 50 (Error Message - Amount
Less than Minimum Fare).

12.Explain Rekey fields?

Rekey field enables authorisers to re-enter the data in specific fields so as to
re-confirm the entry done by the Inputter. The rekey feature can prompt the
Authoriser to re-enter the data for confirmation. If the data entered by the
Authoriser does not match with the Inputter, then the record does not get
authorised. The data for the rekey fields are hidden during authorisation and
the Authoriser needs to compulsorily re-enter the information.
For example in a FUNDS.TRANSFER application, there are sensitive data
like amount, debit account no etc, which are entered by an Inputter.
 The system records the number of incorrect rekey attempts by a same
authorizer, in a file called EB.REKEY.RETRIES. A record is created in
this file whenever a version that contains a rekey field is being authorized.
The record id of EB.REKEY.RETRIES would be of the format
COMPANY*APPLICATION*RECORD.ID. The maximum number of
incorrect retries allowed for a USER who tries to authorize a record can
be restricted using the field NO.OF.RETRIES in SPF application. When
this field is left blank, there is no limit set for incorrect rekey attempts.

13.Can Rekey feature be used on “No Input” field?

No it is not possible to apply Rekey feature on a “No Input” field. Since there
must be some value before we perform validation on the field during
authorization.
14.Brief about VERSION.CONTROL?

 VERSION.CONTROL is a T24 application that provides 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.
 One VERSION.CONTROL record can be linked to multiple VERSION
records via the VERSION.TYPE field on VERSION.
 If the record id in VERSION.CONTROL is the application name itself, then
the routines specified here are applied to the application.

15.How EB.TABLE.DEFINITION and EB.TABLE.PROCEDURES are

linked together?
They’ll be linked together by checking the “Link to wfl” checkbox in
EB.TABLE.DEFINITION.
16.What are the status types (in order) if NO.OF.AUTH is 2.
INAU, INA2, LIVE
17.In which Routine we have to give override messages?
.VALIDATE and .OVERRIDES Routines are used to place override
messages.
18.Explain ATTRIBS fields?

 This field defines a number of Attributes for the Version.

 This includes whether the field is a Hot Field or not. This causes the
contract to be validated when the user exits the field thus displaying all
errors for the current contract. Marking a field as a Hot Field will also
ensure that the application is called when the field is exited. Therefore,
this mechanism can be used to default other field values once the
current field value has been entered.
 Validation Rules:
 HOT.FIELD - This indicates that the field is a Hot Field in the
Browser.
 ENRICHMENT.ONLY - If a field is NOINPUT then display the
enrichment in place of the field. If inputtable then display Enrichment
only via a control.
 POPUP.DROPDOWN - If this field has a dropdown then set behaviour
to popup in new window with paging tools.
19.HOT.FIELD and HOT.VALIDATE differences:
 HOT.FIELD – check field validation will be performed on this field and
only shows the errors for the current field.
 HOT.VALIDATE – check field validation will be performed on all the
fields.

20.Version Common Variables:

 COMI – holds last input data. Every time when you tab out of a field,
the data that you input in the field is available in the common variable.
 ID.NEW – holds the ID of the currently opened record.
 R.NEW – holds the actual records.(record value)
 ID.NEW.LAST - holds the ID of the currently opened record’s
unauthorized record.
 R.NEW.LAST - holds the actual unauthorized record.
 ID.OLD - holds the ID of the currently opened record has authorized
record.
 R.OLD – holds the actual live records.
ENQUIRY

1. UI elements that we can link to drilldown?

 Defines the next enquiry or application and we can also define
VERSION of an application. We can also view a text record, such as a
report the option VIEW should be specified.
 To invoke another enquiry the name of the enquiry should be entered.

2. How can u pass default value in the version based on the values in the
enquiry result/How to default the customer no in the version from the
enquiry drilldown.
 The ENQUIRY application in T24 allows to invoke the other
applications. This is known as Context based Workflow.
 Using this Enquiry invoke a Version that creates Account for the
Customers.

VERSION

ENQUIRY AMENDMENT

3. How can we see per record per page in ENQUIRY Application?

With the help of break change, in OPERATION field we can implement it.
4. What is NOFILE Enquiry?
 NOFILE enquiries can be used when an enquiry needs data from more
than one file in T24.
 This is defined as NOFILE because the enquiry is not designed to a
single file.
 A NOFILE enquiry involves a subroutine to be written with a return
parameter in order to extract the data from different application.
 The return parameter holds the data to be displayed in the enquiry
output.
 A NOFILE enquiry does not have an associate file, so it does not have
field definitions and hence no Standard Selection record.

5. Which value can used as delimiter?

 Any value can be used for delimiter.
 It is designer or user preference.
 Usually we use *. If Multiline is there for a column then we use # for
SV.
6. Enquiry Common Variables:
 I_ENQUIRY.COMMON – it is insert file and holds the common
variables specific to enquiries. This file is similar to I_COMMON and
I_EQUATE.
 O.DATA - holds the last extracted value in the enquiry. This is similar
to the variable COMI in I_COMMON which holds the last entered
value.
 R.RECORD – Holds the record pertaining to the current ID that has
been extracted.

7. In Enquiry, How we can extract the Enquiry Name?

 Used Build Routine to Extract the Enquiry name and print the value of
ENQ.DATA<1> - stores the Enquiry Name.

8. Is it possible to without passed the fields in Drill down Enquiry?

 Not Possible, without passed the fields in drill down enquiry it is
called normal enquiry. The purpose of drill down enquiry access
through hyperlink and get all the details of child enquiry.