You can then:
Close
Fields
The following fields are present on this tab :
Folders
| Define the code for the folder in which the source elements are found. |
| Define the code for the folder on which the search is carried out for the elements to be compared. |
Grid Installed modules
|   |
| This field displays the list of modules. |
| Select Yesto include the elements of the corresponding module. |
Grid Object to process
|   |
|   |
|   |
|   |
Options
| Select this check box to generate a detailed log file. You can specify the detail of the differences to log such as on which field, what are the distinct values. Selecting this check box also adds a line signaling identical elements to the log file. |
| Define the language in which the comparison at the message level is carried out. If left blank, the comparison is carried out in all languages. |
| Select this check box to add the technical sheet additional information to the log file (when it occurs the field name for the dictionary involved with the differences). |
| Select this check box to save the results in a CSV file. |
| If the Filecheck box is selected, you can define the file format (asci, utf-8, usc-2). |
Filter
| Use this field to enter an activity code used as a filter for all elements that have an activity code. |
Close
Action icon
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line.
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line.
Close
This function can be run in batch mode. The standard task ACOMPOBJ is provided for that purpose.
This type of utility has a very long execution time if it is launched for the entire dictionary. It is therefore advised to limit the elements to compare and if necessary, to filter them by module.
Shown below are examples of the messages likely to be displayed in the log file:
Line type | Log file example |
Element header | Source folder: XXXX Target folder: YYYY Screens DD-MM-YY hh :mm -------------------------------- |
OK comparisons | XXXXXX Identical screen nnn Identical chapter |
Nonexistent elements (level 1) | XXXXXXScreen does not exist under FOLDER FFFFF Window does not exist under FOLDER CCCC Inquiry does not exist under FOLDER |
Nonexistent elements (level 2) | XXXXX / Field YYYY nonexistent FOLDER CCCC /Field YYYY Difference YYYY’ |
Level 1 differences | Screen XXXXXX / [AMK]OPTION Grid options ‘options 1’ => ‘options 2’ Screen XXXXXX / [AMK]INTMSK Different titles ‘title 1’ => ‘title 2’ Object XXXXX / [AOB]TRELIS Hierarchical list of differences ‘value 1’ => ‘value 2’ |
Level 2 differences | Screen XXXXX / Field YYYY / [AMZ]NUMBLOC Block number ‘value 1’ => ‘value 2’ Table XXXXX / Field YYYY / [ATZ]NOLONG Long text difference ‘text 1’ => ‘text 2’ Module nnn/ Message mmm Difference ‘message 1’ => ‘message 2’ |
Level 3 differences | Screen XXXXX / Field YYYY / Control Action STD / [AMA]WEBSAI ‘value 1’ => ‘value 2’ |
You can also find in the log file the identification of the element and its sub-elements (e.g. screen, field, action), as well as the name of the dictionary field in which the difference was found.
The field names are not displayed if the Technicalcheck box is not selected.
In addition to the generic error messages, the following messages can appear during the entry :
The server with the name server does not respond (either because it is not accessible via the network or the service daemonadxd has not been launched).