Objects

• Object code (field ABREV)

The object code is comprised of 1 to 3 alphanumeric characters. The Adonix reserved words are prohibited.

• Description (field ZLIBEL)

• Short description (field ZLIBSHO)

• Linked table (field NOMFIC)

Code for the principal table managed by the object.

• Data model (field MODELE)

• Module (field MODULE)

Indicate the application module to which the record is attached (and the attached code if necessary). The records used by several modules are classified in one of the modules common data or supervisor.

A development associated with a module (and the corresponding code) can only be used if the module is active in the current folder.

• Parameter title (field ZLIBPAR)

• Activity code (field CODACT)

If it is defined, an activity code attached to an object is used to make it optional.

• Site field (field ZSITE)

• Access code field (field ZACC)

• Management type (field TYPGES)

This characteristic defines the manner in which the object manages the records in the table. The possible choices are Simple, In grid, Combined. A forth value equal to the Browser makes it possible to independently create the browsers that will then be integrated in a window.

  Simple. this is the most common type. It corresponds to the case where an entry in the principal table is managed in a record, a list of records being displayed in the left list. The object management screen obeys this logic itself (it is an object itself, its code is AOB), but numerous other examples exist : customers, invoices, postings, orders... are all simple objects.

  Grid. This corresponds to the case where the table, if sufficiently small, can be directly loaded in the lines of a single grid displayed in the screen. In this case, the left list no longer exists (it is of no use). The management of the section coding is carried out in this way.

  Combined. This corresponds to the case where a group of records are loaded in a grid, records where the key is made for N (N>1) sections, where the N-1 sections are fixed and the last section varies. Warning, this is not the case for the invoices (which have a key type document/line number), because in this case, the management of a simple object is carried out in the header and the loading of the lines is managed in the code associated with the object. An example of such an object is the management of technical records : for a control code, there is 1 to N lines present in a grid.

  Browser. This type is used to define the left lists that will then be attached to a window. The information to be entered in this object type is reduced to the information required to construct a left list.

• Menu (field MENU)

This field defines the menu code in which the management function for the object will be present for the user ADMIN.

• Row in menu (field RANG)

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

• Printing (field RPT1)

This print code defines the report(s) launched when the File / Print menu option. It should be noted that the report ranges can be entered from the current record : in fact, the File / Print choice is only accessible if a current record is displayed on the screen.

By default, when using these button, the software will attempt to print the reports whose names are given here. But a non-direction table exists that is used to redefine, from the internal code given here, one or more reports (e.g. the printing of the picking lists, and delivery advice notes in the shipments object).

• List (field RPT2)

This print code defines the report(s) launched when the File / List menu option. The File / Listchoice is always accessible and it is designed to be used to print general lists linked to the online tables.

By default, when using these button, the software will attempt to print the reports whose names are given here. But a non-direction table exists that is used to redefine, from the internal code given here, one or more reports (e.g. the printing of the picking lists, and delivery advice notes in the shipments object).

• Standard script (field TRTSTD)

Processes in which, it will be possible to write additional sub-programs for the management of the object for this function. One process is reserved for the standard development, the next for the verticals and the last for the custom/specific. Development help.

• Vertical script (field CTLSPV)

• Specific script (field TRTSPE)

Processes in which, it will be possible to write additional sub-programs for the management of the object for this function. One process is reserved for the standard development, the next for the verticals and the last for the custom/specific. Development help.

• Statistics (field STA)

This tick box allows the activation of the "Statistics" button in the object. This button is used to call the statistics interrogations where the first criteria are defined by the data linked to the principal table or to the tables linked to the object.

• Deferred deletion (field DELDEF)

The supervisor will authorize or not the deferred deletions in the principal table as well as the secondary tables managed by the object. This possibility is offered for the parameterized users on deletion confirmation. When this user deleted a record in the object, a confirmation window is displayed. The user can check the "deferred deletion" box in this window. The record will therefore remain present until the differed deletion utility is launched.

• Import (field IMPORT)

This field makes it possible to specify that the object can be imported by the function import-export.

• Lock in modification (field MLOCK)

Used to trigger the logical lock when going to modify a record, where as standard it is set to the display of the record. In order to use modification mode, it is necessary to click on the key.

