The activity codes offer the following possibilities:

  • to render active or inactive the elements in the dictionary (example: tables, index, tabs, screen sections or fields...). For example, the fact of setting an activity code as active or not gives the possibility to deactivate, in the screens, certain optional fields.
  • to affect the sizing of fields in the tables.
  • to make the sizing of fields and screen section open to parameterization.
  • identify the elements developed for the standard localizations : these elements are identifies by an activity code starting with K.
  • identify the elements developed as custom and vertical. When the activity code starts with X, Y or Z, the element is considered as non standard and is therefore not affected by a standard patch. To be more precise, a standard has been established from version 5 for the X3 software range :
    • The codes starting with X are reserved for the vertical developments
    • The codes starting with Y or Z are reserved for the custom developments.

The value of the activity codes is defined in folder management. Only the codes that are not dependent on another code are entered ; the others are deducted. For more detail and in particular to consult the naming rule for the codes see the field help "Dependence"

The changing of the activity code value requires a revalidation of the folder in order taken into account these structural elements.


SEEREFERTTO Refer to documentation Implementation

Screen management

This parameterization is carried out on a single tab.

Entry screen


The detailed characteristics of the activity code are described here.




The following fields are present on this tab :


The activity code identifies an option that can be of the type yes/no or can define a number of occurrences.

This option, which must be assigned at the folder creation, makes it possible to influence the screen structures of the software package and also possibly the database structure.

  • Title (field ZLIBACT)

This name makes it possible to explain the activity code use.


  • Active (field FLACT)

The fact of setting this field to Yes activates the tables, screens or the fields in the tables and the screens that belong to the option. Conversely, if the field is set to No, the screens, and the tables, or the fields that belong to it are no longer accessible and disappear.

  • 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. It is specified when the module linked to the screen is active in the folder.

  • Sequence (field RANG)

This field makes it possible to indicate the order in which the activity codes will be displayed in folder management. The activity codes depending on a formula are calculated in an ascending order for this number.

  • Type (field TYP)

This field is used to classify the activity codes in the tabs for the folder management.

  • Minimum dimension (field DIMFIL)

Certain fields in the tables can display their number of occurrences vary according to an activity code. Often the number of occurrences is the same for a given field between the table and the screen, but it sometimes happens that there is a requirement simply to hide the field on the screens whilst keeping the occurrences in the table.

In this case, it is possible to give a different value to this column compared to the precedent. This dimension generally corresponds to the dimension generated in the "Crystal Reports" reports.

  • Maximum dimension (field DIMMAX)

This value corresponds to a maximum dimension for variables managed in the processes.

  • Screen dimension (field DIME)

Define the number of occurrences used in the screens and also in the tables involved, remembering that for a table, a minimum number (and a maximum number) can exist, all of which will lead to the use of the following formula to size the tables


  • Dependency (field DEP)

When the value is not equal to No, this field is used to indicate that the value of an activity code has not been entered, but is automatically determined as a function of the value of the other activity codes. The possible values are as follows :

  • Inverse : The activity code takes the inverse value of the activity code entered ; if it is active if the corresponding activity code is inactive and inactive if it is active.
  • Dimensionally : the activity code is then composed of a root followed by a number M (1 to 9) and if it is associated with an activity code that can take the numeric values 1 to N. The activity code is active if the value of the associated code is greater than or equal to M; if not, it is inactive.

Looking at the example of the code ANA, associated by the dimension links to the codes AX1 to AX9. If ANA is set to 5, the codes AX1 to AX5 will be active, the codes AX6 to AX9 will be inactive.

  • Formula : used to calculate the value of an activity code as a function of an entry formula. This calculated expression can include constants, functions and variables in the form of other activity codes. These activity codes can be the entered codes or perviously calculated codes (the order of the calculation of the activity codes depending on the earlier codes is defined by the rank). An activity code not acting on a dimension is set to 1 if its is active and 0 if it is inactive.

For example, if the formula given for the XXX is max(XAA,XAB), XXX will be active if one of the two activity codes XAA or XAB is active. If these codes act on a dimension, the dimension obtained will be the maximum of the two dimensions.


  • Formula (field ACTFOR)

When the activity code depends on a formula, the formula to be evaluated to obtain the activity code value is defined here. This formula can be :

  • a logical formula (if it is true, the activity code will be active, if not inactive).
  • a numeric formula returning a positive integer value (for the activity codes acting on a dimension).




By default, the following reports are associated to the function :

 LISACT : List of activity codes

This can be changed by a different setup.

Specific Buttons

The following fields are present on the window opened through this button :

Block number 1

  • field OBJET


  • field CLES


Block number 2

  • From folder (field DOSORG)

This field is used to define 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)

This field used to define the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix.


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

Menu Bar

Documentation / Paragraphs

This function is used to access the documentation management on the first paragraph of the documentation (if there is one) associated to the current record.

Documentation / Links

This function is used to access the links management. It is used to define the links between the current and other records (for example the links between functions and setups). These links are specific to the documentation and are used to load the generation of documentation structures.

Documentation / Generation

This menu is used to launch a documentation generation. The generation can also be launched from the [Generation] button at the bottom of the window.

Three types of generation can be launched one by one or simultaneously:

  • the generation of the documentation structure from the dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
  • the generation of the documentation from the previous tables.
  • the generation of the field documentation.

The range suggested by default takes into account the current record but it can be modified upon launch.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Activity code dependant on xxx

The activity code has been declared as dependent with respect to another activity code that is itself dependent.

Error in the evaluation of the formula

The formula entered does not respect the Adonix standards.

Tables used

SEEREFERTTO Refer to documentation Implementation