This function is used to parameterize and personalize the inquiry screens across all of the application.

An inquiry presents itself in the following fashion:

  • The principal selection criteria in the header.
  • The additional criteria grouped together in the Criteria button at the bottom of the screen.
  • The grid containing the information in the inquiry.

An inquiry is defined by a code, which corresponds to the logical interrogation of the data. A type corresponds to a group of fields that can be viewed. Each inquiry type can have as many versions available as screen codes as required. Each screen code is therefore given the information that is required to be viewed amongst the list of possible fields : each line of the selected grid will correspond to an inquiry column, the order of appearance being defined by the rank entered.

It is also possible to define a graphical presentation for all or part of the numeric columns in the grids.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The inquiry screens are characterised by a type, which identifies the inquiry function concerned and a code for the screen itself. The left list is displayed in a "tree" form of the inquiry types, then the screen codes themselves.

When several screen codes exist for a give inquiry, the assignment of a default screen code can be defined by default either directly via the menu profile or by the rules linked to the application. If the screen code is protected by access code, it is necessary that the user has the execution rights for the access code in order to use it.

Entry screen

The information to be entered in the definition of the screen is of three types :

  • the general information (code, access code, number of lines)
  • the grid sorted with the fields to be presented (from the exhaustive list of possible fields)
  • the information related to a graphical presentation

Specific Buttons

Validation

It is used to validate the screen by generating the corresponding code. This validation is automatic on creation or modification; the button is thus only really useful when deleting a screen file on the application server, or in the case of a copy from one folder to another (the validation is not in this case carried out automatically in the target folder).