Skip to main content

Intf_Region

Intf_Region = 29

Example​

procedure ScriptEvent(var Value: variant);
begin
  if DATA_Interface['Num'].AsInteger = Intf_Region then
    Value := Intf_Region_String;
end;

Usage​

Intf_Region identifies the Region reference interface by its fixed Interface.Num value 29 for scripts, database references and Velox numeric tags.

Value​

PropertyValue
Script typeLongInt
Numeric value29
Database rowInterface.Num = 29
Interface codeRegion
Module rowNo (IsModule = 0)
Fresh-build defaultActive = 0; IsConfigured = 0

Additional Technical Info​

Intf_Region is the script-visible LongInt identifier for the Region reference interface. Its fixed value is 29, the current Interface.Num primary key paired with code Region.

Use it where Velox explicitly expects an interface number or InterfaceNum. It identifies a reference-data category; it does not execute a module or load that category's records.

Implementation​

vxVeloxEDI.pas declares this value, uPSI_vxVeloxEDI.pas registers it as a PascalScript LongInt, and the fresh-build database seeds the same key/code pair.

InitVeloxConstMap also inserts Intf_Region into the case-insensitive numeric tag dictionary. Configuration processed by ProcessVeloxTags can therefore replace <!Intf_Region!> with the unquoted decimal text 29.

Behaviour​

  • Reading the compile-time constant performs no database query, category lookup or validation.
  • It can be compared with DATA_Interface['Num'] or used for a field/function that explicitly accepts an interface key.
  • Numeric tag replacement is configuration processing, not script-constant evaluation.
  • Intf_Region_String is a separate String registration; Velox does not convert the pair dynamically.

Edge cases and quirks​

  • The row is seeded as inactive, unconfigured and not a module. The constant does not make the Region category available or prove that any corresponding reference rows exist.
  • IsModule = 0 is material: do not pass this identifier to an API merely because that API accepts a module interface number. Confirm the consumer accepts reference-interface keys.
  • Deployed database state can change independently of the executable. Check Interface when behavior depends on current Active or IsConfigured values.
  • Interface keys 14-19 are blank reserved rows; valid named reference identifiers resume at 20.
  • Source constants, importer registrations, tag-map values and database seeds are maintained in parallel. A mismatch indicates mixed deployment versions, not a conversion rule.
  • Numeric tags exist only for explicitly mapped numeric names. The String partner is not a valid <!...!> tag.

Side effects​

Reading or comparing the constant has no side effects. A downstream lookup or data operation has the effects, permissions and transaction behavior of that operation.

Errors​

The constant cannot fail. Consumers can fail when the deployed interface row is missing, inaccessible, inactive or not accepted for that operation. An unknown numeric tag name raises an invalid-tag exception.

Performance and concurrency​

Constant access and tag lookup are constant-time and thread-safe. Database configuration and category data remain mutable shared state and may require an explicit query/transaction for a consistent decision.

Remarks​

Prefer Intf_Region over the literal 29. The name preserves the reference-category meaning and avoids confusing this key with unrelated identifiers that reuse the same number.

External references​

No Delphi or Free Pascal equivalent applies. This identifier and its database meaning are Velox-owned.

Created 2026-07-15