Refer to documentation Implementation
A hierarchy is created by defining information in the header, then completing lines, exclusively by picking from the Classes and objects list. This picking list, organized into a hierarchy, displays all the objects available in the universe associated with the live datamart
On an existing hierarchy, it is possible to:
Presentation
The lines in the grid list the objects, their classes and sub-classes.
Close
Fields
The following fields are present on this tab :
Block number 1
|   |
|   |
|   |
|   |
|   |
Characteristics
| Defines the code for the datamart in which the hierarchy is defined. |
| An activity code is used to:
In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated. |
|   |
Grid Classes
|   |
|   |
|   |
Sort
| Button that is used to move the current line to the top of the grid. |
| Button that is used to move the current line to the bottom of the grid. |
Close
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close This button is used to copy the record definition from or to another folder. |
This choice of menu allows to zoom to the documentation management, on the first documentation paragraph (if it exists) related to the current record.
This choice of menu allows to zoom on the dictionary link management function. This function allows to establish links between the current record and other records (for example links between functions and parameters). These links, dedicated for documentation purpose, allows the generation of documentation structure.
This choice of menu allows to generate the documentation. Three types of generation can be separately or simultaneously started :
The ranges and parameter proposed by default are defaulted according ti the current record, but they can be changed during the execution.