Development >  Script dictionary >  Scripts >  Script dictionary  

Display all Hide all

This function is used to capitalize the processings in a dictionary. This makes it notably possible to apply an activity code on a processing. The processings, as well as every dictionary element, can thus be selected according to an entered activity code for automatic patch creation.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Fields

The following fields are present on this tab :

Block number 1

  • Script (field CODTRT)

Identifier on 12 characters.

  • Description (field DES)

Enter the description of the relevant record.

This long description is used as a title in screens and reports.

Characteristics

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

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.

Block number 3

  • Source processing delivered (field SRC)

Flag used during the industrialization of the product.
  • Internationalized (field INTERN)

Specifies that the names of the variables, labels, sub-programs and comments of the source code of the processing were written in English.

  • field SRCINT

Field reserved

Comments

  • field TEXTE

 

Info

  • field INFO

entries generated by the supervisor, concerning the source and the executable, if the application server is run on a UNIX system.

For the source, the owner is the creator of the process.

For the executable, the owner is the last to have compiled the process (during the compilation, the supervisor deletes the executable prior to recreating it).

Close

 

Specific Buttons

This processing is used to list in a grid (containing one line per process), the processes not identified in the process dictionary. This search selects the processes compiled in the current folder. The processes starting with one of the following letters W, X, Y and Z are not taken into account by this process, as well as the SUB, CNS and IMP processes for the objects, inquiries and imports starting with the letters X, Y Z.

The "Shipped sources" flag is set for the processes SUB*, CNS*, FUN* and IMP*.

There is then the possibility to intervene in this grid, to modify the process characteristics or to add or delete the process.

The button is used to automatically generate in the process dictionary, a record for each process listed in this grid.

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

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.

Close

This button is used to copy the process definition to another folder.

This processing is used enter in a grid (containing one line per processing), the processings to remove from the dictionary.

The button  is then used to delete all the processings entered in this grid.

Menu Bar

Options / Purge

Deletion of the record from the processing dictionary when the corresponding compiled processing (*.adx) does not exist in the TRT directory.

Options / Archive checking

Verification of the consistency between the archive index and the compiled processings (*.adx) in the TRT directory. A log file makes it possible to know:

  • The list of processings present in the archive index in the non compiled form (*.adx) in the TRT directory
  • The list of processings (*.adx) present in the TRT directory, but not in the archive index.

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 link management. It is used to define the links between the current record and other records (for instance the links between functions and parameters). 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 :

Process locked

The process is locked that the user wishes to copy.

Tables used

SEEREFERTTO Refer to documentation Implementation