Order_Line_Changed
Order_Line_Changed = 3
Example
procedure ScriptEvent(var Value: variant);
begin
Value := GetOrderLineStatusCode(Order_Line_Changed); // 'Changed'
end;
Usage
Order_Line_Changed identifies the Changed order-line comparison state as Order_Line_Status.Num value 3 for Velox scripts and mappings.
Value
| Property | Value |
|---|---|
| Script type | LongInt |
| Numeric value | 3 |
| Canonical text | Changed |
| Database domain | Order_Line_Status.Num |
| Data field | Order_Line.StatusNum |
Additional Technical Info
Order_Line_Changed is the script-visible LongInt identifier for the Changed order-line comparison state. Its fixed value is 3, paired with Order_Line_Changed_String. It describes the line comparison/result domain and does not change the order lifecycle.
Implementation
Velox declares and registers the fixed LongInt value 3. GetOrderLineStatusCode maps it to Changed; GetOrderLineStatusNum performs the reverse mapping. The numeric name is registered in the Velox tag map, so <!Order_Line_Changed!> expands to 3.
A fresh VxData database seeds Order_Line_Status row 3 with description Changed, and Order_Line.StatusNum references that domain.
Behaviour
Use Order_Line_Changed only in the order-line comparison state domain. The fixed reverse converter recognises the canonical token without querying the database. Reading or comparing the constant does not assign Order_Line.StatusNum or run order processing.
Edge cases and quirks
- PascalScript stores the value as an untyped integer for domain purposes.
3also occurs in other order families and can have a different meaning there. - Line and response value
3both use textChanged, but they belong to different database tables, fields and converters. - Response value
2isRejected, while line value2isSame; the identical number is not semantically interchangeable. - Number-to-text conversion returns
NullforNullor an unsupported value rather than choosing a default.
Side effects
Reading Order_Line_Changed, expanding its tag or comparing it has no I/O or state-changing side effect. Any persistence or processing effect comes from the caller.
Errors
Reading the constant does not raise an error. Passing a value from another numeric domain can silently select the wrong branch before a database constraint or later business rule detects it.
Performance and concurrency
This is an immutable compiled value. Access and fixed-case conversion are constant-time for practical purposes and carry no shared mutable state.
Remarks
The example is source-reviewed and non-destructive. It performs only fixed numeric-to-text conversion.
Related entries
Order_Line_Changed_Stringis the paired text.GetOrderLineStatusCodeconverts a supported number to text.GetOrderLineStatusNumconverts recognised text to a number.