MULTI Variables
MULTI variable objects obtain a combination of values from two other Variable objects.
This topic provides information on the following:
- Overview
- Defining the Variable Settings
- Specifying Data & Formatting Settings
- Specifying the Script Access Setting
- Defining the Variable Usage in Other Clients
- Previewing Commands
Variables that use the "Multi" source setting obtain a combination of values from two other Variable objects. Use the variable tab to define the source variable and the type of value calculation.
Defining the Variable Settings
Field/Element |
Description |
---|---|
Type | This read-only field shows Multi as the variable type. You determine the variable type when you create the object. It cannot be changed once the variable is defined. |
Variable 1 Variable 2 |
Definition of the two Variable objects that serve as values sources. Variable 1 determines the number of columns. The reference columns' values of both variables are combined depending on the operation that has been specified. The reference column depends on the variable source: Key column (in static variables), first value column (variable source: SQL, SQL-internally, Multi), or the Filelist column (variable source: Filelist). Columns that are not included in Variable 2 do not include a value for the corresponding entries. The values of Variable 1 are used if two Variable objects contain entries of the same name. Note that the data type of the source variable's reference column should match the Multi variable's data type. Otherwise, an error occurs or the values are not available. |
Operation |
The mathematical process used to determine which values to retrieve from Variable 1 and 2.
|
Specifying Data & Formatting Settings
Column |
Description |
---|---|
Data Type |
The data type decides the format of the variable's value.
The exact format of the selected data type (with the exception of "String") can be determined in the Output Format field. The data type of the values that are available in the first column is checked. The variable's data type must match the data type of the first column returned by the SQL statements when you use the sources "SQL" or "SQL internally". Data can also be processed using specific SQL statements. An error occurs if static variables should be stored or dynamic variables are accessed and the data types do not match. Note the following if you change the data type of static Variable objects that already include values:
The data type of variables with the type "Multi", "SQL", or "SQL internally" can be changed at any time. The data type of the script variable in question ("float", "signed", "unsigned", or "string") is irrelevant in values that have been retrieved from Variable objects with the data type "Number" when using the script element GET_VAR. The value can always be stored. Algebraic signs and decimal places are removed if they are not supported by the script variable's data type. The values are always passed on to the script as a "string" if a different data type has been specified in the Variable object. |
Output Format |
This setting defines the format that should be used to store values in the Variable object (source: static variables) or to retrieve values from the data source (dynamic variables). The contents of this selection menu depend on the data type. Several different formats are available for each data type (except for the String type). The output format only refers to the first column. In static variables, this is the column Value 1; in Database and Multi variables, it is the first basic column. Note that Multi variables use the first basic column as their reference column. This means that the source variable's output format can affect the retrieved values. The output format of static variables for a particular datatype can be changed at any time. In doing so, the values are converted to the new format. If the values do not match the old format, they cannot be converted to a new format. The format that is used to enter value in static variables is irrelevant unless it is an AE-supported format of the data type in question. The values are then converted to the relevant output format. The data type "Text" does not show this combo box. Timestamp
Date
Time
Number
Some date formats include RR as a placeholder for the abbreviated year. Having both YY and RR accommodates different century-counting conventions based on the two digits of the abbreviated year value. For example: For example: The time value for the data type "Time" or "Timestamp" must be a 4 or 6-digit number. Decimal places are removed. 4-digit numbers are converted to hours and minutes. Examples: Data type: Timestamp |
Set min. value Min. value |
Enforces a minimum value. The data type "Text" does not show these fields. |
Set max. value Max value |
Enforces a maximum value. The data type "Text" does not show these fields. |
Limit text length Max. Text Length |
Enforces a maximum character length. Allowed values: 1 to 1024 If this option is deactivated, there is no limit. The Key column of VARA objects has a maximum limit of 200 characters. This limit always exists and cannot be increased or deactivated. The result column of dynamic variables has no limit. The length depends on the value columns. In static and dynamic variables, this limit refers to the first value column. The Key or result column is not checked. Values that exceed the maximum length are excluded. Only the data type "Text" shows these fields. |
Force upper case |
Lower case letters that are used in variable values are automatically converted to upper case. This only affects the first value column. Only the data type "Text" shows this field. |
Result Format |
Definition of the result column's contents. The first column that is displayed in the preview is the result column. The result column can show a combination of value columns and any other characters. This is defined via the Result Format. Column numbers that were specified using curly brackets {} in the Result Format field will be replaced by the value of the corresponding column. For example: Without a Result Format being specified, the value of the variable's Result or Key column is assumed. The values of the result column have to comply with the variable's limitations (min. value, max. value, limit text to), the output format, or the data type. Otherwise, the result column does not include a value. |
Specifying the Script Access Setting
You can specify what happens if a key is not found with the If key not found radio buttons.
To: |
Choose: |
---|---|
Have an error message displayed if an object attempts to access an item that is not available at runtime via script | Return error |
Not use the result of output format of when it is " " | Return initial values |
Defining the Variable Usage in Other Clients
In client 0 you specify how the VARA object will behave in other clients.
When you define Variable objects in system Client 0, they can be used in other clients, either because they refer to the values set in the Variable in Client 0 or because you copy the original object from Client 0 to other clients and, if necessary, edit its values in the target clients.
With the Variable Usage in Other Clients options you define the behavior of this Variable object in clients other than 0:
Option |
Description |
---|---|
Don't share but allow duplicates |
If you select this option, this VARA object is available in clients other than 0 and you can use it there. You can modify all of its parameters in the non-0 clients, which can then be different per client. The name of the variable can be kept in non-0 clients. This means that if there is already a VARA object in the non-0 client with this name, two independent VARA objects with the same name will be available. You can modify all the parameters of both variables independently per client. |
Share and allow read-only access |
If you select this option, this VARA object is available in clients other than 0 and you can use it there but you cannot modify any of its parameters. Additionally, the name of this VARA object must be unique system-wide. |
Share but keep attribute settings from system client |
If you select this option, this VARA object can be copied to non-0 clients. If you do so, it keeps all the definitions made on the Attributes page but you can edit the Key and Value settings in the non-0 clients. Each client can have its own Key/Value definitions. Only available for STATIC variables. |
To preview the variable, click Preview. A preview of the result values is displayed.