Validation @ L.V. Expertise X3

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Tab Entry screen
Error messages

Screen management

The entry of parameters is carried out in a single tab.

Entry screen

Presentation

Next, select the elements types (and ranges) to be revalidated for the following:

The database tables (the forced validation tick box causes the regeneration of tables by temporary copy even if no structure modification is detected).

The screens (when validated, create XML files executable by the client/server engine and refreshed on Web servers if they exists).

The objects, windows and enquiries (when validated, create processes with the .adx extension executable by the engine, as well as the XML files necessary for the update of the Web servers if they exist).

The following supplementary filters are possible :

A data type (if it is assigned, only the elements using this type of data are revalidated).

An activity code (if it is assigned, only the elements using this type of activity codes are revalidated).

One or more modules (only the elements attached to modules for which a Yes has been selected are revalidated).

A supplementary tick box, test mode, makes it possible, if it is ticked, to only list the elements that would be revalidated given the filter criteria given.

The launch of this operation can be long, and it can be carried out in batch mode. A log file is created in all the cases. Found here is the detail of the operations carried out and any possible errors. It is advisable to read this file closely when the operation is finished.

Fields

The following fields are present on this tab :

Block number 1

Folder (field APPLI)

Define the code of the folder in which the work will be carried out (such as it is defined in the table of the folders).

Validation (field TYPVAL)

Deferred validation (field VALIDDIF)

This option is used to avoid directly validating windows and screens in order to optimize the validation time of these objects.
If this box is checked, the windows and screens will be validated when first used.

Test mode (field TEST)

When this box is checked, only a list of elements that should be validated is provided in the log file without any validation taking place.

Table Installed modules

Module (field MODULE)

This grid is used to define (by responding Yes for the lines concerned) the elements to be validated by filtering by functional module.

Validation (field VALMOD)

This grid is used to define (by responding Yes for the lines concerned) the elements to be validated by filtering by functional module.

Object to process

Table validation (field VALTAB)

When this box is checked, the tables are re-validated. The revalidation of a table implies the update of the table structure if it previously existed, in order that it can conform to the description in the dictionary.

Forced validation (field FORCE)

When this box is checked, the tables are revalidated in forced mode (that is to say the table is copied by provisionally changing its name).

Validation of views (field VALVUE)

When this box is checked, the views are re-validated. A revalidation of a view implies the creation or update of the view so that it conforms to that described in the dictionary.

System class validation (field GENCLATECH)

Class validation (field VALACLA)

Link synchronization (field GENASWLNK)

Representation validation (field VALASW)

Screen validation (field VALECR)

When this box is checked, the screens are re-validated. A screen revalidation implies the generation of the XML structure of the screen, on the application server, in the publication directory associated with the folder.

Generated screens (field GENECR)

When this box is checked, the screens generated from the parameterization are revalidated (notably the transactions parameterization). These screens have names starting with W.

Object validation (field VALOBJ)

When this box is checked, the objects are re-validated. The revalidation of an object implies the generation of an automatic process on the application server, potentially the update of any standard, custom or vertical processes, as well as the production of an XML file.

Window validation (field VALFEN)

When this box is checked, the windows are re-validated. A window revalidation implies the generation of the XML structure of the window, on the application server, in the publication directory associated with the folder.

Generated windows (field GENFEN)

When this box is checked, the windows generated from the parameterization are revalidated (notably the transactions parameterization). These screens have names starting with W.

Inquiry validation (field VALCNS)

When this box is checked, the inquiries are re-validated. An inquiry revalidation implies the generation of a process and its compiling on the application server, in the TRT directory of the folder.