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
Presentation
A single screen is used to write the variable, specify it format, its size and if needed to setup its initialization.
Close
Fields
The following fields are present on this tab :
Block number 1
| The following standard is used to name the global variable :
This variable belongs to the class [V]. |
|
|
Characteristics
| An activity code is used to:
If the activity code is disabled:
|
| 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. |
| This flag indicates that this element is published. It can therefore be re-used by the custom/specific. An associated documentation is available. |
Description
| This text field is used to display the comments relative to the current record. |
Format
| 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. |
| Field displayed with the value coming from the 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. |
Sizing formulas
| 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. |
|
|
|
|
|
|
Initialization
| 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 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. |
|
|
Generation
| 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 :
|
|
|
| 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. |
Close
Specific Buttons
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close The global variables declared by the standard are protected. Some fields only can be modified. |
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close 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. |
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close It is used not only to delete the recording in the global variable table, but also
Caution: there is no Supervisor control on the use of this variable in the current processing or in any other processing. |
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close Is used to duplicate the definition of a global variable to another folder. It is then necessary to validate in order to generate the associated processing. |
Is used to regenerate all processings known in this dictionary of global variables. |
Menu Bar
Option / Formula Wizard setup
Used to tunnel to the function "contextual formula wizard".
Documentation / Paragraphs
This menu item allows access to the documentation management on the first paragraph of the documentation (if there is one) associated with the current record.
Documentation / Links
This menu item allows access to link management. It is used to define the links between the current record and other records (for example, 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 item launches a documentation generation. You can also launch it from the Generation button at the bottom of the screen.
You can launch three types of generation one by one or simultaneously
- The generation of the documentation structure from the dictionary (ADOCUMENT, ADOCBLB, and ADOCCLB tables)
- 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 you can modify it at launch time.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Non-existent setup
If a setup is entered, it must be present in the setup definition table ADOPAR.
This setup is used by global variable xxxxxxxxx
This setup is already associated with a global variable. It can load only one variable.
Incorrect data type
The data type of the variable and the setup type must be fully compatible.
Incorrect value
The variable code must begin with G, X, Y, or Z
The name of a global variable must start with a G for the standard development, and an X, Y or Z for the specific development.