Data Types

• Type code (field CODTYP)

• Description (field ZINTITTYP)

• Activity code (field CODACT)

The validation of the ADONIX folder does not update the data types where the activity code begins with X Y or Z.

• Module (field MODULE)

Module belonging to the setup. This field is used to specify whether the screen has to be created in the folder database or not. It is specified when the module linked to the screen is active in the folder.

• Internal type (field TYPTYP)

Used to indicate the internal type of the data type. The possible types are:

• Alphanumeric: character string with a maximum length of 255 characters, where the length can be given in the corresponding section. If the length is not given, it will be given by the length of the field at the time of using the type.
• Local menu: integer between 1 and 255.
• Short integer: integers between -32768 and 32767.
• Long integer: Integers between -2^31 et +2^31-1.
• Decimal: This is a numeric field with up to 32 significant figures, whose length is given in the form N.M (N being the number of figures before the decimal point and M being the number of figures after). This length can be given directly at the level of the type or in the length field defined at the level of the field that will use this type. According to the database, this type of field can be stored in the floating or fixed form in the database. In the first case, which corresponds to Oracle: in this case, what counts, when a N.M format is defined is in reality the total precision of the storage – N+M – . The second case corresponds to SQLServer: the number of positions before and after the decimal point must be clearly defined. The format field (which can be variable) will then define more precisely the distribution of the figures between the whole number section and the decimal section.
• Date: this is the date comprised between the 1st January 1600 and 31st December 9999 (remembering that a null date symbolised by [0/0/0] exists).
• Blob: it is used to store and manage the images.
• Clob: it is used to store in the database variable length texts with the format "rtf" or "txt" and to manage them.

For the blobs as with the clobs, it is necessary to enter the length that will be maximum storage length. The coding is as follows:

  Floating and Double are the types that will not be recommended for use (formats linked to the machine).

• Length (field LNGTYP)

Used to indicate if necessary, the length of the character strings or the numbers. If this is 0 the length will be entered for each variable of this type.

• Local menu no. (field NOLIB)

Local menu number. If this is 0 it will be entered for each variable of this type.

• Adonix format (field FORTYP)

Used to indicate the "adonix" format of the data type.  This format must be coherent with the internal type. The format must conform to the Adonix syntax. Only the part situated to the right of the ":" should figure in this field. Ex: 10X , 3A2B. The detail of existing syntaxes is given in the corresponding documentation.

For a variable format, it should be preceded by "=". Ex: =[F:DEV]FM92

A good example of this type of variable format can be viewed with the MD1 to MD4 types. These formats are used for the amounts expressed in a currency. For MD1, the format =GDEVFMT. This global variable is loaded in the INIDEV action declared in this same data type.

• Options (field OPTION)

These options are realized by characters that can be concatenated when several options are required. It is possible to choose these options thanks to a selection window. A detailed description for all the possible options is available.

• Linked object (field OBJLIEN)

Used to indicate if necessary, the object associated with the data type. The linked table managed by the object is displayed.

The presence of an object code automatically starts:

• The existence control
• The selection and advanced selection windows
• The possibility of a tunnel to the object management
• The possibility to display the current entry properties of the object.

• Linked table (field FICLIEN)

• Grid format (field OPTTAB)

Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

• Parameter : represents the parameter code to enter in the screen management for the data type.
• Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.

• Parameter (field PARTAB)

• field W1

• Variable (field VARTAB)

Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

• Parameter : represents the parameter code to enter in the screen management for the data type.
• Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.

• Default value (field VALDEF)

This field allows you to enter a calculation formula to assign a default value to fields of this type

An example can be seen in the CRY type, which defines the country code : the GPAYS variable, which defines the local country, is proposed as the default value for all the fields of this type. This default value is automatically proposed in the screen fields using this type of data. However, if a field using this data type has its own default value in the screen, it's this that will be used; in this case, the default value for the data type is ignored.

• Type (field ACTTYP)

This grid is used to declare the actions catalogued in the actions dictionary. The objective is that for all fields having this data type, the actions defined here will be systematically executed.

If a single action is defined is defined for both the data type and the screen field, the actions will be executed consecutively and in the following order : it is the data type then the field. There is a particular case for the "selection" and "button" actions, for which only the screen field action will be executed.

This grid makes it possible to define the particular actions associated with the field. The possible action types are :

• Before-field : Action before all entry or display of the field. It can be used, for example, to define the format of the field.
• Init_button : used to define the button names in the contextual contextual.
• Init : Used to initialize a field.
• Before_entry : Action carried out before each entry. For example it can be used to position mkstat and so not enter it.
• Control : Makes it possible to test the validity of the field.
• After-field : Carried out after the control if this is valid. Makes it possible for example to assign or to display other fields.
• After-modif : Ditto but is not started unless the field has been modified.
• Selection : Started by the F12 key.
• Button 1 : Triggered by the F9 key (reserved for the tunnels)
• Button 2 to 20 : The F4 key makes it possible to have a list of contextual menus.
• Before_line : Uniquely for the scrolling menus, making it possible to so something each time line modification is started.
• After_line : Uniquely for the scrolling grids, making it possible to do something after each line entry.
• Click : Only for the icon fields

• Code (field ACTION)

Indicate the actions to be carried out in a systematic manner on the type of data.
The actions STD, SPE or SPV that are linked to a particular function will not be entered at this level.
It is possible to enter several actions for the same action type except for the "button" or "icon" or "selection" actions

• Execution (field EXEACT)

This field is used to define the context of the action execution :

• Interactive : on-line entry.
• Import / Web service : loading of the record web service or import mode. The execution of the actions on the fields is carried out when all the fields are entered.
• Always : in all cases.

• Type (field TYPSELSYR)

• Content type (field TYPPROSYR)

• Description (field PROTYP)

• Supervisor mgmt (field SUPFLG)

• Special format (field FMTPROSYR)

• Class (field CODCLA)

• field DEFREPDES

• field DEFREPMOB

• field DEFREPTAB

• Type (field TYPRUL)

• Script (field TRTRUL)

• Sub-program (field PRGRUL)

• Sequence (field ORDRUL)

• Activity code (field ACTRUL)

• Active (field ENARUL)

• Code (field PARCOD)

• Description (field ZPARTIT)

• Key (field PARCLE)

• Type (field PARTYP)

• Class (field PARCLA)

• Dim. (field PARDIM)

• Method (field PARMOD)