• Option title (field ZOPTLIB)

• Code (field OPTCOD)

This grid is used to define the options for the management of the object. One option makes it possible to characterize the sub set of records identified by a condition (active customers, open accounts,...)

An option can be defined by :

• A key letter
• A title
• A logical condition
• An error message will be displayed if the object is not correspond to the option.

• Option condition (field OPTCND)

• Error message (field ZOPTERR)

• Index (field SELCLE)

This field is used to define an index for the principal file for the display in the left list and in the selection windows. If this field is empty, it is the first index in the table that is used.

• Sign (field SELORD)

This field is used to define the direction from moving through the principal table for the display in the left list and the selection windows for the object.

• Selection options (field SELOPT)

This field makes it possible to specify one or many options for the records present in the selection window.

• Hierarchical list (field SELTREE)

When the key chosen for the let list is composed of several parts, the list presents only the first part of the key initially. By double clicking on one of the values of the key there is the possibility to explore the sub-values of the key and thus through the number of levels of existing sub-keys. When all the key levels are explored, a record can be selected from the table.

An example of this functioning can be seen in the site management object : each site being attached to a company, the initial display is the list of companies and there is then the possibility to expand a company by double clicking it : the list of sites then appears and it is possible to select one of these.

if the box is not checked, it is a simple list.

• No. characters (field SELCAR)

Any field in a screen where the type is linked to a object has available a selection field accessible by right click or by.

This value is used to define the number of characters used to specify where the selection should start, as a function of what has been entered in the field before the selection. If this value is N, the selections starts from the first key where the first N characters are greater than or equal to the string entered. Indeed :

• If the value 2 is entered and if the string DEF is entered before opening the selection, the selection window will start the search from the first value of the key greater than or equal to DE (if keys starting with DEA exist, it is these that appear first in the window). If H has been entered, the selection will start with the first key greater than or equal to H.
• If this field has the value 0 and a string UVW is entered before opening the selection, the selection starts at A and is not limited.

• Table (field SELFIC)

The table in which the field to be displayed is located is entered here. This table is either the principal table or one of the tables defined as linked to the principal table in the object definition.

This field can be empty if a calculated expression is displayed.

• Field (field SELZON)

The fields present in the left list are entered here. They come from the table previously defined.

• Expression (field SELEXP)

When a column from the left list is evaluated, a calculated expression is defined here whose result is placed in the column. A data type is then required to format the field.

• Description (field ZSELINT)

• Type (field SELTYP)

This data type is used to forma the previous expression in the left list.

• Options (field SELSAI)

This information is used to format the data by the choice of option. The options depend on the data type (use the search window).

• Length (field SELLNG)

Possibility to indicate a length for an alphanumeric column constructed by an expression. If not entered, a length of 30 characters is used by default.

• Tables to open (field TABFIC)

Additional tables to the principal table managed by the object. These tables are opened then automatically closed on the execution of the object, under the abbreviation indicated otherwise under the dictionary abbreviation. The fields in these tables are accessible in the object.

In addition, the fields in these tables are used to define a left list column and the selection screens from the moment when the link expression is entered. It is possible to define the hierarchy links, on the condition that these tables are entered in the grid in the hierarchy order.

The link key must be unique. If it is not entered, the supervisor takes the primary key.

• Index (field TABCLE)

• Link expression (field TABLIEN)

• Abbreviation (field TABABR)

• Activity code (field TABACT)

• Table (field IMPTBL)

Specify all the tables that will be updated for the import. Then, for each table, the screen(s) are specified that it will generate. And finally, for each grid section, the variableat the bottom of the grid is specified when this information is used to load a detail table.

• Screen (field IMPMSK)

• Line field (field IMPTAB)

• Screens (field SCRNAM)

For WEB services, indicate the additional screens used in the object management from the button at the bottom of the screen or a menu.

• Abbreviations (field SCRABR)

• Views (field VUECOD)

These views are opened then automatically closed on the execution of the object, under the abbreviation indicated otherwise under the dictionary abbreviation. The fields in these views are accessible in the object.

• Abbreviation (field VUEABR)

• Activity code (field VUEACT)