User menu profile
This function is used to associate a profile code (itself associated with the users) to a menu structure used to access the different functions in the software, as well as two associated additional parameters.
Prerequisite
Refer to documentation Implementation
Screen management
Entry screen
Presentation
The entry of the menu profile is made in a single tab, in which is found two characteristics in particular (which did not exist in version 130) :
the first characteristic is a profile type defined by local menu 926, which contains 3 values by default. The interest of this type of profile is to be able to limit the number of users connected simultaneously under a given profile type. This is made with the help of the parameters USR1, USR2, and USR3 (this list of parameters can be completed with the custom/specific parameters USRn, n being the rank of the profile type in the local menu).
the second characteristic concerns an addition memory value, expressed in Kbytes, associated with the engine that executes the user processes having the corresponding menu profile. This parameter, defined globally for a given folder by the field Memory in folder management, which can therefore be modified for certain users that launch functions that are particularly heavy in terms of consumption.
Following this there are two grids in this tab :
the first concerns the definition of the current menu (by default, the first when opening an existing profile)
the second is used to display the detail of the titles in the current sub-menu, if the line currently being entered in the first grid is found in a menu :
The management of these grids is used to successively pass from one menu to another or to return to a higher level. The Menu structure field that is displayed is used to identify the current level. If already located at the highest level (assuming that the highest level menu is called GENE, which is the default case), GENE is displayed here. If located in the sub-menu MDITM, which is itself a sub-menu of the MDBA menu referenced in the GENE menu, the display of the structure will be in the form GENE/MDBA/MDITM.
Creation of a menu profile
When creating a new profile menu, the cursor should be placed on the Start Menu field, this is used to pick up by default the name of one of the standard menus defined for the super user (ADMIN by default). Once a standard menu is selected, all the sub-menus attached to it are also loaded :
if GENE has been selected as the start menu (default value proposed on creation), a complete standard menu structure for the software is obtained (it is then possible to modify the different menus line by line).
it is possible to choose another menu (thanks to the selection key) in order to load only part of the menu structure.
Menu profile modification
In menu profile modification the Start menu field is not accessible.
When in entry mode in the grid, it is possible to modify the menus by simply inserting or deleting the lines. The insertion of a line is made by entering the following fields :
the function code. This code makes reference to a basic function in the software. It is possible to use a selection window.
potentially an option. This option depends on the function involved.
a title that will be displayed in the menu to identify the function called.
Options associated with the functions
The functions for which an option can be entered are as follows :
MENU : this signifies that the menu line calls a sub-menu, where the code must be entered in the options column.
PRINT : this signifies that the menu line calls a report, whose code must be entered in the options columns. if the report code is not entered, the menu line makes it possible for the user to choose the report that when it is launched, by displaying the list of all the reports that the user has access to.
all the functions that correspond to the object management with transactions that can be parameterised (that is to say the majority of the movements). It is then possible to give as an argument the transaction code to be used ( this is not mandatory : if this is not done, there will be the choice of transaction (if a choice is possible) from amongst the different transactions for which the user is authorised.
all the functions that correspond to the standard enquiries that can be parameterised. It is then possible to give an argument for the enquiry screen code to be used (this is not mandatory : if this is not done, a default enquiry screen will be used) and it will then be possible to change the screen by selection (if a choice is possible) from amongst the different screens for which the user is authorised.
SYSTEM : this signifies that a system command is going to be launched either on the client or on the server according to the syntax used. The different syntaxes possible are detailed in the corresponding paragraph shown below. In this specific case, an additional window opens to allow the entry of the system command.
the ADPVAL function, which is used to modify the basis of the parameters in the software, can be called with an argument defining the chapter (for example SUP), or an argument defining the chapter and template for the parameter names in the form CHAPTER_TEMPLATE (for example SUP_USR*), or even a template without chapter (for example USR*).
Two functions used to navigate between the sub-menu levels are accessible from the lines in the grid (by right click). These functions are the following :
Origin is used to descend a level (from a menu line) to pass to sub-menu modification.
Destination is used to go up a level in the menu structure.
Close
Fields
The following fields are present on this tab :
Block number 1
| This code identifies the created records in a unique manner. |
|
|
Block number 2
| The type of profile is a local menu that is used to give a category to the users, with a goal of limiting, if necessary, the simultaneous number of connections by category. This is made by means of the USR1, USR2, and USR3 parameters. |
| Used to define a quantity of additional memory allocated to the Adonix process executing the functions for the user connected under the profile menu. |
| Specify the code of the first menu that will be viewed at the time of user connection. This menu must be present in the grid below. |
|
|
|
|
|
| ||
| Indicate here the code of a function that will be executed when the user carries out the corresponding choice. Some functions accept an additional parameter, namely:
| ||
| For some functions, a supplementary argument can be specified. The table below draws up a list of the most frequent cases :
When the supplementary argument is not mandatory, it is selected or entered when starting the function, depending on the cases. | ||
| Define the title appearing in a menu line. |
Close
Functions accessed by right click on the grid
Other conditions
System command syntax
The system orders must be written according to the server type that is used. The server on which the command is executed is by default the process server. warning, the length of the system command is limited to 40 characters, which may lead to the use of an intermediary script. For example :
under UNIX, an example of a system command is /u/mine/my_command.sh
under NT, an example of a system command is C:\prog\command.bat
It is also possible to execute commands on another server accessible from the network, to which a connection service for the software operates with the same service number as the connection service of the current folder. In this case, the command to be launched is the following : server@command, server being the name of the server network concerned and command the command to be launched.
Finally, it is possible to use this last syntax with # as the server name, which defines by convention the client workstation. Thus to launch Word(TM) on a client workstation from an Adonix menu, a command file can be created called for exampleword.bat in C :, which will contain "C:\Program Files\Microsoft Office\Office\Winword.exe" (this last command exceeds 40 characters), and then give as an argument to the system command the line : #@C:\word.bat
Reports
By default, the following reports are associated to the function :
PROFMEN : Menu profile
This can be changed by a different setup.
Menu Bar
This button is used to transfer the menu profile to another folder accessible from the same server. |
Menu Bar
Validation / Menu validation
Documentation / Paragraphs
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.
Documentation / Links
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.
Documentation / Generation
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 generation of the documentation structure from the dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
- the generation of the documentation from the previous tables.
- the generation of the field documentation.
The range suggested by default takes into account the current record but it can be modified upon launch.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Non existent function code
This message signifies that a function code has been entered that is not declared in the functions table.
Menu already used
This warning (which is not blocking) signifies that a menu has already been referenced elsewhere (in other words, that the same menu is accessible by two different paths.
Menu already used in the access path
This message signifies that an attempt is made to insert in the call menu a menu located above in the hierarchy (which may provoke a loop in the menus). Here it is a blocking error.