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

$ACTION
Case ACTION
When "..."
...
Endcase
Return

 

Prerequisite

Refer to documentation on Implementation

Entry point management

Entry point definition

This function 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.

Grid

Type (TYP)
Standard script (TRTSTD)

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

Object (OBJ)
Description (LIBTRT)
Specific script (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 (MODULE)

Select a module for the setup.

Use this field to specify if the entry point has to be created in the folder database. This is the case when the module linked to the entry point is active on the folder.
Activity (CODACT)

An activity code is used to:

  • Make the entry point optional if the value associated with the activity code is null
  • Identify specific/custom entry points if they are marked with a code starting with X, Y, or Z

If the activity code is disabled, the entry point will not be called or processed.
Order (RNG)

Defines the execution order when multiple specific/custom implementations are attached to the same standard script. Entry points are called in ascending order.
Setup (TRTPAR)

In a V12 environment, you should leave this field blank. Each vertical or customization uses its own separate entry point implementation script, and the execution order between multiple implementations is controlled by the Order field.

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

Refer to documentation on Implementation