Functions

Indicate the function code. The codes starting with "GES" are automatically generated by the object management supervisor.

When a function is created, it is indispensable to reference it in a menu, in order that this function can be called. The menus are parameterized by user, but a reference user exists, called ADMIN, but whose name is modifiable using the parameter ADMUSR.. These menus contain all the functions and can serve as a template during the creation of the menus. Therefore a reference menu for where the function is found is defined here.

The top menu in the standard menu tree structure is called GENE ; all functions must be referenced, whether in this menu GENE, or in another menu itself accessible via the menu GENE. The following constrains exist :

  it is not possible to have more than 30 choices in a menu.

  it is not possible to exceed 4 levels of sub-menus.

The menu title is the text (translatable) that will actually appear in the user menu to describe the function.

Indicate the rank where the function will appear in the menu above. In a menu the functions are sorted by rank in ascending order.

Specify the module that uses this function. If the function is using several modules, indicate "supervisor".

If this field is not assigned, the function will always be active and will generate a menu line for the user ADMIN. If this field corresponds to an inactive activity code, the function will not be active. If this field starts with an X, Y or Z, the folder validation does not update the function.

Indicate the type of function : process or sub-menu.

The process, if it is entered, corresponds to :

• either the name of the process to be executed on the condition that it does not open the window.
• or to the name of the menu.

For a function of the process type, the method recommended is to enter the action, if it is not of the type "miscellaneous process", rather than enter the process directly.

When the function is linked to an object, the field "Object access type" is automatically set. It is used to propose the following 3 codes in the functional authorizations : C (Creation), M (Modification), S (Deletion).
For any object, it will be possible to restrict the functional authorizations rights, by not authorizing the creation and/or modification and/or the deletion.

When the "site authorization" field is set, it allows the detailing of the functional authorizations by site or group of sites.

Note: This setting is not available for GESFCY.

This check box is used to make the function executable even if the folder has been set to the "mono-module" ; that is to say it does not authorize any function or the module. A folder is set to mono-module by an exclusive function.

These two fields are used to define the name of the two report codes that can be called by the functions Print file and List file. These codes being stored in the following varables :GREPORT1 and GREPORT2. In the standard way, the Print function relates to the current record (the function is not in principal available if there is no current record), whilst the List function is available in all cases. In the case of a function linked to the object, the supervisor manages these buttons (activation, de-activation, execution). For all the other functions, the developer in the function is assumed to manage the call to these two reports, as well as the activation.

Setting autorizations, around this function, for the "Navigation/Go to the gunction" menu:

 Autorized: this function can be accessed via the navigation.

 Forbidden to this fonction : this function cannot be reached via navigation if, for instance, a calling context is necessary.

 Forbidden from this function: The navigation is forbidden from this function when, for instance, it is necessary to protect the current context.

 Forbidden in all cases: It is forbidden to access this function via navigation and to access navigation via this function.

This table is used to define the options codes (up to a maximum of 20) in the form of a letter and associated comment. The lower case letters are reserved for specific/custom developments. On each functional authorization, this letter can be selected or not in order to add the options to the function. On the execution of a function, the supervisor loads the global variable GUSRAUZ(n) with the authorized option codes; n is the index that indicates the breakdown of the authorizations by site. The developer can link a section of their process with the presence or not of an option code in this variable.

This field makes it possible to define a function that will govern the access to this parameter. This makes it possible to avoid access authorization errors. For example : The button 'Validation' for the function GESBIC 'BP customer invoices' corresponds to the function BPCVAL. It is therefore possible to control access to the button according to the authorizations defined in the function BPCVAL.

This activity code governs the presence or not, of the option in the function.

This table is used to define a list of global variables that must be assigned in order to give a calling process a more specific context. These variables are initialized by the function, when the process is called from the menu.

Specify the value to be assigned to the variable of the same line. Be careful to respect its type (no control is carried out).

This activity code makes it possible to protect the variable during a folder update.

The action that will be executed at the launch of the function is defined here. The action must exist in the dictionary and must not be of the type "miscellaneous process". If this is the case, the unction must not call the function but must call the process directly ; to do this the name of the process must be entered in the first tab.

possibility to enter the values for the action parameters.