Intf_Voyage_String

Intf_Voyage_String = 'Voyage'

Example

procedure ScriptEvent(var Value: variant);
begin
  if DATA_Interface['Code'].AsString = Intf_Voyage_String then
    Value := Intf_Voyage;
end;

Usage

Intf_Voyage_String provides the exact Voyage Interface.Code token paired with operational reference-interface key 33.

Value

Property	Value
Script type	String
Exact value	Voyage
Database row	Interface.Num = 33
Numeric partner	Intf_Voyage = 33
Module row	No (IsModule = 0)
Fresh-build default	Active = 0; IsConfigured = 0

Additional Technical Info

Intf_Voyage_String is the script-visible String code Voyage for operational reference-interface key Intf_Voyage = 33.

Use it for trusted interface-code comparisons or lookups. It identifies a category only; it does not load Voyage records, select an operation, authenticate a caller or confer access.

Implementation

vxVeloxEDI.pas, its PascalScript importer and the fresh-build Interface.Code field use the exact token Voyage. The String registration is maintained separately from numeric key 33.

String names are absent from gVeloxConstMap; <!Intf_Voyage_String!> is invalid. Only the numeric name Intf_Voyage can be expanded as a Velox tag.

Behaviour

• Reading the constant returns immutable text without a database query.
• It can be compared with DATA_Interface['Code'].AsString or passed to an operation documented to accept an interface code.
• Canonical capitalization is part of the documented token. Database comparison still follows the deployed database collation.
• No script-visible native converter currently maps arbitrary interface codes and numbers.

Edge cases and quirks

• The database row is seeded inactive/unconfigured and is not a module. A matching code does not enable the category or prove related data exists.
• Do not substitute a display Description or CustomDescription; those fields may change while Code is the technical token.
• The Scriptlet GetInterfaceForCode helper interpolates its argument into SQL instead of binding a parameter. Pass this fixed/trusted constant, never raw external text.
• Script String equality and SQL collation are distinct; do not depend on collation to repair whitespace, localization or an altered code.
• A category name does not select a concrete table API or grant authority. Follow the documentation and security checks of the actual consumer.
• Native GetInterfaceNum/GetInterfaceCode implementations and registrations are commented out.

Side effects

Constant access has no side effects. A separate lookup or operation uses its caller's connection, permissions, auditing and transaction context.

Errors

The constant cannot fail. Lookup can report not found for a missing/changed deployment row. Untrusted text passed to an interpolating helper can produce malformed SQL; use a constant or parameterized logic.

Performance and concurrency

Constant access is constant-time and thread-safe. Database lookup cost, collation and concurrent state apply only when a separate operation performs the query.

Remarks

Prefer Intf_Voyage_String over literal Voyage so the category dependency and its numeric pair remain explicit.

Related entries

• Intf_Voyage — numeric key and supported <!Intf_Voyage!> tag.
• DATA_Interface — dataset for explicit interface-row queries.
• ProcessTags — numeric tag processing; this String name is not a tag.

External references

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

Created 2026-07-15