Development > Script dictionary > Scripts > Entry points 

A group of actions is planned in the standard templates, to make it possible to call a specific/custom process. In addition, when the requirement is expressed, the entry points are created in the standard, to allow the calling of a specific/custom process.

Each entry point is documented in a record, in order to define the context of the call to the specific/custom process.

This table allows the functioning of the entry points : the specific/custom process is identified in which will be written one or more entry points called from the standard process.

The entry points table is shipped empty by Adonix. It must therefore be loaded as and when required.   

For an entry point, the specific/custom process must follow the writing rules identical to the action ; it must start by the sub-programme $ACTION, in which will be tested the different values possible for the ACTION variable. This variable contains the name of the entry points.

When "..."



SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen


This screen makes it possible to reference the specific processes in which are developed the called actions of the standard process. These processes make it possible to specifically adapt the standard program. The specific process must start with the label $ACTION within which the action is declared; it conserves the environment of the standard program.




The following fields are present on this tab :


  • Type (field TYP)


  • Standard script (field TRTSTD)

Standard process, for which a specific/custom is being added.


  • Title (field LIBTRT)


  • Specific script (field TRTSPE)

Specific/custom process, used to add to or to replace certain actions in the standard process. It will be noted that the specific/custom developments linked to 2 entry points in a standard process, must be written in a single specific/custom process.

  • 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.

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.

  • Order (field RNG)


  • Setup (field TRTPAR)

This field is used to identify the other specific/custom processes attached to the principal process. It must be entered in the form PROG1~CODACT1;  PROG2~CODACT2;.... where PROGn is the name of the process and CODACTn an activity code. The specific/custom will analyze the values of this field in their principal specific/custom process in order to carryout the call to the other processes if necessary.



Error messages

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

Code already exists in line i

An attempt has been made to enter the same standard process twice in the grid.

Tables used

SEEREFERTTO Refer to documentation Implementation