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. |
|   |
Table 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 present 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 function is used to access the documentation management on the first paragraph of the documentation (if there is one) associated to the current record.
This function is used to access the links management. It is used to define the links between the current and other records (for example the links between functions and setups). These links are specific to the documentation and are used to load the generation of documentation structures.
This menu is used to launch a documentation generation. The generation can also be launched from the [Generation] button at the bottom of the window.
Three types of generation can be launched one by one or simultaneously:
The range suggested by default takes into account the current record but it can be modified upon launch.