This function is used to associate to a profile code (itself associated with users):

  • a menu tree structure to access the various functions of the software
  • two additional setups

It is important to note that a menu profile code does not define access rights, but only a browsing tree structure. The latter are defined by the function profile code as well as by some additional setups of the user record.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

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 setups USR1, USR2, and USR3 (this list of setups can be completed with the custom/specific setups USRn, n being the rank of the profile type in the local menu).
  • the second characteristic concerns an additional memory value, expressed in Kbytes, associated with the engine that executes the user processes having the corresponding menu profile. This setup, 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

Some functions accept an additional setup, namely:

  • MENU : this signifies that the menu line calls a sub-menu, where the code must be entered in the options column.
  • AIMP: 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 set up (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 authorized.
  • all the functions that correspond to the parameterizable standard inquiries. It is then possible to give an argument for the inquiry screen code to be used (this is not mandatory : if this is not done, a default inquiry 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 authorized.
  • SYSTEME (execution of a system order): The order is given in the form of a command line, entered in a specific window and whose syntax is specified in an annex documentation.
  • AMIEXE (execution of a system transaction): The transaction code can be specified.
  • the ADPVAL function, which is used to modify the basis of the setups in the software, can be called with an argument defining the chapter (for instance SUP), or an argument defining the chapter and a template of setup names in the form CHAPITER_TEMPLATE (for instance SUP_USR*), or even a template without chapter (for instance 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 move to sub-menu modification.
  • Destination is used to go up a level in the menu structure.

Block number 1

Menu profile (field CODPRF)

This code identifies the current record in a unique way.
Description (field INTPRF)

Block number 2

Profile type (field TYPPRF)

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.

Additional memory (field MEM)

Used to define a quantity of additional memory allocated to the Adonix process executing the functions for the user connected under the profile menu.
Start menu (field MENDEP)

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.
Menu hierarchy (field MENUSA)

Table number 2

Menu detail (field LMENU)

Table number 1

No. (field NUMLIS)
Function (field FONCTIONS)

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:

  • MENU : this signifies that the menu line calls a sub-menu, where the code must be entered in the options column.
  • AIMP: 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 parameterizable standard inquiries. 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.
  • SYSTEME (execution of a system order): The order is given in the form of a command line, entetered in a specific window and whose syntax is specified in an annex ocumentation.
  • AMIEXE (execution of a system transaction): The transaction code can be specified.
  • 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 instance SUP), or an argument defining the chapter and a template of parameter names in the form CHAPITER_TEMPLATE (for instance SUP_USR*), or even a template without chapter (for instance USR*).
Options (field CODMENS)

For some functions, a supplementary argument can be specified. The table below draws up a list of the most frequent cases :

Function code

Definition

Supplementary argument

Mandatory 

MENU

Software menu

Menu code

Yes

AIMP

Printing

Report code

No

AMIEXE

System transactions

Transaction code

No

BATCHEXP

Exports

Template code

No

BATCHIMP

Imports

Template code

No

CONS*

Inquiries

Inquiry screens

No

EXEALH

Requester

Code for the request

No

All transaction-managed functions

Transaction code

No

GIMPOBJ

Imports

Template code

No

SYSTEM

Execution of a system order

Order to be executed

No

When the supplementary argument is not mandatory, it is selected or entered when starting the function, depending on the cases.
Description (field ZLIBMENUS)
Source

Used to display the original menu referencing the menu being modified.

Destination

This is used to display the menu of the current line in order to modify the characteristics.

Other conditions

System order 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 instance:

*   under UNIX, a system command will be written the following way: /u/mine/my_command.sh

*    under NT, a system command will be written the following way: 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, "server" is the name of the specific server, and command is the command to launch.

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 a menu, a command file, called for instance word.bat can be created in C:, which will contain "C:\Program Files\Microsoft Office\Office\Winword.exe"  (this last command exceeds 40 characters), and then give the following line as an argument to the system command: ../FCT/mailto:#@C:/word.bat

Reports

By default, the following reports are associated with this function :

  PROFMEN : Menu profile

This can be changed using a different setup.

Specific Buttons

Copy

This button is used to transfer the menu profile to another folder accessible from the server where the current folder is located.

Documentation / Paragraphs

This menu item allows access to the documentation management on the first paragraph of the documentation (if there is one) associated with the current record.

Documentation / Links

This menu item allows access to link management. It is used to define the links between the current record and other records (for example, the links between functions and parameters). These links are specific to the documentation and are used to load the generation of documentation structures.

Documentation / Generation

This menu item launches a documentation generation. You can also launch it from the Generation button at the bottom of the screen.

You can launch three types of generation one by one or simultaneously

  • The generation of the documentation structure from the dictionary (ADOCUMENT, ADOCBLB, and ADOCCLB tables)
  • 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 you can modify it at launch time.

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.

Tables used

SEEREFERTTO Refer to documentation Implementation