Error messages

Certain database information is displayed in the form of a list with restricted choice. For instance, the Yes / No choice, round codes, report groups, etc., are available in the form of a table holding the limited choices of items available.

This type of data is called a local menu and the table used is identified by a module number. For all the fields in the database storing data of this type, the title row is stored in the corresponding table. Thus, if for instance in local menu number 1, composed of the choices No and Yes (in this order), what is actually sorted in the database is 1 for the value No, and 2 for the value Yes.

A large number of local menus is used in the software. As with all the miscellaneous tables, this system is used to avoid the creation of a large number of annex table, the description of these local menus being stored in a single table in the database : the APLSTD table. Furthermore, these local menus have the advantage of being translatable: indeed, as only the title row in the table is stored, it is only necessary to change the table to display or enter with another title translated into the appropriate language.

Warning, it is necessary to take care when modifying these tables, not to insert values but only to add values to the list of titles. Unless no data has yet been assigned to a given local menu, inserting a choice leads to titles being switched for data that has already been entered, because only the row number has been stored in the table. Thus if the choice Maybe is entered in the first row of the No / Yes table, all the fields in the database having been entered with the value Yes will be redisplayed with the value No, those entered with the value No taking the value Maybe ! The number of choices in a local menu is limited to 123.

Beyond the notion of local menu, some chapters in the table are used to store other messages, such as error messages. As a standard, when a specific message needs to be displayed to the user (for instance, a confirmation request, an error message, a comment in a log file, etc.), the message is stored in a chapter dedicated for that purpose, in order to make these messages translatable based on the connection language.

It is of course recommended to all the developers of specific functions to do do. In order to have easy access to the texts in the processes or in any calculation formula, the standard function mess is available to provide access to the messages. Indeed, Mess(NUM,CHAP,1) provides access, in the current connection language, to the message number NUM from the chapter CHAP.

In any case, each software with the adonix technology defines its own mapping for the chapters, by allocating number ranges to functional modules of each offer. The module assignment specific to the software involved can be found in the annex.

Prerequisites

See also Refer to documentation Implementation

Screen management

Entry screen

The entry is made by chapter in a single tab. A chapter can be a local menu or even a group of messages. On exiting this function, if at least one local menu has been modified, the system will automatically launch an update of the local menus in order to update sequential files, used as caches for the local workstations depending on the languages managed in the folder.

Identifier

Chapter (field LANCHP)

Define the number of the chapter that is to be parameterized.
Description (field TITCHP)

Title associated with the previous code.
Local menu (field MENLOCAL)

When this box is checked, the chapter is usable as a local menu and not simply as a list of messages.

Characteristics

Module (field MODULE)

[object Object]

Activity code (field CODACT)

An activity code is used to:

  • Make an element optional in the dictionary if the value associated with the activity code is null
  • Identify the specific/custom elements if they are marked with a code starting with X, Y, or Z
  • Size a maximum number of lines when the activity code marks elements from a grid

If the activity code is disabled:

  • The marked element will not be useable
  • The associated code will not be generated nor activated
Changeable (field AUZMOD)

This field is used to indicate if the local menu is modifiable by the user in a parameterization phase, directly in the menu Parameterization / General parameters.
Do not translate (field NONTRA)

Size

Length (field LONG)

This field makes it possible to specify the maximum text width in the different local menu choices.

Mini (field MINI)

This field makes it possible to indicate the minimum number of possible choices that the local menu must include.

Maxi (field MAXI)

This field makes it possible to indicate the maximum possible number of choices that the local menu include.

Grid List of values

Number (field LANNUM)

Define the message number in a chapter A local menu defines by this rank the value of the field corresponding to the title.
Code (field CODE)

Code on one character associated with the title.
Message (field LANMES)

Define the title associated with the message number in a chapter. It is this title that is displayed in a component of the type "rolling list" or "radio button" when the field is used as a local menu.

Reports

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

  PRTSCR : Screen print

  APLSTD : Local menus

This can be changed using a different setup.

Specific Buttons

This button is used to copy the record definition from or to another folder.

Block number 1

field OBJET
field CLES

Block number 2

From folder (field DOSORG)

Indicate the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix.
All folders (field TOUDOS)

This option is used to copy the record to all the folders defined in the dictionary (ADOSSIER table from the current solution).
To folder (field DOSDES)

Indicate the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix.