Object Difference
This function is used to globally compare dictionary elements between two folders. The result is given in the form of a log file which level of detail depends on the execution options selected.
Screen management
Entry screen
Presentation
The two folders to compare are defined in the screen. By default, the current folder is suggested, but it is possible to give the name of another accessible folder, using the syntax detailed in the attached documentation.
A sequence of checkboxes are used to select, among all the dictionary elements, which are those to be compared (with associated code ranges).
Additionally, a filter is specified for the modules with the elements to be compared, as well as additional options.
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 in which the search will be carried out for the elements to be compared. |
Grid Installed modules
|
|
| [object Object] |
| If Yes is entered in this field, the elements of the corresponding module are taken into account in the process. |
Grid Object to process
|
|
|
|
|
|
|
|
Options
| This box is used to have a detailed log file : When this box is checked, specify the detail of the differences to log (on which field, what are the distinct values). The fact that this box is checked also adds a line signalling identical elements to the log file . |
| Define the language in which the comparison at the message level will be carried out. If left blank, the comparison will be carried out in all the languages. |
| If this box is checked, the technical sheet additional information is added to the log file (when it occurs the field name for the dictionary involved with the differences). |
|
|
|
Filter
|
|
Close
Action icon
Yes to all the rest
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.
No to all the rest
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.
Remarks
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.
Log file displayed in the resulting file
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 module |
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’ |
Also found in the log file is the identification of the element and its sub-elements (for example screen, field, action), as well as the name of the dictionary field in which the difference was found. The field names do not appear if the Technical checkbox is not checked.
Close
Batch task
This function can be run in batch mode. The standard task ACOMPOBJ is provided for that purpose.