Skip to main content

Intf_Issue

Intf_Issue = 40

Example​

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

Usage​

Intf_Issue identifies the Issue operational reference interface by fixed Interface.Num value 40 for scripts, database references and numeric tags.

Value​

PropertyValue
Script typeLongInt
Numeric value40
Database rowInterface.Num = 40
Interface codeIssue
Module rowNo (IsModule = 0)
Fresh-build defaultActive = 0; IsConfigured = 0

Additional Technical Info​

Intf_Issue is the script-visible LongInt identifier for the Issue operational reference interface. Its fixed value is 40, paired with exact code Issue in the Interface table.

The name identifies an interface category. It does not by itself expose Issue records, select a database operation, execute a module, authenticate a caller or grant permissions.

Implementation​

The native constant in vxVeloxEDI.pas, the PascalScript LongInt registration in uPSI_vxVeloxEDI.pas, the gVeloxConstMap entry and the fresh-build database row all use value 40.

Configuration processed by ProcessVeloxTags can replace <!Intf_Issue!> with decimal text 40. This tag feature reads the in-memory dictionary; it does not query the Interface table.

Behaviour​

  • Constant access returns an immutable number without loading or validating current database state.
  • Use it only where a consumer explicitly accepts an interface number or InterfaceNum.
  • Numeric tag expansion emits an unquoted number suitable for the surrounding configuration syntax when that syntax expects one.
  • Intf_Issue_String is a separately registered String code, not a runtime conversion result.

Edge cases and quirks​

  • The current seed row is inactive, unconfigured and not a module. The identifier does not enable the Issue category or prove that related data exists.
  • A generic interface key does not establish the accepted operation. Verify the target function, field, relationship or query before passing 40.
  • Category identity is not authorization. In particular, an identifier named Application, User, Setting, Mapping, Event or Issue does not bypass the product's normal permissions and validation paths.
  • Database state can change independently of the compiled executable; query Interface when current state matters.
  • The source/import/tag/database definitions are maintained in parallel. Treat disagreement as mixed product/data versions.
  • The String partner is not a numeric tag, and numeric tags are available only for names explicitly entered in gVeloxConstMap.

Side effects​

Reading or comparing the constant has no side effects. Downstream operations retain their own database, audit, security and transaction effects.

Errors​

The constant cannot fail. A consumer can reject a reference-interface key, fail to find the deployed row or deny the requested operation. An unknown <!...!> tag raises an invalid-tag exception.

Performance and concurrency​

Constant access and in-memory tag lookup are constant-time and thread-safe. Explicit database checks observe mutable shared state and should use the transaction/consistency guarantees required by the operation.

Remarks​

Prefer the named constant over literal 40. It preserves category intent while making clear that the number belongs to the Interface key space.

External references​

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

Created 2026-07-15