Skip to main content

Order_Response_Accepted

Order_Response_Accepted = 1

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetOrderResponseStatusCode(Order_Response_Accepted); // 'Accepted'
end;

Usage​

Order_Response_Accepted identifies the Accepted order-response outcome as Order_Response_Status.Num value 1 for Velox scripts and mappings.

Value

PropertyValue
Script typeLongInt
Numeric value1
Canonical textAccepted
Database domainOrder_Response_Status.Num
Data fieldOrder_Hdr.ResponseStatusNum

Additional Technical Info​

Order_Response_Accepted is the script-visible LongInt identifier for the Accepted order-response outcome. Its fixed value is 1, paired with Order_Response_Accepted_String. It is supplementary response detail and does not set the order lifecycle to Responded.

Implementation

Velox declares and registers the fixed LongInt value 1. GetOrderResponseStatusCode maps it to Accepted; GetOrderResponseStatusNum performs the reverse mapping. The numeric name is registered in the Velox tag map, so <!Order_Response_Accepted!> expands to 1.

A fresh VxData database seeds Order_Response_Status row 1 with description Accepted, and Order_Hdr.ResponseStatusNum references that domain.

Behaviour

Use Order_Response_Accepted only in the order-response outcome domain. The fixed reverse converter recognises the canonical token without querying the database. Reading or comparing the constant does not assign Order_Hdr.ResponseStatusNum or run order processing.

Edge cases and quirks

  • PascalScript stores the value as an untyped integer for domain purposes. 1 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_Response_Accepted, 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