This function is used to create documentation links used in the documentation generator. These links complete the dictionary information in order to automates notably the annexes and the prerequisites of the documentation. An annex documentation specifies for each documentation type what links are available and what are the documentation paragraphs loading them.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The header section contains a documentation type an a corresponding code. The type is attached to a link grid.

Entry screen

Each line of the table represents a link used in the documentation generation.

Block number 1

Type of document (field TYP)

This type, defined in table 910, defines the documentation type for which links are being defined.

Module (field MODULE)

Select a module for the setup.

Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on the folder.
Code (field COD)

This code defines the code for the documentation to which the links are attached.

Activity code (field CODACT)

An activity code is used to:

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

If the activity code is disabled:

  • The marked element will not be useable
  • The associated code will not be generated nor activated

Grid Links

Line number (field NUM)
Type (field TYPLNK)

This type of link makes reference to miscellaneous table 913. According to the documentation type different links are authorised.

Key (field CLELNK)

The key for the link is linked to the type previously entered. For example, when the type ADP type (parameter) is used, this field is used to enter the parameter code or the name of a local variable. If the type ATB (table) is used, the code for a table in the database is used. In most cases, a selection window associated with the context opens so that a choice can be made from the possible codes. The list of possible links can be found in the documentation annex.
Description (field INTLNK)

Title associated with the previous code.

Specific Buttons

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

Block number 1

field OBJET
field CLES

Block number 2

From folder (field DOSORG)

Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.
All folders (field TOUDOS)

Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).
To folder (field DOSDES)

Use this field to define the folder to which the record will be copied. The possible syntaxes are described in the Dedicated appendix.