Temperature_Ambient_String
Temperature_Ambient_String = 'Ambient'
Example
procedure ScriptEvent(var Value: variant);
begin
Value := Temperature_Ambient_String; // 'Ambient'
end;
Usage
Temperature_Ambient_String provides the exact Ambient temperature-category text paired with Temperature_Ambient for Velox product and transaction metadata.
Value
| Property | Value |
|---|---|
| Script type | String |
| Text value | Ambient |
| Paired number | Temperature_Ambient = 1 |
| Database domain | Temperature.Num / Temperature.Description |
| Fresh-build DefaultTemp | 20 (measurement unit not declared by the reviewed source/schema) |
Additional Technical Info
Temperature_Ambient_String is the script-visible String name for the Ambient temperature category. Its exact value is Ambient, paired with Temperature_Ambient value 1.
The constant identifies a category only. It does not read or set a measured temperature, apply refrigeration rules, select a product, validate a shipment or convert measurement units.
Implementation
Velox declares and registers the exact text Ambient. No temperature text/number converter is registered, and the String name is not in the Velox tag map.
Fresh-build VxData seeds Temperature row 1 with Description Ambient and DefaultTemp=20. The reviewed SQL does not label the temperature unit; do not assume Celsius, Fahrenheit or another scale solely from this constant.
Booking, PreAdvice and Shipment header TemperatureNum fields have foreign keys to Temperature. Product.TemperatureNum exists in the current product table script but has no declared foreign key there.
Behaviour
Use the numeric identifier where a TemperatureNum key is expected and the text only where a category name is expected. There is no automatic conversion between the two exposed by this family.
DefaultTemp is database reference data, not the constant's runtime value. Reading the constant does not retrieve that field or a record-specific TemperatureValue.
Edge cases and quirks
- The measurement unit for
DefaultTempandTemperatureValueis not declared in the reviewed Pascal or SQL definitions. Confirm the deployment's data contract before calculations or threshold comparisons. - String matching/conversion is caller-owned because no temperature converter is registered.
- The String identifier is not a tag-map entry.
Product.TemperatureNumis not constrained by a foreign key in the reviewed fresh-build Product script, unlike Booking, PreAdvice and Shipment header fields.- PascalScript retains no temperature-domain type information after evaluation, and values 1-3 overlap many unrelated constant families.
Side effects
Reading Temperature_Ambient_String, comparing it has no I/O or state-changing effect. The caller owns database lookup, assignment and temperature control.
Errors
Reading the constant does not raise an error. A receiving database field can reject a non-existent key, and caller-written unit conversion or text mapping can fail independently.
Performance and concurrency
This is an immutable compiled value. Access is constant-time and carries no shared mutable temperature state.
Remarks
The example is source-reviewed and non-destructive. It returns fixed category metadata only and does not test refrigeration or live measurements.
Related entries
Temperature_Ambientis the paired numeric identifier.