Skip to main content

Order_Line_Deleted

Order_Line_Deleted = 4

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetOrderLineStatusCode(Order_Line_Deleted); // 'Deleted'
end;

Usage​

Order_Line_Deleted identifies the Deleted order-line comparison state as Order_Line_Status.Num value 4 for Velox scripts and mappings.

Value

PropertyValue
Script typeLongInt
Numeric value4
Canonical textDeleted
Database domainOrder_Line_Status.Num
Data fieldOrder_Line.StatusNum

Additional Technical Info​

Order_Line_Deleted is the script-visible LongInt identifier for the Deleted order-line comparison state. Its fixed value is 4, paired with Order_Line_Deleted_String. It describes the line comparison/result domain and does not delete a database row by itself.

Implementation

Velox declares and registers the fixed LongInt value 4. GetOrderLineStatusCode maps it to Deleted; GetOrderLineStatusNum performs the reverse mapping. The numeric name is registered in the Velox tag map, so <!Order_Line_Deleted!> expands to 4.

A fresh VxData database seeds Order_Line_Status row 4 with description Deleted, and Order_Line.StatusNum references that domain.

Behaviour

Use Order_Line_Deleted 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. 4 also occurs in other order families and can have a different meaning there.
  • Line and response value 3 both use text Changed, but they belong to different database tables, fields and converters.
  • Response value 2 is Rejected, while line value 2 is Same; the identical number is not semantically interchangeable.
  • Number-to-text conversion returns Null for Null or an unsupported value rather than choosing a default.

Side effects

Reading Order_Line_Deleted, 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

Created 2026-07-15