Global variable
This function is used to capitalize a set of global variables defined in the application and to generate automatically the declaration (or even to initialize it if it is planned so in the record) in the sub-program DEFVAR of the processing specified in the record. It is never possible to add processing lines in the generated processings.
This is a delicate function since it intervenes in the processing variable declaration. It is essentially designed for developers and should not under any circumstances be left in the hands of unauthorized users. It is strongly advised not to modify the standard or when doing it at all, do it on purpose.
When checked, the "public" checkbox indicates that the global variable can be reused, notably by the specific. The documentation linked to this variable is available.
The global variables used in the product are not all declared in this dictionary. It is necessary to identify:
- those allocated to a setup
- those going beyond a processing.
For the variables that are not in the dictionary, they should be declared directly in the functional processing.
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
A single screen is used to write the variable, specify it format, its size and if needed to setup its initialization.
Block number 1
Variable code (field CODVAR) |
The following standard is used to name the global variable :
This variable belongs to the class [V]. |
Description (field ZINTIT) |
Characteristics
Activity code (field CODACT) |
An activity code is used to:
If the activity code is disabled:
|
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. |
Public (field PUBFLG) |
This flag indicates that this element is published. It can therefore be re-used by the custom/specific. An associated documentation is available. |
Description
field TEXTE |
This text field is used to display the comments relative to the current record. |
Format
Data type (field CODTYP) |
Defined here is the data type of the global variable. If the data type is the alphanumeric type and defined with a length, the global variable is then generated with a length defined by GLONxxx (xxx=data type). The length is mandatory if the data type indicated in the record is of the type internal alphanumeric, clob or blob and does not have a length entered. On the other hand, the length is not entered where the data type is of an internal type other than alphanumeric, clob and blob. |
Internal type (field TYPTYP) |
Field displayed with the value coming from the data type. |
Length (field LNGTYP) |
The length is mandatory if the data type indicated in the record is of the type internal alphanumeric, clob or blob and does not have a length entered. On the other hand, the length is not entered where the data type is of an internal type other than alphanumeric, clob and blob. |
Sizing formulas
Formula (field FORDIM0) |
Possibly to define the variables of one or two dimensions, the first line starting with 0 by default, but according to the parameterization can start with 1. Used to define a value by means of a calculated expression can contain constants and variables. |
From 1 (field FORDEB0) |
Formula (field FORDIM1) |
From 1 (field FORDEB1) |
Initialization
Parameter (field PARAM) |
Used to link a variable to a parameter, in order to automatically recover the value of the parameter in this global variable during the connection to the folder.
|
field DES1 |
Formula (field FORINI) |
Field that is used to initialize the field. Generation of the global variable loading in the subprog DEFAR for the process named in the record. For the standard, in order to conserve a homogeneity, it is recommended to no initialize the variable in the dictionary except for the variable used in the declaration of another variable. The initialization will be made in one of the processes GLOBxxx (xxx=module). Used to define a value by means of a calculated expression can contain constants and variables. |
Initial processing (field TRTINI) |
Generation
Script (field TRTSTD) |
Process in which the variable will be declared. Must have been created in the process dictionary. Must be named WWAGLOBxxx. Even though it can be assigned to new processes, the standard is limited to the available list. It is advised that or specific/custom, to generate their own processes. Two processes exist reserved for the global variables associated with a parameter :
|
field TRTINTIT |
Sequence (field RANG) |
Rank for the declaration and initialization of the variable in the process named in this record. This information is of importance, when a variable serves to size or initialize a second variable. |
Specific Buttons
Save
The global variables declared by the standard are protected. Some fields only can be modified. Block number 1
Block number 2
|
It is used to create the record in the global variable table, but also to generate the documentation (paragraph PRE) if some text is entered.
It is used to create the lines for the variable declaration in the linked processing.
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. |
It is used not only to delete the recording in the global variable table, but also
- to delete the associated documentation,
- to delete the declaration and the potential initialization of the variable in the processing
Caution: there is no Supervisor control on the use of this variable in the current processing or in any other processing.
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. |