Skip to main content

Type_CustomerTracking_String

Type_CustomerTracking_String = 'CustomerTracking'

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetTrackingTypeNum(Type_CustomerTracking_String); // 1
end;

Usage​

Type_CustomerTracking_String provides the exact CustomerTracking text paired with Type_CustomerTracking for the Velox tracking type domain.

Value

PropertyValue
Script typeString
Text value'CustomerTracking'
Paired numberType_CustomerTracking = 1
Direction labelCustomer
Database type tableShipment_Tracking_Type
Record fieldShipment_Tracking.TypeNum
Tag-map entryNo

Additional Technical Info​

Type_CustomerTracking_String is the canonical text for the CustomerTracking member of the Velox tracking-type vocabulary. Its fixed String value is 'CustomerTracking', paired with Type_CustomerTracking.

It selects an artifact-direction type. It does not create, load, validate, send, receive or change the state of a shipment, POD or tracking record.

Implementation

Velox declares and registers exact text CustomerTracking. GetTrackingTypeNum compares it with Delphi SameText and returns 1; GetTrackingTypeCode performs the reverse mapping. The String identifier is not in the Velox tag map.

The tracking converter is independent from the other two artifact-type converters even though all three families use customer value 1 and supplier value 2. Use GetTrackingTypeNum and GetTrackingTypeCode only for this family.

Database alignment

Fresh-build VxData seeds row 1 as CustomerTracking in Shipment_Tracking_Type, and nullable Shipment_Tracking.TypeNum references that table. Required Shipment_Tracking_Event_Type.TypeNum is intended to select type/status event behaviour, but its current foreign key points to Shipment_POD_Type; its status foreign key likewise points to Shipment_POD_Status.

The type-table code is exact CustomerTracking and the description is human-spaced. Code, number and display description are separate representations; persist the numeric key where TypeNum is expected.

Behaviour

Text-to-number conversion uses SameText, so case differences are accepted, but whitespace is not trimmed: customertracking is recognised and CustomerTracking is not. Unsupported text returns Null. Number-to-text conversion returns Null for Null or an unsupported number.

The value has meaning only in its tracking-type domain. The same integer in the other shipment artifact families, party roles, lifecycle statuses or transaction types is not a typed substitute.

Edge cases and quirks

  • CustomerTracking classifies a tracking artifact; it does not prove an event occurred, derive a location/ETA or emit a tracking notification.
  • Tracking lifecycle StatusNum is separate from artifact TypeNum and from the general processing Status field.
  • Current fresh-build tracking event routing has wrong-domain type/status foreign keys to POD tables. Seeded type values align, but callers must not treat that as schema correctness.
  • Customer/supplier is a Velox artifact-direction label, not proof of sender, recipient, bill-from/bill-to roles, ownership or transport direction.
  • Numeric PascalScript constants do not retain a domain type after evaluation; validate the target field/table contract before assignment.
  • Text conversion is case-insensitive and non-trimming; String constants themselves remain exact compiled text.
  • A nullable record TypeNum may contain Null even though the seed vocabulary defines this value.
  • Selecting a type does not select a lifecycle status or trigger an event-routing row.

Side effects

Reading or comparing Type_CustomerTracking_String has no database, file, network or shared-state side effect. Its converters are fixed in-memory mappings.

Errors

Reading the constant does not raise an error. Converter misses return Null; inputs outside the documented String/number contract can still encounter normal PascalScript Variant conversion behaviour. Persisting a value absent from the target type table can fail a database foreign key.

Performance and concurrency

This is immutable compiled metadata. Constant access and its two-branch converters are constant-time for practical purposes and do not carry mutable shipment state.

Remarks

Use the constant to make configuration intent explicit, then validate the surrounding dataset, direction, parties, lifecycle status and event configuration independently. The example is source-reviewed and non-destructive.

Related entries

Created 2026-07-15