Development > Script dictionary > Scripts > Script dictionary 

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)

    [object Object]

    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

     

    Grid 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)

    Indicate the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

    • All folders (field TOUDOS)

    This option is used to copy the record to all the folders defined in the dictionary (ADOSSIER table from the current solution).

    • To folder (field DOSDES)

    Indicate the folder in which the record is going 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 choice of menu allows to zoom to the documentation management, on the first documentation paragraph (if it exists) related to the current record.

    Documentation / Links

    This choice of menu allows to zoom on the dictionary link management function. This function allows to establish links between the current record and other records (for example links between functions and parameters). These links, dedicated for documentation purpose, allows the generation of documentation structure.

    Documentation / Generation

    This choice of menu allows to generate the documentation. Three types of generation can be separately or simultaneously started :

    • the generation of the structure of documentation from dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
    • the generation of the documentation itself from the previous table (they have been normally completed after the first generation).
    • the field help documentation generation.

    The ranges and parameter proposed by default are defaulted according ti the current record, but they can be changed during the execution.

    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