Skip to main content

Order_Responded_String

Order_Responded_String = 'Responded'

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetOrderStatusNum(Order_Responded_String); // 2
end;

Usage​

Order_Responded_String provides the exact Responded text paired with order lifecycle-status value 2 and recognised by Velox order-status conversion.

Value

PropertyValue
Script typeString
Exact literalResponded
Numeric partner2 through Order_Responded
Database representationOrder_Status.Description for row 2

Additional Technical Info​

Order_Responded_String is the canonical script-visible text Responded paired with order lifecycle-status value Order_Responded = 2. Use it for canonical output or as an input to the order-status converter.

The string names a lifecycle state. It does not transition, validate or persist an order.

Implementation

Velox declares and registers the exact String literal Responded. GetOrderStatusNum compares input with it using Delphi SameText, so recognised ASCII status text is case-insensitive. GetOrderStatusCode returns this exact casing for value 2.

The fresh-build Order_Status table stores Responded in Description; it has no separate Code column.

Behaviour

Pass Order_Responded_String to GetOrderStatusNum for deterministic conversion. Different letter casing is recognised, but surrounding whitespace is not removed and produces Null.

Unlike numeric Order_Responded, Order_Responded_String is not registered in the Velox constant tag map. Use <!Order_Responded!> for configuration-tag expansion.

Edge cases and quirks

  • Direct script string comparisons can have different case/coercion behaviour from GetOrderStatusNum; use the converter when normalising external status text.
  • Order_Hdr.StatusNum and related StatusNum fields use the numeric lifecycle key. General Status columns use the separate issue/presentation scale.
  • The same word can occur in another family. For example, Changed has distinct order lifecycle, order-response and order-line identifiers even where their numbers happen to match.
  • Unknown or whitespace-padded input returns Null; there is no fallback lifecycle state.

Side effects

Reading or comparing Order_Responded_String has no I/O or state-changing side effect. Conversion uses a fixed in-process mapping and does not query Order_Status.

Errors

Reading the constant does not raise an error. The converter returns Null for unknown text rather than raising an order-specific exception.

Performance and concurrency

This is an immutable compiled string. Access and the fixed seven-value converter are constant-time for practical purposes and carry no shared mutable Velox state.

Remarks

The example is source-reviewed and non-destructive. Use the constant's exact casing for canonical output even though reverse conversion is case-insensitive.

Related entries

Created 2026-07-15