Development > Script dictionary > Scripts > Subprograms 

This function is used to capitalize on the information related to the reusable sub-programmes and functions.

It is purely a knowledge base. This is also used to make a sub-program accessible during the generation of the web services.



SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen





The following fields are present on this tab :

Block number 1

  • File (field PRG)

Process code. It must be used in the process dictionary.

  • Subprograms (field SUBPRG)

sub-program or function considered as re-usable and as a result to be capitalized on in this dictionary.

  • Title (field ZINTIT)

Descriptive title for the sub-program or the function.

Must be clearer and more precise to then facilitate the searches.


An activity code is used to:

  • make optional an element 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.

In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated.

  • Module (field MODULE)

Whether the module is active or not has no impact on the execution of the sub-program.

  • Type (field TYPASU)
  • field WA


  • Web services (field WEBS)

Used to specify that this sub-program or function can be generated for the web services. In fact, no process is shipped that can be directly used for the web services. However, a services web generationfunction is available for the objects and sub-programs identified as being suitable for generation.

  • field PUBNAM


Block number 3

  • Function (field FONCTION)

Check box that is used to make the distinction between the functions (called by the instruction Func ) and the sub-programs (called by the instruction Call.)

  • Argument type (field TYPFCT)


  • field TEXTE

Text loading the PRE "presentation" paragraph, in the record help. In the documentation management, the record help is identified by :

  • documentation type = ASU
  • documentation code = sub-program_process

Table Parameter definition

  • No. (field NUMLIG2)


  • Code (field PARAM)

Each parameter is identified with a 10 character code (uppercase and numbers). There is no dictionary for these parameters.

  • Title (field ZINTITPAR)

Parameter title for the sub-program or the function. Must be clearer and more precise to facilitate understanding.

  • Type (field TYPPAR)

Nature of the parameter :

  • Char : Character string
  • Integer : Integer number
  • Decimal : Decimal number
  • Date : date
  • Title : Local menu
  • Clob : text
  • Blob : image


  • Dim. (field DIME)

Dimension of the parameter

  • Argument type (field ADRVAL)

It indicates how the parameter is passed.

          by address ( a variable is necessary to pass the parameter. On exiting the sub-program, the value of any modified parameter is returned to the calling process).

          by value ( the parameter is passed by a variable or by a constant. On exiting the sub-program, the value of the parameter even if it is modified is not returned to the calling process).



Functions accessed by right click on the grid

Parameter Definitions

Button that is used to update the parameters grid following the analysis of the sub-program. The fields loaded automatically are : the parameter code, the type and the argument type. Then it is necessary to complete this grid by entering the parameter title and dimension.




Specific Buttons

This button is used to copy the sub-program definition to another folder.

This button is active in the sub-programs authorized in Web services. It is only used for the current sub-program in web services.

Menu Bar

Option / Verification

The Coherence verification process for the parameters grid with the sub-program. The number of parameters with errors is then displayed if any exist.

Option / Global verification

The Coherence verification process for the parameters grid with all the sub-programs. A log file is generated at the end of the verification process.

Option / Context of formula assistant

This menu used to access by tunnel to the function "formula assistant context".

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 :

Non-existent process

Process does not exist in the current folder or in one of the parent folders.

Reserved code

The entered process code is a code reserved for Adonix, and it therefore cannot be used.

Tables used

SEEREFERTTO Refer to documentation Implementation