Setup > Users > Menu profile 

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

SEEWARNING A menu profile code does not define access rights but only a navigation tree structure.The latter are defined by thefunction profile code as well as by some additional parameters of the user record.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

The entry of the menu profile is carried out on a single tab. There are two specific characteristics:

  • The profile type defined by local menu 926, which contains 3 default values. This type of profile is used to limit the number of users connected simultaneously under a given profile type. This is carried out through the use of parameters USR1, USR2, and USR3 (note that this list of parameters can be completed with the USRn custom/specific parameters, 'n' being the rank of the profile type in the local menu).
  • The additional memory value, expressed in Kbytes, associated with the engine instance that executes the user processes which have the corresponding menu profile. This parameter, defined globally for a given folder by the Memory field in folder management, can therefore be modified for users who launch functions particularly heavy in terms of consumption.

The graphical representation

The tree structure of the current menu (by default, the first one when opening an existing profile).

The grid of menu codes

Folder and function detail

Create a menu profile

When creating a new menu profile, the Start Menu can be accessed. It is thus possible to select by default the name of one of the standard menus defined for the super user (ADMIN by default).

  • if GENE has been selected as the start menu (default value suggested upon 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 tree structure.

Modify a menu profile

Upon menu profile modification, it is possible to delete and/or add menus and functions, but also to move them so to position them in the requested order.

When in entry mode in the grid, it is possible to modify the menus by simply inserting or cancelling the lines. To insert a line, the following fields have to be entered:

  • the function code. This code refers to a basic function of the software. It is possible to use a selection window.
  • a potential 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 parameter, namely:

  • MENU: this means that the menu line calls a sub-menu in which the code must be entered in the option column.
  • AIMP: this means that the menu line calls a report with a code that must be entered in the option column. If the report code is not entered, the menu line make it possible for the user to choose the report to launch, by displaying the list of all reports 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, it will be possible to choose the transaction (if a choice is available) amongst the different transactions for which the user is authorized.
  • all the functions that correspond to the standard inquiries that can be set up. It is then possible to give as an argument the inquiry screen 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 choosing (if a choice is available) from amongst the different screens for which the user is authorized.
  • The order is given in the form of a command line, entered in a specific window. Its syntax is specified in an attached 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 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 CHAPTER_TEMPLATE (for instance SUP_USR*), or even a template without chapter (for instance USR*).
  • the GESADI function (miscellaneous table management), makes it possible to give a table number, a list of table numbers separated by a comma, and also table number intervals (ranges are separated by a dash), or a combination of all this. For instance, 1-5,8,25-27 means one table number is between 1 and 5 or equal to 8, or between 25 and 27.

Close

 

Fields

The following fields are present on this tab :

Block number 1

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)

 

Close

 

Action icon

Add a menu

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

Add a menu

Used to display the menu of the current line in order to modify the characteristics.

Zoom

 

Close

 

Reports

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

 PROFMEN : Menu profile

This can be changed using a different setup.

Specific Buttons

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

Menu bar

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 means that the function code that has been entered is not declared in the functions table.

Menu already used

This warning (which is not blocking) means 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 means that an attempt is made to insert in the call menu a menu located above it in the hierarchy (which may generate a loop in the menus). In this case the error is blocking.

Tables used

SEEREFERTTO Refer to documentation Implementation